TF-M has been under active development since it was launched in Q1'18. It is being designed to include 1. //**Secure boot**// ensuring integrity of runtime images and responsible for firmware upgrade. 2. Runtime firmware consisting of //** TF-M Core**// responsible for secure isolation, execution and communication aspects. and a set of Secure Services providing services to the Non-Secure and Secure Applications. The secures services currently planned to be supported are //**Secure Storage, Cryptography, Audit Logs, Attestation, Provisioning and Platform Services**// Roadmap below shows when the services are getting supported and then enhanced. Currently Supported Features - [[ http://git.trustedfirmware.org/trusted-firmware-m.git/tree/bl2/ext/mcuboot | Secure Boot]] - [[ http://git.trustedfirmware.org/trusted-firmware-m.git/tree/docs/user_guides/services/tfm_sst_integration_guide.md | Secure Storage]] - [[ http://git.trustedfirmware.org/trusted-firmware-m.git/tree/docs/user_guides/services/tfm_log_integration_guide.md | Audit Logs]] Q3'18 (July-Sept'18) - [TF-M Core] Inter Process Communication (IPC) - [Secure Boot] Enhancements - [Secure Storage] Rollback Protection - [Crypto] PSK TLS - [Attestation] Initial Attestation Service Q4'18 (Oct-Dec'18) - [TF-M Core] Secure Partition Manager, IRQ Handling - [Secure Boot] Multiple Image Update - [Secure Storage] Key Diversification - [Crypto] TLS with Key exchange - [Audit Logs] Encryption - [Attestation] [[ https://tools.ietf.org/html/draft-mandyam-eat-00 | EAT ]] Support - [Platform] NV Count, Timer - Open CI Q1'19 (Jan-Mar'19) - [TF-M Core] Scheduler - [Secure Boot] Key Revocation, Rollback Protection - [Secure Storage] Lifecycle Management - [Crypto] RNG, KDF - [Audit Logs] Secure Storage - [Platform] GPIO, Debug, NONCE

TF-M has been under active development since it was launched in Q1'18. It is being designed to include 1. //**Secure boot**// ensuring integrity of runtime images and responsible for firmware upgrade. 2. Runtime firmware consisting of //** TF-M Core**// responsible for secure isolation, execution and communication aspects. and a set of Secure Services providing services to the Non-Secure and Secure Applications. The secures services currently planned to be supported are //**Secure Storage, Cryptography, Audit Logs, Attestation, Provisioning and Platform Services**// Roadmap below shows when the services are getting supported and then enhanced. Currently Supported Features - [[ http://git.trustedfirmware.org/trusted-firmware-m.git/tree/bl2/ext/mcuboot | Secure Boot]] - [[ http://git.trustedfirmware.org/trusted-firmware-m.git/tree/docs/user_guides/services/tfm_sst_integration_guide.md | Secure Storage]] - [[ http://git.trustedfirmware.org/trusted-firmware-m.git/tree/docs/user_guides/services/tfm_audit_integration_guide.md | Audit Logs]] Q3'18 (July-Sept'18) - [TF-M Core] Inter Process Communication (IPC) - [Secure Boot] Enhancements - [Secure Storage] Rollback Protection - [Crypto] PSK TLS - [Attestation] Initial Attestation Service Q4'18 (Oct-Dec'18) - [TF-M Core] Secure Partition Manager, IRQ Handling - [Secure Boot] Multiple Image Update - [Secure Storage] Key Diversification - [Crypto] TLS with Key exchange - [Audit Logs] Encryption - [Attestation] [[ https://tools.ietf.org/html/draft-mandyam-eat-00 | EAT ]] Support - [Platform] NV Count, Timer - Open CI Q1'19 (Jan-Mar'19) - [TF-M Core] Scheduler - [Secure Boot] Key Revocation, Rollback Protection - [Secure Storage] Lifecycle Management - [Crypto] RNG, KDF - [Audit Logs] Secure Storage - [Platform] GPIO, Debug, NONCE

TF-M has been under active development since it was launched in Q1'18. It is being designed to include 1. //**Secure boot**// ensuring integrity of runtime images and responsible for firmware upgrade. 2. Runtime firmware consisting of //** TF-M Core**// responsible for secure isolation, execution and communication aspects. and a set of Secure Services providing services to the Non-Secure and Secure Applications. The secures services currently planned to be supported are //**Secure Storage, Cryptography, Audit Logs, Attestation, Provisioning and Platform Services**// Roadmap below shows when the services are getting supported and then enhanced. Currently Supported Features - [[ http://git.trustedfirmware.org/trusted-firmware-m.git/tree/bl2/ext/mcuboot | Secure Boot]] - [[ http://git.trustedfirmware.org/trusted-firmware-m.git/tree/docs/user_guides/services/tfm_sst_integration_guide.md | Secure Storage]] - [[ http://git.trustedfirmware.org/trusted-firmware-m.git/tree/docs/user_guides/services/tfm_logaudit_integration_guide.md | Audit Logs]] Q3'18 (July-Sept'18) - [TF-M Core] Inter Process Communication (IPC) - [Secure Boot] Enhancements - [Secure Storage] Rollback Protection - [Crypto] PSK TLS - [Attestation] Initial Attestation Service Q4'18 (Oct-Dec'18) - [TF-M Core] Secure Partition Manager, IRQ Handling - [Secure Boot] Multiple Image Update - [Secure Storage] Key Diversification - [Crypto] TLS with Key exchange - [Audit Logs] Encryption - [Attestation] [[ https://tools.ietf.org/html/draft-mandyam-eat-00 | EAT ]] Support - [Platform] NV Count, Timer - Open CI Q1'19 (Jan-Mar'19) - [TF-M Core] Scheduler - [Secure Boot] Key Revocation, Rollback Protection - [Secure Storage] Lifecycle Management - [Crypto] RNG, KDF - [Audit Logs] Secure Storage - [Platform] GPIO, Debug, NONCE