Roadmap

From TNC@FHH

At the time, we are trying to extend TNC@FHH with the following features:

1. Add TPM Support
   • Currently, TNC@FHH does not use a TPM in any case. The integrity tests done by the TNC-Client in combination with the IMC's are only reliable, if these software components can not be modified by an attacker. Otherwise, an attacker could fake messages at will. One major change will therefore be to add TPM support to TNC@FHH.
2. Improve Policy Management
   • The descision of the TNC-Server whether to open a port or not is based on multiple IMV suggestions. Currently, these suggestions are combined in a rather simple way to make a final descision. In the future, emphasising several suggestions should be possible.
3. Initiate integrity checks by the TNC-server
   • At the moment, the TNC-handshake has to be initiated by the TNC-client. Unfortunately, our TNC-server is not able to do that. I.e., it is currently not possible to check the integrity of an endpoint when an aspect of the TNC-policy, which is located at the TNC-server, changes.