Skip to content

Commit d2db878

Browse files
committed
changing test to requirement
1 parent ba44a81 commit d2db878

File tree

1 file changed

+6
-17
lines changed

1 file changed

+6
-17
lines changed

articles/certification/program-requirements-edge-secured-core.md

Lines changed: 6 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -136,7 +136,7 @@ Validation|Device to be validated through toolset to ensure the device supports
136136
|Name|SecuredCore.Protection.CodeIntegrity|x86/AMD64|Arm64|
137137
|:---|:---|:---|:---|
138138
|Status|Required|2023|2023|
139-
|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.|
140140
|Requirements dependency|HVCI is enabled on the device.|
141141
|Validation Type|Manual/Tools|
142142
|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
203203
|Name|SecuredCore.Policy.Manageability.Reset|
204204
|:---|:---|
205205
|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.|
207207
|Requirements dependency||
208208
|Validation Type|Manual/Tools|
209209
|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
356356
|Name|SecuredCore.Protection.CodeIntegrity|x86/AMD64|Arm64|
357357
|:---|:---|:---|:---|
358358
|Status|Required|2023|2023|
359-
|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.|
360360
|Validation Type|Manual/Tools|
361361
|Validation|Device to be validated through toolset to ensure that code integrity is enabled by validating dm-verity and IMA|
362362
|Resources||
@@ -447,7 +447,7 @@ Validation|Device to be validated through toolset to ensure the device supports
447447
|Name|SecuredCore.Policy.Manageability.Reset|
448448
|:---|:---|
449449
|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.|
451451
|Validation Type|Manual/Tools|
452452
|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.|
453453
|Resources||
@@ -507,7 +507,6 @@ Additional considerations for Azure Sphere are provided as an application note h
507507
|:---|:---|:---|
508508
|Status|Required|2023|
509509
|Description|The purpose of the requirement is to validate the device identify is rooted in hardware.||
510-
|Requirements dependency|||
511510
|Validation Type|Pre-validated, no additional validation is required||
512511
|Validation|Provided by Microsoft||
513512
|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
552551
|:---|:---|:---|
553552
|Status|Required|2023|
554553
|Description|The purpose of the requirement is to ensure the device can remotely attest to the Microsoft Azure Attestation service.|
555-
|Dependency|||
556554
|Validation Type|Automated|
557555
|Validation|Provided by Microsoft|
558556
|Resources||
@@ -568,7 +566,7 @@ Additional considerations for Azure Sphere are provided as an application note h
568566
|Validation|Provided by Microsoft|
569567
|Resources||
570568

571-
## Linux Configuration Requirements
569+
## Sphere OS Configuration Requirements
572570

573571
---
574572
|Name|SecuredCore.Encryption.Storage|Sphere|
@@ -596,10 +594,9 @@ Additional considerations for Azure Sphere are provided as an application note h
596594
|Name|SecuredCore.Protection.CodeIntegrity|Sphere|
597595
|:---|:---|:---|
598596
|Status|Required|2023|
599-
|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.|
600598
|Validation Type|Automated|
601599
|Validation|Provided by Microsoft|
602-
|Resources||
603600

604601
---
605602
</br>
@@ -610,7 +607,6 @@ Additional considerations for Azure Sphere are provided as an application note h
610607
|Description|The purpose of the requirement is to validate that applications accepting input from the network are not running with elevated privileges.|
611608
|Validation Type|Automated|
612609
|Validation|Provided by Microsoft|
613-
|Resources||
614610

615611
---
616612
</br>
@@ -621,7 +617,6 @@ Additional considerations for Azure Sphere are provided as an application note h
621617
|Description|The purpose of this requirement is to validate that applications cannot connect to endpoints that have not been authorized.|
622618
|Validation Type|Automated|
623619
|Validation|Provided by Microsoft|
624-
|Resources||
625620

626621

627622
## Sphere Software/Service Requirements
@@ -641,10 +636,8 @@ Additional considerations for Azure Sphere are provided as an application note h
641636
|:---|:---|:---|
642637
|Status|Required|2023|
643638
|Description|The purpose of this requirement is to validate the device supports remote adiministration via service-based configuration control.|
644-
|Dependency||
645639
|Validation Type|Automated|
646640
|Validation|Provided by Microsoft|
647-
|Resources||
648641

649642
---
650643
</br>
@@ -655,7 +648,6 @@ Additional considerations for Azure Sphere are provided as an application note h
655648
|Description|The purpose of the requirement is to validate the device can receive and update its firmware and software.|
656649
|Validation Type|Automated|
657650
|Validation|Provided by Microsoft|
658-
|Resources||
659651

660652
---
661653
</br>
@@ -664,10 +656,8 @@ Additional considerations for Azure Sphere are provided as an application note h
664656
|:---|:---|:---|
665657
|Status|Required|2023|
666658
|Description|The purpose of the requirement is to validate that the system conforms to a baseline security configuration|
667-
|Dependency|azure-osconfig|
668659
|Validation Type|Automated|
669660
|Validation|Provided by Microsoft|
670-
|Resources||
671661

672662
---
673663
</br>
@@ -678,7 +668,6 @@ Additional considerations for Azure Sphere are provided as an application note h
678668
|Description|The purpose of the requirement is to validate that updates must be signed.|
679669
|Validation Type|Automated|
680670
|Validation|Provided by Microsoft|
681-
|Resources||
682671

683672

684673

0 commit comments

Comments
 (0)