🛡️ Azure Subscription Activity Log Alert for Create Role Assignment does not exist🟢

• Contextual name: 🛡️ Subscription Activity Log Alert for Create Role Assignment does not exist🟢
• ID: /ce/ca/azure/subscription/activity-log-alert-for-create-role-assignment
• Tags:
  • 🟢 Policy with categories
  • 🟢 Policy with type
  • 🟢 Production policy
• Policy Type: COMPLIANCE_POLICY
• Policy Categories: SECURITY

Stats

not available

Logic

• 🧠 prod.logic.yaml🟢
  • 📗 Azure Subscription
  • 🔌 Azure Activity Log Alert - object.extracts.yaml
  • 🔌 Azure Subscription - object.extracts.yaml
  • 🧪 test-data.json

Description

Open File

Description

Create an activity log alert rule that notifies an action group whenever the activity log records the Create role assignment operation in the Administrative category. The rule covers role assignments made at the subscription scope and at every resource group and resource beneath it.

Rationale

A role assignment grants a principal its permissions at the assigned scope, so a new Owner, Contributor or User Access Administrator assignment is a privilege escalation that changes no protected resource. Without an alert, the grant goes unnoticed until the next access review, and the new access can be used and removed before then.

Audit

This policy marks an Azure Subscription as INCOMPLIANT if no current enabled Activity Log Alert covers Administrative / Microsoft.Authorization/roleAssignments/write, has a resolved action group, and covers the subscription root. Category and operation must occur on their matching JSON fields, with no additional Level, Status, Caller, or other filter.

A qualifying alert makes the subscription COMPLIANT. Otherwise, unassessable alert configuration produces UNDETERMINED. Complex or narrower scope strings require manual review and do not prove subscription-wide coverage. Notification recipients and delivery must be verified operationally.

Remediation

Open File

Remediation

Create an enabled Activity Log Alert for Microsoft.Authorization/roleAssignments/write in the Administrative category across the affected subscription. Set the scope to /subscriptions/{{subscription-id}}.

Review existing alerts for this event before creating another. Select a current action group with enabled notification receivers for the responsible team, and review the expected notification volume and any charges for its notification channels.

Use an unused alert-rule name for the command examples. Before editing an existing rule, record its configuration and retain all action groups that are still required.

From Azure Portal

1. Go to Monitor > Alerts and select Create > Alert rule.
2. On the Scope tab, select the affected subscription itself and select Apply.
3. On the Condition tab, select See all signals, choose Create role assignment (Role Assignment), and select Apply.
4. Leave Event level, Status, and Event initiated by set to All. The condition should match only the Administrative category and the specified operation.

... see more

policy.yaml

Open File

Linked Framework Sections

Section	Sub Sections	Internal Rules	Policies	Flags	Compliance
💼 CIS Azure v7.0.0 → 💼 6.1.2.12 Ensure that Activity Log Alert Exists for Create Role Assignment (Automated)			1		no data
💼 Cloudaware Framework → 💼 Alerting and Notification			49		no data