Logs and monitoring

A log records who did what, when and where. Monitoring means someone, or something, actually reads it.

// TECH FOR GRC

What a log line is

A log is a record of an event. A good log line answers five questions:

Who What When Where Result
maria.s changed a firewall rule 2026-10-01 18:03 production account success

Kinds of logs you will meet

  • Audit logs from the cloud: AWS CloudTrail, Azure activity logs, Google Cloud Audit Logs. They record admin actions.
  • Sign-in logs from the identity provider: who logged in, from where, with MFA or not.
  • Application logs from the company's own software.

Logging is not monitoring

Logging means the record exists. Monitoring means something reads it and raises an alert when something looks wrong, such as a login from an unusual country. A SIEM collects logs from many systems and runs those rules. Alerts are only useful if someone triages them, deciding whether each one is an incident.

Three things auditors check

  1. Coverage: is logging on everywhere in scope, in every account and region?
  2. Protection and retention: can admins delete logs? How long are they kept?
  3. Response: show an alert from the period, and what someone did about it.

Time matters

If system clocks disagree, logs cannot be lined up during an investigation. That is why clock synchronisation is a control (ISO A.8.17).

// WHAT IT LOOKS LIKE AS EVIDENCE
CloudTrail on in every region and accountAWS CloudTrail · proves CC7.2, A.8.15, A.5.33
AWS CloudTrailSAMPLE
CloudTrail › Trails › org-audit-trail

org-audit-trail

complyoo-org management (7710 2284 0051)Viewed 2026-10-01 09:22 UTC1
  • LoggingOn2
  • Multi-region trailYes3
  • Apply trail to my organizationEnabled for all accounts
  • Log file validationEnabled4
  • S3 bucketcomplyoo-audit-logs (Object Lock: Compliance, 400 days)
  • Management eventsRead and write
  1. 1Date of capture. For a Type II, take this more than once across the period, or show it was never turned off.
  2. 2Logging is on. This is the control itself.
  3. 3Multi-region. A single-region trail leaves gaps attackers use.
  4. 4Log file validation and Object Lock show the logs are protected from tampering.

Weak version: Single region, in one account only. The auditor will ask about every other region and account, and logging gaps there are a finding.

// FROM A REAL ACCOUNTAWS console, CloudTrail · identifiers blurred
This account has no trail. Event history still shows 90 days of management events, but nothing is kept longer and data events are not recorded. Against a twelve month SOC 2 period, that is a gap.
WeakThis account has no trail. Event history still shows 90 days of management events, but nothing is kept longer and data events are not recorded. Against a twelve month SOC 2 period, that is a gap.
Event history from the same account while these screenshots were made. Every change was made as root. An auditor would ask why the root user does daily work, which is an access question before it is a logging one.
Worth knowingEvent history from the same account while these screenshots were made. Every change was made as root. An auditor would ask why the root user does daily work, which is an access question before it is a logging one.
Admin Activity logs showing who changed whatGoogle Cloud Logging · proves CC7.2, A.8.15
Google Cloud LoggingSAMPLE
Logging › Logs Explorer

Admin Activity audit logs

Project: complyoo-prodQuery run 2026-10-03 11:18 IST1
TimestampPrincipal2MethodResource
2026-10-02 22:41:07deploy@complyoo-prod.iamrun.services.replaceServiceapi
2026-10-02 18:03:55maria.s@complyoo.comSetIamPolicycomplyoo-prod3
2026-10-01 09:12:40david.e@complyoo.comcompute.firewalls.patchallow-lb
  1. 1Query date and project.
  2. 2Each entry names a person or service account.
  3. 3An IAM policy change, exactly the kind of event an auditor traces back to an approved request.

Weak version: A screenshot of the logging settings page only. It shows logging exists, not that anyone reviews what it records.

// FROM A REAL ACCOUNTGoogle Cloud console, Logging and IAM · identifiers replaced
Admin Activity logs: who created the project, which services were turned on, and when billing was linked, each with the person's email and the exact second. Google writes these for every project and they cannot be switched off.
StrongAdmin Activity logs: who created the project, which services were turned on, and when billing was linked, each with the person's email and the exact second. Google writes these for every project and they cannot be switched off.
The same project's Data Access logs: all three types disabled, which is Google's default for most services. Reads of sensitive data leave no trail until someone turns these on.
WeakThe same project's Data Access logs: all three types disabled, which is Google's default for most services. Reads of sensitive data leave no trail until someone turns these on.
// REMEMBER THIS

Logging records. Monitoring notices. You need both.

// CHECK YOURSELF

1. Logging is on, but alerts go to a mailbox nobody reads. Which part fails?

2. Which of these is a cloud audit log?

3. Why do auditors care whether admins can delete logs?