# CIS 8.2 — Collect Audit Logs

- Source: https://support.icompaas.com/support/solutions/articles/a_gen_cis_82_96d70d96bb-cis-82-collect-audit-logs
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [AWS Checks New Version](https://support.icompaas.com/support/solutions/62000112673) › [Detect](https://support.icompaas.com/support/solutions/folders/f_gen_62000112673_detect)
- Last updated: 2026-05-30
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

CIS · Control 8.2 · Priority: critical · Component: Detect

### What this control covers

Collect audit logs. Ensure that logging, per the enterprise's audit log management process, has been enabled across enterprise assets.

### Why it matters

Risk is the language an executive team understands; this control connects technical reality to board-level decisions and budget allocation.

### How to implement

#### AWS

Codify the policy intent as **SCPs, AWS Config conformance packs, and Security Hub standards** so the cloud enforces what the document says.

#### Azure

Codify in **Azure Policy initiatives** (built-in regulatory compliance for CIS, ISO 27001, SOC 2, HIPAA) and assign at management-group level.

#### GCP

Centralize via **Cloud Logging** log sinks at the org level to a **locked log bucket** with 7-year retention. Use **SCC Premium** for posture findings and **Chronicle** for SIEM correlation.

#### Google Workspace

Forward the **Admin, Login, Drive, Token and Mobile** audit logs to Cloud Logging (Workspace BigQuery export). Alert on impossible-travel logins, OAuth-scope grants for high-risk scopes, and external Drive sharing of sensitive labels.

#### GitHub

Stream the **Enterprise audit log** to your SIEM and enable **Audit Log API** alerting on key events: owner changes, IP allowlist edits, secret deletions, repo visibility flips.

#### On-premises

Maintain a policy library with a documented review cadence (annual minimum); store in your GRC tool with attestation tracking. Map each policy to controls so an audit pull cites the exact policy clause.

### Evidence to collect

-   `policy_document` — A signed, version-controlled policy stating leadership intent and the named owner.
-   `infra_scan` — See the iCompaas Evidence library for the canonical source for this evidence type.

Signed policy or standard documents the safeguard. Focus: Collect Audit Logs.

### Quick checklist

-   Ensure — Audit Log Management Process / Logs
-   Log — Audit Log Management Process / Logs
-   Collect Audit — Audit Log Management Process / Logs

### Related articles on this site

-   [Ensure EKS Control Plane Audit Logging is enabled for all log types](https://support.icompaas.com/support/solutions/articles/62000229615-ensure-eks-control-plane-audit-logging-is-enabled-for-all-log-types)
-   [Ensure GuardDuty EKS Audit Log Monitoring Enabled](https://support.icompaas.com/support/solutions/articles/62000235131-ensure-guardduty-eks-audit-log-monitoring-enabled)
-   [Ensure EKS Control Plane Audit Logging is enabled for all log types](https://support.icompaas.com/support/solutions/articles/62000236326-ensure-eks-control-plane-audit-logging-is-enabled-for-all-log-types)
-   [Ensure Redshift cluster has audit logging enabled](https://support.icompaas.com/support/solutions/articles/62000129490-ensure-redshift-cluster-has-audit-logging-enabled)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.