Continuous monitoring, mapped to the rules your customers and auditors ask about.
Every SentinelSMB detection is tagged to the compliance frameworks that apply to your industry. When your auditor, insurer, or enterprise client asks for evidence, you have it.
Framework map
How the rules fit together.
They look different on paper, but they ask for the same evidence: who accessed what, when it happened, and a record you can show. Tap any rule to jump to the details.
Applies to every business, in every industry. The timing clock starts at detection.
One monitoring layer under all of it.
Once you tell us your industry, every detection is tagged to the frameworks that apply to you.
36detection engines
365days of audit trail
Frameworks mapped
Ten frameworks. One monitoring layer.
These are the frameworks we map detections to. You do not need to know which ones apply to your business — the mapping is automatic once you tell us your industry.
ABA Model Rule 1.6
Attorney confidentiality
Lawyers owe a duty of confidentiality to their clients. Rule 1.6 requires reasonable efforts to prevent inadvertent disclosure.
Email forwarding-rule detection helps catch privileged communications leaving the firm
365-day audit trail documents reasonable efforts
IRS Publication 4557
Tax preparer data security
Tax professionals must keep a written information security plan (WISP) under the FTC Safeguards Rule, and IRS Publication 4557 is the IRS guide to building one. SentinelSMB supplies the monitoring evidence a WISP calls for.
Identity engines catch credential theft targeting taxpayer data
Pro subscribers get the WISP template pre-filled with monitoring evidence
FTC Safeguards Rule
Financial institution security
The amended Safeguards Rule (effective June 2023) requires a qualified individual, a written incident response plan, and either continuous monitoring or annual penetration testing with vulnerability scans every six months.
36 engines provide the continuous-monitoring option
Plain-English alerts document incident response in real time
SEC Reg S-P
Adviser & broker notification
The 2024 amendment gives RIAs and broker-dealers 30 days to notify clients of unauthorized access to their sensitive information. Continuous monitoring starts the clock on time.
Detection timestamps anchor the 30-day notification window
Pro quarterly evidence report helps with SEC exam prep
NAIC Model Law 668
Insurance producer security
28 jurisdictions have adopted NAIC Model Law 668, which requires insurance licensees to maintain an information security program.
5-minute scan cycles support the program’s monitoring element
Risk assessment evidence generated from real detection data
CMMC 2.0 Level 2
Defense contractor compliance
Federal contractors handling Controlled Unclassified Information must meet CMMC 2.0 Level 2, which maps to the 110 NIST SP 800-171 security controls.
Monitoring supports 800-171 requirements 3.14.6 and 3.14.7 (monitor systems for attacks and unauthorized use)
Identity engines support requirement 3.1.1 (limit access to authorized users)
GLBA Safeguards
Financial institution obligations
Financial institutions under the Gramm-Leach-Bliley Act must protect customer nonpublic personal information (NPI).
Email and data engines detect NPI exfiltration paths
Access-control logs retained for 365 days
NY DFS 23 NYCRR 500
New York cybersecurity regulation
Financial services companies regulated by NY DFS must comply with 23 NYCRR 500, including access-control, audit-trail, and user-activity monitoring requirements.
Section 500.6 audit trail supported by 365-day retention
Section 500.14 user-activity monitoring supported by identity engines
NIST SP 800-171
CUI protection baseline
The 110 NIST 800-171 controls protect Controlled Unclassified Information in nonfederal systems. Foundation for CMMC 2.0 and many federal contract clauses.
AU (Audit and Accountability) family supported by audit retention
SI (System and Information Integrity) family supported by detection engines
State Breach Notification
All 50 states
Every US state requires notification to affected individuals when personal information is accessed without authorization. The timing clock starts at detection.
Accurate detection timestamps anchor each state's notification clock
You tell us your industry once. From then on, every detection is tagged to the frameworks that matter to you. No manual mapping, no consultant required.
1. Detection happens
One of the 36 engines flags an event — a foreign sign-in, a new forwarding rule, an OAuth consent grant. The detection carries a timestamp, severity score, and attack-pattern label.
2. Framework tagging
The detection is matched against the frameworks registered for your industry. A credential-theft event for a law firm gets tagged ABA 1.6. The same event for an RIA gets tagged SEC Reg S-P and GLBA. Automatic.
3. Evidence-ready
Every tagged detection becomes part of your live compliance record. Pro subscribers get the Cyber Insurance Evidence Report quarterly — a 7-page audit-ready PDF built from real detection data.
Pro Feature
Cyber Insurance Evidence Report
The 7-page quarterly PDF generated from your real monitoring data — formatted for cyber insurance underwriters, auditors, and enterprise-client security questionnaires. Every framework mapping included, every detection timestamp referenced, every audit trail linked.