Email authentication (SPF, DKIM, DMARC)
What we can show. The preview and a saved scan show whether SPF and DMARC are published, and whether DMARC is p=none, quarantine, or reject. The preview checks seventeen built-in DKIM selectors, one optional selector you type, MTA-STS, and TLS-RPT, and shows a score out of 100. Saved DKIM, MTA-STS, and TLS-RPT findings are Pro checks.
What we cannot show. That every outbound message is signed, or that a selector you did not check is absent.
TLS on the website or app hostname
What we can show. Whether port 443 presents a certificate that verifies for the hostname you enter, plus the issuer and expiry when the handshake succeeds.
What we cannot show. TLS inside a private network, or mail-server STARTTLS. STARTTLS on MX hosts is a Pro check on a saved scan.
Multi-factor authentication
What we can show. CyberEnforced accounts can turn on TOTP. That is evidence for those accounts only.
What we cannot show. MFA on Microsoft 365, Google Workspace, a VPN, or any other system. A domain scan does not read your identity provider.
Security awareness training
What we can show. The Training & Awareness add-on assigns catalog courses and records who passed, including "Spot It. Stop It. Report It."
What we cannot show. That a carrier will accept the course, or a training history from before you assigned it.
Policies and incident response
What we can show. The GRC add-on stores policies, versions, and acknowledgments, and a risk register. Evidence notes are manual.
What we cannot show. An automated pull from AWS, Okta, or GitHub, or a legal opinion that a policy is sufficient.
Vendors and third parties
What we can show. The Vendor Security add-on is an inventory with criticality, review status, and a next-review date.
What we cannot show. A scan of the vendor’s own environment.
Backups, EDR, and endpoint controls
What we can show. Nothing. CyberEnforced does not check these.
What we cannot show. Whether backups run, whether an EDR agent is installed, or whether laptops are encrypted.