Detection rules › Panther

Wiz User Role Updated Or Deleted

Severity
medium
Group by
id
Log types
Wiz.Audit
Reference
https://www.wiz.io/blog/cloud-security-custom-roles-democratization
Source
github.com/panther-labs/panther-analysis

This rule detects updates and deletions of Wiz user roles.

MITRE ATT&CK coverage

Rule body yaml

AnalysisType: rule
RuleID: Wiz.User.Role.Updated.Or.Deleted
Description: This rule detects updates and deletions of Wiz user roles.
DisplayName: Wiz User Role Updated Or Deleted
Runbook: Verify that this change was planned. If not, revert the change and ensure this doesn't happen again. Review privileges given to accounts to ensure the principle of minimal privilege
Reference: https://www.wiz.io/blog/cloud-security-custom-roles-democratization
Enabled: true
Filename: wiz_user_role_updated_or_deleted.py
Severity: Medium
Reports:
  MITRE ATT&CK:
    - TA0003:T1098.001  # Account Manipulation
LogTypes:
  - Wiz.Audit
DedupPeriodMinutes: 60
Threshold: 1
Tests:
  - Name: DeleteUserRole
    ExpectedResult: true
    Log:
      {
        "id": "671d8e2d-1ca8-47eb-bf1c-d46cd3f0d737",
        "action": "DeleteUserRole",
        "requestId": "a83aba82-c707-4a2f-9761-fe9ee723b703",
        "status": "SUCCESS",
        "timestamp": "2024-07-31T18:09:28.790129Z",
        "actionParameters": {
          "input": {
            "id": "b92c4032-9af8-4e2d-b6dc-3bf2005bb7ad"
          },
          "selection": [
            "__typename",
            "_stub"
          ]
        },
        "userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36",
        "sourceIP": "12.34.56.78",
        "serviceAccount": null,
        "user": {
          "id": "test.user@company.com",
          "name": "user@company.com"
        }
      }
  - Name: CreateUser
    ExpectedResult: false
    Log:
      {
        "id": "220d23be-f07c-4d97-b4a6-87ad04eddb14",
        "action": "CreateUser",
        "requestId": "0d9521b2-c3f8-4a73-bf7c-20257788752e",
        "status": "SUCCESS",
        "timestamp": "2024-07-29T09:40:15.66643Z",
        "actionParameters": {
          "input": {
            "assignedProjectIds": null,
            "email": "testy@company.com",
            "expiresAt": null,
            "name": "Test User",
            "role": "GLOBAL_ADMIN"
          },
          "selection": [
            "__typename",
            {
              "user": [
                "__typename",
                "id"
              ]
            }
          ]
        },
        "userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36",
        "sourceIP": "8.8.8.8",
        "serviceAccount": null,
        "user": {
          "id": "someuser@company.com",
          "name": "someuser@company.com"
        }
      }
  - Name: DeleteUserRole - Fail
    ExpectedResult: false
    Log:
      {
        "id": "671d8e2d-1ca8-47eb-bf1c-d46cd3f0d737",
        "action": "DeleteUserRole",
        "requestId": "a83aba82-c707-4a2f-9761-fe9ee723b703",
        "status": "FAILED",
        "timestamp": "2024-07-31T18:09:28.790129Z",
        "actionParameters": { },
        "userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36",
        "sourceIP": "12.34.56.78",
        "serviceAccount": null,
        "user": {
          "id": "test.user@company.com",
          "name": "user@company.com"
        }
      }

Detection logic

Condition

status eq "SUCCESS"
action in ["DeleteUserRole", "UpdateUserRole"]

Indicators

Each row is a field, operator, and value that the rule matches. The corpus column counts how many other rules in the catalog look for the same combination: high numbers point to widely-used, community-vetted indicators. Blank or 1 shows that the indicator is specific to this rule.

FieldKindValues
actionin
  • DeleteUserRole
  • UpdateUserRole
statuseq
  • SUCCESS

Output fields

Fields the rule emits when it matches. Chronicle authors list these in the outcome block; they appear on the detection and $risk_score drives alerting. Sentinel / Defender XDR rules build them up through project / summarize / extend stages. Sentinel maps these into alert fields via entityMappings and customDetails; Defender XDR custom detections surface them as alert fields directly.

FieldSource
action
source_ipsourceip
event_idid
action_parametersactionparameters