Skip to content

Commit 8a2963f

Browse files
committed
Custom policy metadata instructions
1 parent 13e6f0a commit 8a2963f

File tree

1 file changed

+17
-1
lines changed

1 file changed

+17
-1
lines changed

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

Lines changed: 17 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ To help secure your systems and environment, Azure Security Center generates sec
1919

2020
With this feature, you can add your own *custom* initiatives. You'll then receive recommendations if your environment doesn't follow the policies you create. Any custom initiatives you create will appear alongside the built-in initiatives in the regulatory compliance dashboard described in the tutorial [Improve your regulatory compliance](security-center-compliance-dashboard.md).
2121

22-
As discussed [here](https://docs.microsoft.com/azure/governance/policy/concepts/definition-structure#definition-location) in the Azure Policy documentation, when you specify a location for your custom initiative, it must be a management group or a subscription.
22+
As discussed in [the Azure Policy documentation](https://docs.microsoft.com/azure/governance/policy/concepts/definition-structure#definition-location), when you specify a location for your custom initiative, it must be a management group or a subscription.
2323

2424
## To add a custom initiative to your subscription
2525

@@ -67,6 +67,22 @@ As discussed [here](https://docs.microsoft.com/azure/governance/policy/concepts/
6767

6868
[![Custom recommendations](media/custom-security-policies/custom-policy-recommendations.png)](media/custom-security-policies/custom-policy-recommendations-in-context.png#lightbox)
6969

70+
## Enhancing your custom recommendations with detailed information
71+
72+
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.
73+
74+
The meta data support should be added to the policy definition under ‘securityCenter’ property.
75+
76+
These are the types of information you can add:
77+
78+
- **RemediationDescription** – String
79+
- **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]
83+
84+
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).
85+
7086

7187
## Next steps
7288

0 commit comments

Comments
 (0)