Key takeaways
- CIS Control 8 has 12 safeguards, and three of them (8.1 to 8.3) are in Implementation Group 1.
- IG1 asks for a documented logging process, logging enabled across assets, and adequate log storage.
- Retention for at least 90 days (8.10) and weekly log reviews (8.11) start at Implementation Group 2.
- As of November 2026, Purview Audit (Standard) keeps records 180 days by default, but Entra sign-in logs last only 7 or 30 days.
- The FTC Safeguards Rule requires covered firms to monitor and log authorized user activity.
What does CIS Control 8 audit log management require?
Control 8, CIS's audit log management control, asks a firm to "collect, alert, review, and retain audit logs of events that could help detect, understand, or recover from an attack." In CIS Controls v8.1 it has 12 safeguards, and only three of them sit in Implementation Group 1 (IG1), the essential hygiene tier most small firms start with.
The three IG1 safeguards are short:
- Safeguard 8.1: establish and maintain a documented audit log management process that defines the firm's logging requirements, reviewed annually or when significant changes occur.
- Safeguard 8.2: make sure logging is enabled across enterprise assets, as that process defines.
- Safeguard 8.3: make sure logging destinations keep enough storage to comply with the process.
Implementation Group 2 adds eight more: time synchronization (8.4), detailed logs on assets that hold sensitive data (8.5), DNS, URL and command-line logs (8.6 to 8.8), centralized collection (8.9), retention for a minimum of 90 days (8.10) and log reviews on a weekly, or more frequent, basis (8.11). Collecting service provider logs (8.12) is IG3 only. The full wording is in the CIS Control 8 assessment specification.
Why do audit logs matter to a regulated firm?
Audit logs are the record that answers who did what, and when, after something goes wrong. Without them, a firm cannot show an examiner, an insurer or its board what was accessed, and it may not be able to narrow who needs to be notified.
Some rules address logging directly. The FTC Safeguards Rule, which covers non-bank financial firms such as tax preparers, mortgage brokers and auto dealers, requires at 16 CFR 314.4(c)(8) controls "designed to monitor and log the activity of authorized users and detect unauthorized access or use of, or tampering with, customer information by such users."
For SEC-registered investment advisers and broker-dealers, the amended Regulation S-P requires a written incident response program reasonably designed to detect, respond to and recover from unauthorized access to or use of customer information. Logs are how a firm detects that access and works out its scope.
The CIS Controls also carry weight outside regulated industries. In California they are the usual starting point for what reasonable security means.
Which logs should a small firm turn on first?
A small firm should turn on the logs that cover identity, email and files first, because that is where an attacker acts and where client data lives. For most small firms that means Microsoft 365, the endpoints and the firewall.
- Microsoft Entra sign-in and audit logs: who signed in, from where, and which administrative changes were made.
- The Microsoft Purview audit log: mailbox access, file downloads and sharing, and inbox rule changes across Exchange, SharePoint and OneDrive.
- Endpoint detection and response logs: blocked threats, suspicious processes and isolation actions.
- Firewall and DNS filtering logs: outbound connections and blocked domains.
- Line-of-business systems: the portfolio, tax or practice management platform's own user activity log, where one exists.
Write this list into the Safeguard 8.1 process document. Safeguard 8.2 is then measured against it: each source the process names should actually be logging.
Do not assume Microsoft 365 auditing is on. In its guide to turning auditing on or off, Microsoft states that auditing is not enabled by default for its small and medium business licenses, including Business Premium, and says to verify the setting. That check is the simplest Safeguard 8.2 test a firm can run.
How long do Microsoft 365 logs last by default?
By default, Microsoft 365 keeps audit records for 180 days in Microsoft Purview Audit (Standard), according to Microsoft's auditing overview, and keeps Entra sign-in and audit logs for 7 days on Entra ID Free or 30 days on P1 or P2, according to Microsoft Entra data retention. Those are the defaults as of November 2026, and they are shorter than most firms assume.
The Entra gap matters most. Sign-in logs are the first place an investigator looks after a suspected account takeover, and an intrusion may not be found until weeks after it began. If the firm's process calls for 90 days or more, the IG2 bar in Safeguard 8.10, Entra logs have to be routed to storage the firm controls. Upgrading a license later does not bring back older records.
Audit (Premium) keeps Entra ID, Exchange, OneDrive and SharePoint records for one year by default, and Microsoft offers a 10-year retention add-on for users who need it. Neither is retroactive. Safeguard 8.3 is the IG1 check here: a log that rolls over before anyone needs it does not meet the firm's own process.
Do you need a SIEM to meet Control 8 on a budget?
A small firm does not need a SIEM to meet Control 8 at Implementation Group 1. A SIEM is the example tool for centralizing logs under Safeguard 8.9, which starts at IG2. A small firm can meet Safeguards 8.1 to 8.3 with native logging, a written process and an export of short-lived logs to low-cost storage.
Central collection earns its cost when the firm wants alerting and weekly reviews without someone reading raw logs by hand. Budget options, roughly in order:
- Use what is already licensed: turn on Purview auditing and confirm Entra sign-in logging in the existing Microsoft 365 tenant.
- Route Entra sign-in and audit logs to an Azure storage account or Log Analytics workspace with a retention setting that matches the written process.
- Use the alerting already built into the endpoint and firewall tools the firm pays for.
- Bring in a managed log review service once weekly reviews are required and no one in-house has the time.
What should you do this quarter?
Five steps get a small firm to IG1 for Control 8 and set up the move to IG2.
- Write a one-page audit log management process: what is logged, where it is stored, how long it is kept and who reviews it. CIS publishes an audit log management policy template geared toward IG1.
- Verify that Purview auditing is on and run a test search for a known event, such as your own sign-in.
- Route Entra sign-in and audit logs past the 7 or 30 day default.
- Check storage and retention on the firewall, endpoint tools and line-of-business systems against the process.
- Set a review rhythm and record each review. Weekly is the IG2 standard in Safeguard 8.11.
Logging works best alongside the rest of the IG1 safeguards, especially monthly stale account reviews. A log is easier to read when you know which accounts should exist.
How does s90 help?
s90 sets up and maintains audit logging for small firms through its CIS Controls package: logging across Microsoft 365, endpoints and network devices, a documented process for your evidence binder, and retention long enough to answer questions after the fact. That matters the day an examiner, insurer or your board asks who opened a client file last quarter. Our agreements include 24-hour evidence production, so when an examiner or insurer asks for records, you have them. If you want to know whether your current log retention would hold up in an incident review, ask us for a quick look.




