Control: 3.6 Ensure a notification is configured for IAM group changes
Description
It is recommended to setup an Event Rule and Notification that gets triggered when IAM Groups are created, updated or deleted. Event Rules are compartment scoped and will detect events in child compartments, it is recommended to create the Event rule at the root compartment level.
Remediation
From Console
- Go to the Events Service page.
- Select the
compartmentthat should host the rule. - Click
Create Rule. - Provide a
Display NameandDescription. - Create a Rule Condition by selecting
Identityin the Service Name Drop-down and selectingGroup – Create,Group – DeleteandGroup – Update. - In the
Actionssection selectNotificationsas Action Type. - Select the
Compartmentthat hosts the Topic to be used. - Select the
Topicto be used. - Optionally add Tags to the Rule.
- Click
Create Rule.
From Command Line
- Find the
topic-idof the Event Rule which should be used for sending Notifications by using the topicnameandCompartment OCID.
oci ons topic list --compartment-id=<compartment OCID> --all --query "data [?name=='<topic_name>']".{"name:name,topic_id:\"topic-id\""} --output table
- Create a JSON file to be used when creating the Event Rule. Replace topic id, display name, description and compartment OCID.
{ "actions": { "actions": [ { "actionType": "ONS", "isEnabled": true, "topicId": "<topic id>" }] }, "condition": { "eventType": ["com.oraclecloud.identitycontrolplane.creategroup", "com.oraclecloud.identitycontrolplane.deletegroup", "com.oraclecloud.identitycontrolplane.updategroup"], "data":{} }, "displayName": "<display name>", "description": "<description>", "isEnabled": true, "compartmentId": "compartment OCID"}
- Create the actual event rule
oci events rule create --from-json file://event_rule.json
- Note in the JSON returned that it lists the parameters specified in the JSON file provided and that there is an OCID provided for the Event Rule
Usage
Run the control in your terminal:
powerpipe control run oci_compliance.control.cis_v120_3_6Snapshot and share results via Turbot Pipes:
powerpipe loginpowerpipe control run oci_compliance.control.cis_v120_3_6 --shareSQL
This control uses a named query:
select distinct t.id as resource, case when c.name is not null then 'skip' when condition -> 'eventType' ?& array ['com.oraclecloud.identitycontrolplane.creategroup', 'com.oraclecloud.identitycontrolplane.deletegroup', 'com.oraclecloud.identitycontrolplane.updategroup'] and a ->> 'actionType' = 'ONS' and t.lifecycle_state = 'ACTIVE' and t.is_enabled then 'ok' else 'alarm' end as status, case when c.name is not null then c.name || ' not a root compartment.' when condition -> 'eventType' ?& array ['com.oraclecloud.identitycontrolplane.creategroup', 'com.oraclecloud.identitycontrolplane.deletegroup', 'com.oraclecloud.identitycontrolplane.updategroup'] and a ->> 'actionType' = 'ONS' and t.lifecycle_state = 'ACTIVE' and t.is_enabled then t.title || ' configured for IAM group changes.' else t.title || ' not configured for IAM group changes.' end as reason , t.region as region, t.tenant_name as tenant , coalesce(c.name, 'root') as compartmentfrom oci_events_rule t left join oci_identity_compartment as c on c.id = t.compartment_id, jsonb_array_elements(actions) as a;