This post walks through pragmatic steps for configuring a SIEM and log aggregation pipeline to reliably detect unauthorized use, map detections to the Compliance Framework requirements (NIST SP 800-171 Rev.2 / CMMC 2.0 Level 2 - SI.L2-3.14.7), and produce the evidence small businesses need for audits and incident response.
Understanding the control and objectives
SI.L2-3.14.7 focuses on the continuous monitoring capability to identify unauthorized use of systems and data — i.e., detecting access, privilege escalation, data movement, or actions outside approved patterns. For compliance, your SIEM implementation must collect the right telemetry, produce repeatable detections, and retain evidence demonstrating that unauthorized use is identified and handled according to your policy. Key objectives include: comprehensive source coverage (endpoints, servers, network, cloud, identity), time-synchronized logs, correlation to identify sequences of activity, and auditable alerting and response records.
Implementation steps: collect, aggregate, and centralize logs
Technical details: collectors, transport, and formats
Start by inventorying log sources and creating a collection map: Windows Event Logs (Security/PowerShell/Process Creation), Linux auditd/syslog, network devices (firewalls, VPNs, switches), cloud (AWS CloudTrail, Azure Activity Logs, Office365), identity providers (Azure AD, Okta), and file repository audit logs (SharePoint, SFTP, Git). Install forwarders/collectors appropriate to each source: Windows Event Forwarding (WEF) or Winlogbeat/NXLog for Windows, Filebeat/rsyslog for Linux, and native cloud connectors for CloudTrail/CloudWatch. Use TLS/TCP (syslog-ng or TLS-enabled syslog) or HTTPS ingestion to protect transport. Normalize timestamps and ensure NTP is enforced across all hosts. Standardize on common message formats where possible (CEF, LEEF, JSON) to simplify parsing and correlation.
Normalization, enrichment, retention, and integrity
Normalize fields such as username, source_ip, dest_ip, event_type, and process_name so correlation rules can use consistent field names. Enrich logs with asset owner, business unit, and classification tags (is_cui_host=true) at collection time or in the SIEM using CMDB lookups. Implement log integrity and protection: write-once storage (WORM or immutable object storage), encrypt logs at rest, and restrict SIEM admin permissions. For retention, document a policy aligned with contracts and internal risk tolerance — a common small-business baseline is online retention for 90 days with archived (cold) storage for 1+ year, but adjust to client/contract requirements. Ensure you record chain-of-custody metadata (who accessed SIEM, exported logs, and when) for audit trails.
Detection use cases and correlation rules
Prioritize use cases that directly map to unauthorized use: successful logins outside normal hours, impossible travel (same user authenticating from distant IPs within short window), elevation of privilege (group membership changes, new admin account), large outbound transfers from CUI repositories, new device connecting to internal services, and suspicious command-line usage (PowerShell with encoded commands). Example detection rule (Splunk SPL): index=wineventlog EventCode=4625 | stats count by src_ip, AccountName | where count > 5 to detect repeated failed logins. Example threshold rule for Elastic: a rule that fires when count of event.action:authentication_failure for a user in 5 minutes > 10. Correlate authentication events with process creation and network egress to detect sequences (login → access to CUI repo → large outbound transfer).
Alerting, prioritization and tuning
Configure alerts with severity and playbook links. Tie high-confidence detections to immediate notifications (email + ticket creation + Slack/PagerDuty) and lower-confidence alerts to analyst queues. To reduce false positives: build baselines of normal activity per user or device (e.g., normal work hours, regular source IPs), whitelist known automated service accounts, and review rule thresholds after two-week tuning windows. Map each detection to an incident response playbook: who to contact, steps to isolate the host, evidence collection commands, and remediation actions.
Operational best practices and compliance tips
Document the mapping from SI.L2-3.14.7 to your implemented controls and artifacts — include a log-source matrix, detection rules list, tuning history, and sample incident records. Use MITRE ATT&CK to tag detections (e.g., T1078 for valid accounts) — this helps auditors and security teams understand intent. Perform quarterly review of rule effectiveness, run tabletop exercises that validate alert-to-response timelines, and periodically re-run ingestion tests to ensure new or changed log sources are captured. Limit SIEM admin and read/write privileges via RBAC and enforce MFA for access to the SIEM console. Keep a secure copy of raw logs outside the production SIEM to satisfy integrity and evidence needs in case the SIEM is compromised.
Risk of not implementing this requirement
Failing to implement centralized log aggregation and SIEM detection substantially increases the risk that unauthorized use goes unnoticed: attackers can persist, escalate privileges, and exfiltrate CUI without detection, leading to data breaches, lost contracts, reputational damage, and regulatory penalties. For small businesses contracting with the government, undetected compromise can lead to immediate contract termination and debarment. Operationally, lack of logs makes forensic investigations slow or impossible — you lose the ability to reconstruct timelines and scope of compromise.
Small-business scenario and a concrete example
A small defense subcontractor with ~60 employees implemented an Elastic stack: Winlogbeat on Windows endpoints, Filebeat on Linux servers, CloudTrail ingestion for AWS, and an rsyslog forwarder for on-prem firewalls. They created these prioritized rules: external RDP access to domain controllers, any admin-group modification events, and file-downloads from the CUI file share larger than 250 MB. When an after-hours RDP session from a foreign IP triggered an alert, the playbook required immediate host isolation, password resets for affected accounts, and export of raw logs before remediation. That structured flow enabled the company to contain the incident within hours and produce logged evidence for the contracting officer, demonstrating compliance with SI.L2-3.14.7.
Summary: meet SI.L2-3.14.7 by inventorying and centralizing log sources, using secure collectors and normalized schemas, implementing targeted correlation rules for unauthorized-use scenarios, and operationalizing alerts with documented playbooks and retention policies; doing so reduces detection gaps, provides auditable evidence, and aligns your small business with NIST SP 800-171 / CMMC 2.0 Level 2 expectations.
