You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Edge Secured-core is an incremental certification in the Azure Certified Device program for IoT devices running a full operating system, such as Linux or Windows 10 IoT.This program enables device partners to differentiate their devices by meeting an additional set of security criteria. Devices meeting this criteria enable these promises:
18
+
Edge Secured-core is an incremental certification in the Azure Certified Device program for IoT devices running a full operating system, such as Linux, Windows 10 IoT or Azure Sphere OS. This program enables device partners to differentiate their devices by meeting an additional set of security criteria. Devices meeting this criteria enable these promises:
19
19
20
20
1. Hardware-based device identity
21
21
2. Capable of enforcing system integrity
@@ -25,7 +25,6 @@ Edge Secured-core is an incremental certification in the Azure Certified Device
25
25
6. Built in security agent and hardening
26
26
27
27
28
-
Overview content
29
28
::: zone pivot="platform-windows"
30
29
31
30
## Windows IoT OS Support
@@ -492,191 +491,186 @@ Validation|Device to be validated through toolset to ensure the device supports
492
491
::: zone pivot="platform-sphere"
493
492
494
493
## Azure Sphere platform Support
495
-
The Mediatek MT3620AN must be included in your design. For any component that can connect to the internet directly from your hardware product outside of this chip, including cellular modems, additional certification details may be required.
494
+
The Mediatek MT3620AN must be included in your design. Additional guidance for building secured Azure Sphere applications can be within the [Azure Sphere application notes](https://learn.microsoft.com/azure-sphere/app-notes/app-notes-overview).
496
495
497
-
All operating systems on device must meet Secured Core requirements
498
496
499
-
Additional considerations for Azure Sphere are provided as an application note here: [Azure Sphere application notes](https://learn.microsoft.com/azure-sphere/app-notes/app-notes-overview)
500
-
501
-
502
-
## Sphere Hardware/Firmware Requirements
497
+
## Azure Sphere Hardware/Firmware Requirements
503
498
504
499
---
505
-
|Name|SecuredCore.Hardware.Identity|Sphere|
500
+
|Name|SecuredCore.Hardware.Identity|Azure Sphere|
506
501
|:---|:---|:---|
507
502
|Status|Required|2023|
508
-
|Description|The purpose of the requirement is to validate the device identify is rooted in hardware.||
503
+
|Description|The purpose of the requirement is to validate the device identity is rooted in hardware.||
509
504
|Validation Type|Pre-validated, no additional validation is required||
510
505
|Validation|Provided by Microsoft||
511
-
|Resources|[Setup auto provisioning with DPS](../iot-dps/quick-setup-auto-provision.md)||
|Description|The purpose of the requirement is to validate that applications accepting input from the network are not running with elevated privileges.|
606
-
|Validation Type|Automated|
600
+
|Validation Type|Pre-validated, no additioanl validation is required|
|Description|The purpose of this requirement is to validate that applications cannot connect to endpoints that have not been authorized.|
616
-
|Validation Type|Automated|
610
+
|Validation Type|Pre-validated, no additioanl validation is required|
617
611
|Validation|Provided by Microsoft|
618
612
619
613
620
-
## Sphere Software/Service Requirements
614
+
## Azure Sphere Software/Service Requirements
621
615
---
622
-
|Name|SecuredCore.Built-in.Security|Sphere|
616
+
|Name|SecuredCore.Built-in.Security|Azure Sphere|
623
617
|:---|:---|:---|
624
618
|Status|Required|2023|
625
-
|Description|The purpose of the requirement is to make sure devices can report security information and events by sending data to Azure Defender for IoT. <br>Note: Download and deploy security agent from GitHub|
626
-
|Validation Type|Automated|
619
+
|Description|The purpose of this requirement is to make sure devices can report security information and events by sending data to a Microsoft telemetry service.|
620
+
|Validation Type|Pre-validated, no additioanl validation is required|
627
621
|Validation|Provided by Microsoft|
628
622
|Resources|[Collect and interpret error data - Azure Sphere](https://learn.microsoft.com/azure-sphere/deployment/interpret-error-data?tabs=cliv2beta)</br>[Configure crash dumps - Azure Sphere](https://learn.microsoft.com/azure-sphere/deployment/configure-crash-dumps)|
|Description|The purpose of the requirement is to validate that updates must be signed.|
667
-
|Validation Type|Automated|
661
+
|Validation Type|Pre-validated, no additioanl validation is required|
668
662
|Validation|Provided by Microsoft|
669
663
670
664
671
665
672
-
## Sphere Policy Requirements
666
+
## Azure Sphere Policy Requirements
673
667
---
674
668
|Name|SecuredCore.Policy.Protection.Debug|
675
669
|:---|:---|
676
670
|Status|Required|
677
671
|Description|The purpose of the policy requires that debug functionality on the device is disabled.|
678
-
|Validation Type|Manual/Tools|
679
-
|Validation|Device to be validated through toolset to ensure that debug functionality requires authorization to enable.|
672
+
|Validation Type|Pre-validated, no additioanl validation is required|
673
+
|Validation|Provided by Microsoft|
680
674
681
675
682
676
---
@@ -685,9 +679,9 @@ Additional considerations for Azure Sphere are provided as an application note h
685
679
|Name|SecuredCore.Policy.Manageability.Reset|
686
680
|:---|:---|
687
681
|Status|Required|
688
-
|Description|The policy requires that the device can execute two use cases: a) Ability to perform a reset (remove user data, remove user configs), b) Restore device to last known good in the case of an update causing issues.|
689
-
|Validation Type|Manual/Tools|
690
-
|Validation|Device to be validated through a combination of toolset and submitted documentation that the device supports this functionality. The device manufacturer can determine whether to implement these capabilities to support remote reset or only local reset.|
682
+
|Description|The policy requires that the device can execute two use cases: a) Ability to perform a reset (remove user data, remove user configurations), b) Restore device to last known good in the case of an update causing issues.|
683
+
|Validation Type|Pre-validated, no additioanl validation is required|
684
+
|Validation|Provided by Microsoft|
691
685
692
686
693
687
---
@@ -697,8 +691,8 @@ Additional considerations for Azure Sphere are provided as an application note h
697
691
|:---|:---|
698
692
|Status|Required|
699
693
|Description|The purpose of this policy is to ensure that the device remains secure.|
700
-
|Validation Type|Manual|
701
-
|Validation|Commitment from submission that devices certified will be required to keep devices up to date for 60 months from date of submission. Specifications available to the purchaser and devices itself in some manner should indicate the duration for which their software will be updated.|
694
+
|Validation Type|Pre-validated, no additioanl validation is required|
695
+
|Validation|Provided by Microsoft|
702
696
703
697
704
698
---
@@ -708,9 +702,10 @@ Additional considerations for Azure Sphere are provided as an application note h
708
702
|:---|:---|
709
703
|Status|Required|
710
704
|Description|The purpose of this policy is to ensure that there is a mechanism for collecting and distributing reports of vulnerabilities in the product.|
711
-
|Validation Type|Manual|
712
-
|Validation|Documentation on the process for submitting and receiving vulnerability reports for the certified devices will be reviewed.|
713
-
705
+
|Validation Type|Pre-validated, no additioanl validation is required|
706
+
|Validation|Azure Sphere vulnerabilities are collected by Microsoft through MSRC and are published to customers through the Tech Community Blog, Azure Sphere “What’s New” page, and through Mitre’s CVE database.|
707
+
|Resources|<ul><li>[Report an issue and submission guidelines](https://www.microsoft.com/msrc/faqs-report-an-issue)</li><li>[What's new - Azure Sphere](https://learn.microsoft.com/azure-sphere/product-overview/whats-new)</li><li>
@@ -719,8 +714,8 @@ Additional considerations for Azure Sphere are provided as an application note h
719
714
|:---|:---|
720
715
|Status|Required|
721
716
|Description|The purpose of this policy is to ensure that vulnerabilities that are high/critical (using CVSS 3.0) are addressed within 180 days of the fix being available.|
722
-
|Validation Type|Manual|
723
-
|Validation|Documentation on the process for submitting and receiving vulnerability reports for the certified devices will be reviewed.|
717
+
|Validation Type|Pre-validated, no additioanl validation is required|
0 commit comments