Skip to content

Commit b53ced4

Browse files
committed
Polishing the draft
1 parent e9bd661 commit b53ced4

File tree

2 files changed

+3
-5
lines changed

2 files changed

+3
-5
lines changed

articles/security-center/custom-security-policies.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -71,15 +71,13 @@ As discussed in [the Azure Policy documentation](https://docs.microsoft.com/azur
7171

7272
The built-in recommendations supplied with Azure Security Center include details such as severity levels and remediation instructions. If you want to add this type of information to your custom recommendations so that it appears in the Azure Portal or wherever you access your recommendations, you'll need to use the REST API.
7373

74-
The meta data support should be added to the policy definition under ‘securityCenter’ property.
75-
7674
These are the types of information you can add:
7775

7876
- **RemediationDescription** – String
7977
- **Severity** – Enum [Unknown, Low, Medium, High]
80-
- **UserImpact** - Enum [Unknown, Low, Moderate, High]
81-
- **ImplementationEffort** - Enum [Unknown, Low, Moderate, High]
82-
- **Threats** – Array of Enum [Unknown, AccountBreach, DataExfiltration, DataSpillage, MaliciousInsider, ElevationOfPrivilege, ThreatResistance, MissingCoverage, DenialOfService]
78+
The metadata should be added to the policy definition under the ‘SecurityCenter’ property, as shown:
79+
80+
![Example of the SecurityCenter property with custom metadata](media/custom-security-policies/custom-policy-metadata.png)
8381

8482
For an example of how to do this, see [this section of the REST API documentation](https://docs.microsoft.com/rest/api/securitycenter/assessmentsmetadata/createinsubscription#examples).
8583

6.55 KB
Loading

0 commit comments

Comments
 (0)