Security log management: Event logging best practices for a small business
A client calls to say they received an invoice from your accounting manager’s mailbox with new bank details. The first questions are obvious: when did someone get in, from where, and what did they read, forward or download? Whether you can answer depends on security log management, meaning what you logged and whether those logs still exist.
Event logging records what happens across your systems, with a timestamp, the user or device involved and the outcome. NIST describes log management as generating, transmitting, storing, accessing and disposing of log data, used to investigate incidents, find operational problems and keep records for as long as required. It decides whether an incident stays contained or turns into notifying every client because you can’t prove what wasn’t touched.
Talk to an advisor
Ask about your own setup.
We ask what you’re trying to accomplish and tell you what we’d look at first. It costs nothing to talk, and no price comes up on this call.
How security log management works
Logs come from many places: Microsoft 365 and Entra ID sign-ins, Windows computers and servers, firewalls, VPN or remote access gateways, endpoint security tools, line-of-business applications and backups. Each one records its own events. The value comes from three uses.
Detection
Unusual sign-ins, new mailbox forwarding rules or mass downloads show up in logs before any other symptom.
Investigation
Logs show what an intruder did, which determines what you have to report and to whom.
Compliance
The FTC Safeguards Rule requires covered financial firms to implement controls to monitor and log the activity of authorized users and detect unauthorized access or tampering. The HIPAA Security Rule requires mechanisms that record and examine activity in systems containing electronic protected health information.
What to log first
You don’t need to record every keystroke. Start with the events that reveal account takeovers, data theft and tampering.

- Sign-ins: successes, failures, MFA prompts, new locations or devices, and lockouts.
- Account changes: new users, password resets, new MFA methods, group membership and admin role changes.
- Email activity: new inbox rules, forwarding to outside addresses and mailbox access by other users.
- Access to sensitive data: file access, sharing links and bulk downloads in SharePoint, OneDrive and file servers.
- System changes: software installs, security tool changes, firewall rule changes and disabled logging.
- Security alerts from endpoint, email and firewall tools.
- Backup activity, especially deletions and failed jobs.
Once these are flowing and someone reviews them, expand to application logs, database access and DNS queries. More data than anyone can review only adds noise.
Event logging best practices
Bring logs together
Logs scattered across a firewall, three servers and Microsoft 365 are hard to connect. A SIEM (security information and event management) system or a managed detection service collects them in one place, so a failed VPN login, a new inbox rule and a large download by the same account read as one story.
Protect them from tampering
Attackers try to delete logs to cover their tracks. Send logs off the device they come from, limit who can change or delete them, and use storage that can’t be altered once written where possible.
Keep the clocks in sync
If your firewall, servers and cloud services disagree about the time, building a timeline is painful. Sync every system to a reliable time source.
Include the edge
Firewalls and remote access gateways often keep only a little history on the device itself, and those are the logs you need when an attacker comes in through a VPN account or an unpatched firewall. Forward them to your central store, and log remote access sign-ins, configuration changes and blocked connections.
How long to keep logs
Long enough to investigate an incident nobody noticed right away, and long enough to satisfy your regulators, contracts and cyber insurer. A few weeks isn’t enough. In Microsoft 365, Audit (Standard) keeps audit records for 180 days. Audit (Premium), included with E5 licensing, keeps Entra ID, Exchange, OneDrive and SharePoint records for one year by default, and up to 10 years with an add-on. On a business plan, exporting logs to a SIEM or separate storage is the usual way to keep them longer.
Check that logging is actually on before you plan retention. In the Microsoft 365 tenants we review, auditing is one of the settings we regularly find turned off. HIPAA doesn’t set a specific log retention period, though it does require keeping required policies and documentation for six years. Write your decision into your security policy and your compliance documentation: what you keep, where, and for how long.
Make sure someone is watching
247 days
Average time to identify and contain a breach in IBM’s Cost of a Data Breach Report 2026, the first increase in five years
That gap is a monitoring problem. If no one sees the evidence, the attacker stays longer, and longer breaches cost more.
- 01Alert on high-risk events: impossible-travel sign-ins, new forwarding rules, admin role changes, disabled security tools and mass deletions.
- 02Review sign-in and admin activity on a schedule, along with after an incident.
- 03Group related events across systems into one investigation.
- 04Cover nights and weekends, when many attacks run.
- 05Test it with a tabletop exercise. Could you answer “what did they access?” from your logs today?
For our clients, email sign-in monitoring weighs a mix of signals, and it has caught real takeover attempts, including password spraying and business email compromise. When it flags one, we contain the account within the hour. Every client also has a 24/7 security operations center reviewing alerts, and it can isolate a device when something looks wrong. Our post on data breach response covers what happens next.
Case file: OCR faulted a health network for not reviewing activity
What the record shows
On October 29, 2026, HHS’s Office for Civil Rights announced an $800,000 settlement with Lehigh Valley Health Network (LVHN), which it called its 22nd ransomware enforcement action (HHS). OCR said the attack affected the protected health information of 248,359 people.
The resolution agreement says LVHN’s malware detection tools flagged suspicious activity in February 2023, in the systems of a physician group LVHN acquired in 2021 (resolution agreement). Among the potential violations OCR listed was a failure to “implement procedures to regularly review records of information system activity, such as audit logs, access reports, and security incident tracking reports.” OCR also listed no accurate and thorough risk analysis and late breach notice. The agreement states: “This Agreement is not an admission of liability by LVHN.” The three-year corrective action plan requires a policy for information system activity review.
OCR Director Paula M. Stannard said failing to do a risk analysis and regularly review system activity “makes regulated entities attractive targets for cyberattacks.”
What we don’t know
The agreement doesn’t say how the attackers got in, whether the acquired group’s logs existed and went unread or were never collected, or how late the notices were.
Questions for your office
- 01OCR’s finding was about review, not collection. Who in your office looks at sign-in and access logs, and on what schedule?
- 02The activity was in an acquired group’s systems. When you added a location or bought a practice, did anyone review that network’s accounts and logging before connecting it?
- 03OCR also listed late notice. If your logs showed a breach on a Friday, who would decide who gets told, and by when?
How this could happen in an office like yours
Illustrations only, not a description of what happened at LVHN.
- Logging is on, but alerts go to a shared mailbox nobody owns. What we would have done: route alerts to a named person and review them on a set schedule.
- A practice buys another office and joins the networks over a weekend, and the old office’s accounts keep working. What we would have done: review the new network’s accounts and turn on the same logging before connecting it.
Louisiana’s breach law asks every business holding residents’ personal information to “implement and maintain reasonable security procedures and practices” (La. R.S. 51:3074). Reviewing who signed in, and from where, is part of that for any office, not only healthcare.
Case log
- October 29, 2026: HHS OCR settlement with Lehigh Valley Health Network (HHS; resolution agreement).
Try answering that client’s questions from your logs today, before an incident forces the test. Book a 15-minute call and we’ll look at what you record and how long it lasts. It is part of our cybersecurity services.
Frequently asked questions
What is security log management?
Security log management is collecting, protecting, keeping and reviewing the records your systems create about sign-ins, account changes, file access and security alerts. NIST describes it as generating, transmitting, storing, accessing and disposing of log data. Done well, it lets you spot an account takeover early and answer what an intruder accessed, which decides what you have to report and to whom.
How long should security logs be kept?
Long enough to investigate an incident nobody noticed right away, and long enough to meet your regulators, contracts and cyber insurer, so a few weeks isn’t enough. Microsoft 365 Audit (Standard) keeps records for 180 days, and Audit (Premium) keeps them for a year by default. HIPAA doesn’t set a log retention period, so write your decision into your security policy.
Is Microsoft 365 audit logging turned on by default?
Microsoft says Audit (Standard) is enabled by default for most Microsoft 365 organizations, but confirm it in the Purview portal anyway. In the tenants we review, auditing is one of the settings we regularly find turned off. Check mailbox auditing and retention settings too, since standard audit records are kept for 180 days unless you export them or license longer retention.
Do small businesses need a SIEM?
Not necessarily their own. A SIEM (security information and event management) system collects logs from your firewall, servers and Microsoft 365 in one place so related events read as one story. Many small businesses get the same result through a managed detection service that collects and reviews logs around the clock, without buying and staffing a SIEM themselves.
Sources
- NIST SP 800-92 Rev. 1 (initial public draft), Cybersecurity Log Management Planning Guide
- eCFR, 16 CFR 314.4, Safeguards Rule elements
- eCFR, 45 CFR 164.312, HIPAA technical safeguards
- Microsoft Learn, Learn about auditing solutions in Microsoft Purview
- Microsoft Learn, Manage audit log retention policies
- Baker Donelson, Ten takeaways from IBM’s 2026 Cost of a Data Breach Report
- eCFR, 45 CFR 164.316, HIPAA policies and documentation requirements
- HHS, OCR settles ransomware investigation with Lehigh Valley Health Network, October 29, 2026
- HHS, LVHN resolution agreement and corrective action plan
- La. R.S. 51:3074
Next step
Let us handle this for you.
We tell you which rules apply, put safeguards in place and hand you the policies.
- 15 minutes
Tell us which question brought you here and how your office runs.
We’ll tell you how it applies to you and what we’d look at first.
If we’re not the right fit, we’ll say so.
