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
|Description|The purpose of this test is to validate that code integrity is available on this device.|
139
+
|Description|The purpose of this requirement is to validate that code integrity is available on this device.|
140
140
|Requirements dependency|HVCI is enabled on the device.|
141
141
|Validation Type|Manual/Tools|
142
142
|Validation|Device to be validated through [Edge Secured-core Agent](https://aka.ms/Scforwiniot) toolset to ensure that HVCI is enabled on the device.|
@@ -203,7 +203,7 @@ Some requirements of this program are based on a business agreement between your
203
203
|Name|SecuredCore.Policy.Manageability.Reset|
204
204
|:---|:---|
205
205
|Status|Required|
206
-
|Description|The purpose of this test is to validate the device against 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.|
206
+
|Description|The purpose of this requirement is to validate the device against 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.|
207
207
|Requirements dependency||
208
208
|Validation Type|Manual/Tools|
209
209
|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.|
@@ -356,7 +356,7 @@ Validation|Device to be validated through toolset to ensure the device supports
|Description|The purpose of this test is to validate that authorized code runs with least privilege.|
359
+
|Description|The purpose of this requirement is to validate that authorized code runs with least privilege.|
360
360
|Validation Type|Manual/Tools|
361
361
|Validation|Device to be validated through toolset to ensure that code integrity is enabled by validating dm-verity and IMA|
362
362
|Resources||
@@ -447,7 +447,7 @@ Validation|Device to be validated through toolset to ensure the device supports
447
447
|Name|SecuredCore.Policy.Manageability.Reset|
448
448
|:---|:---|
449
449
|Status|Required|
450
-
|Description|The purpose of this test is to validate the device against 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.|
450
+
|Description|The purpose of this requirement is to validate the device against 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.|
451
451
|Validation Type|Manual/Tools|
452
452
|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.|
453
453
|Resources||
@@ -507,7 +507,6 @@ Additional considerations for Azure Sphere are provided as an application note h
507
507
|:---|:---|:---|
508
508
|Status|Required|2023|
509
509
|Description|The purpose of the requirement is to validate the device identify is rooted in hardware.||
510
-
|Requirements dependency|||
511
510
|Validation Type|Pre-validated, no additional validation is required||
512
511
|Validation|Provided by Microsoft||
513
512
|Resources|[Setup auto provisioning with DPS](../iot-dps/quick-setup-auto-provision.md)||
@@ -552,7 +551,6 @@ Additional considerations for Azure Sphere are provided as an application note h
552
551
|:---|:---|:---|
553
552
|Status|Required|2023|
554
553
|Description|The purpose of the requirement is to ensure the device can remotely attest to the Microsoft Azure Attestation service.|
555
-
|Dependency|||
556
554
|Validation Type|Automated|
557
555
|Validation|Provided by Microsoft|
558
556
|Resources||
@@ -568,7 +566,7 @@ Additional considerations for Azure Sphere are provided as an application note h
568
566
|Validation|Provided by Microsoft|
569
567
|Resources||
570
568
571
-
## Linux Configuration Requirements
569
+
## Sphere OS Configuration Requirements
572
570
573
571
---
574
572
|Name|SecuredCore.Encryption.Storage|Sphere|
@@ -596,10 +594,9 @@ Additional considerations for Azure Sphere are provided as an application note h
|Description|The purpose of this test is to validate that authorized code runs with least privilege.|
597
+
|Description|The purpose of this requirement is to validate that authorized code runs with least privilege.|
600
598
|Validation Type|Automated|
601
599
|Validation|Provided by Microsoft|
602
-
|Resources||
603
600
604
601
---
605
602
</br>
@@ -610,7 +607,6 @@ Additional considerations for Azure Sphere are provided as an application note h
610
607
|Description|The purpose of the requirement is to validate that applications accepting input from the network are not running with elevated privileges.|
611
608
|Validation Type|Automated|
612
609
|Validation|Provided by Microsoft|
613
-
|Resources||
614
610
615
611
---
616
612
</br>
@@ -621,7 +617,6 @@ Additional considerations for Azure Sphere are provided as an application note h
621
617
|Description|The purpose of this requirement is to validate that applications cannot connect to endpoints that have not been authorized.|
622
618
|Validation Type|Automated|
623
619
|Validation|Provided by Microsoft|
624
-
|Resources||
625
620
626
621
627
622
## Sphere Software/Service Requirements
@@ -641,10 +636,8 @@ Additional considerations for Azure Sphere are provided as an application note h
641
636
|:---|:---|:---|
642
637
|Status|Required|2023|
643
638
|Description|The purpose of this requirement is to validate the device supports remote adiministration via service-based configuration control.|
644
-
|Dependency||
645
639
|Validation Type|Automated|
646
640
|Validation|Provided by Microsoft|
647
-
|Resources||
648
641
649
642
---
650
643
</br>
@@ -655,7 +648,6 @@ Additional considerations for Azure Sphere are provided as an application note h
655
648
|Description|The purpose of the requirement is to validate the device can receive and update its firmware and software.|
656
649
|Validation Type|Automated|
657
650
|Validation|Provided by Microsoft|
658
-
|Resources||
659
651
660
652
---
661
653
</br>
@@ -664,10 +656,8 @@ Additional considerations for Azure Sphere are provided as an application note h
664
656
|:---|:---|:---|
665
657
|Status|Required|2023|
666
658
|Description|The purpose of the requirement is to validate that the system conforms to a baseline security configuration|
667
-
|Dependency|azure-osconfig|
668
659
|Validation Type|Automated|
669
660
|Validation|Provided by Microsoft|
670
-
|Resources||
671
661
672
662
---
673
663
</br>
@@ -678,7 +668,6 @@ Additional considerations for Azure Sphere are provided as an application note h
678
668
|Description|The purpose of the requirement is to validate that updates must be signed.|
0 commit comments