Control: 4.7 Ensure a notification is configured for user changes
Description
It is recommended to setup an Event Rule and Notification that gets triggered when IAM Users are created, updated, deleted, capabilities updated, or state updated. 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.
Users use or manage Oracle Cloud Infrastructure resources. Monitoring and alerting on changes to Users will help in identifying changes to the security posture.
Remediation
From Console
- Using the search box to navigate to
events. - Navigate to the
rulespage. - Select the
compartmentthat should host the rule. - Click
Create Rule. - Provide a
Display NameandDescription. - Create a
Rule Conditionby selectingIdentityin theService NameDrop-down and selecting:User – Create,User – Delete,User – Update,User Capabilities – Update,User State – 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 CLI
- 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.CreateUser", "com.oraclecloud.identityControlPlane.DeleteUser", "com.oraclecloud.identityControlPlane.UpdateUser"], "com.oraclecloud.identityControlPlane.UpdateUserCapabilities", "com.oraclecloud.identityControlPlane.UpdateUserState"], "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_v200_4_7Snapshot and share results via Turbot Pipes:
powerpipe loginpowerpipe control run oci_compliance.control.cis_v200_4_7 --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.createuser', 'com.oraclecloud.identitycontrolplane.deleteuser', 'com.oraclecloud.identitycontrolplane.updateuser', 'com.oraclecloud.identitycontrolplane.updateusercapabilities', 'com.oraclecloud.identitycontrolplane.updateuserstate'] 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.createuser', 'com.oraclecloud.identitycontrolplane.deleteuser', 'com.oraclecloud.identitycontrolplane.updateuser', 'com.oraclecloud.identitycontrolplane.updateusercapabilities' 'com.oraclecloud.identitycontrolplane.updateuserstate'] and a ->> 'actionType' = 'ONS' and t.lifecycle_state = 'ACTIVE' and t.is_enabled then t.title || ' configured for IAM user changes.' else t.title || ' not configured for IAM user 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;