updated some TNC scenarios

This commit is contained in:
Andreas Steffen
2013-07-19 19:36:07 +02:00
parent dcd5129c25
commit 645e9291f0
4 changed files with 59 additions and 18 deletions
@@ -7,7 +7,8 @@ At the outset the gateway authenticates itself to the clients by sending an IKEv
The strong EAP-TTLS tunnel protects the ensuing weak client authentication based on <b>EAP-MD5</b>.
In a next step the EAP-TNC protocol is used within the EAP-TTLS tunnel to determine the
health of <b>carol</b> and <b>dave</b> via the <b>IF-TNCCS 1.1</b> client-server interface.
The communication between IMCs and IMVs is based on the <b>IF-M</b> protocol defined by <b>RFC 5792 PA-TNC</b>.
The communication between the OS and Attestation IMC and the Attestion IMV is based on the
<b>IF-M</b> protocol defined by <b>RFC 5792 PA-TNC</b>.
<p>
<b>carol</b> passes the health test and <b>dave</b> fails. Based on these measurements the clients
are connected by gateway <b>moon</b> to the "rw-allow" and "rw-isolate" subnets, respectively.