Skip to main content

Compliance

Every server audit can be read framework by framework. DeaconGuard maps each control of its baseline, and its checks for vulnerabilities, file integrity and malware, to requirements of:

  • NIST SP 800-53 Rev. 5
  • PCI DSS v4.0
  • The HIPAA Security Rule (45 CFR Part 164, Subpart C)
  • ISO/IEC 27001:2022 Annex A
  • The DISA STIG for the machine's operating system (1.24.0 and later), for Ubuntu 22.04 and 24.04 and for RHEL 8 and 9; see DISA STIG.

What it means, and what it doesn't​

The mapping says which of a framework's requirements a host audit gives evidence for. For each one, the audit shows:

StatusMeaning
MetEvery control behind the requirement passed.
Met, risk acceptedThey passed, or failed with an accepted risk.
Not metAt least one control behind it failed.
Not checkedA control behind it couldn't be checked, usually because the audit ran without root.
Partly checkedDISA STIG only: the control behind the rule passed, but the rule asks for more than the control checks. Check the rest by hand.

This is DeaconGuard's own mapping, for guidance. Frameworks also require policies, training, physical security, vendor management and processes that no scan of a server can see. A server meeting every mapped requirement is not certified or compliant on that basis alone: an assessor decides that. Requirements are referred to by their number; the short names are DeaconGuard's own descriptions, not the standards' text.

Where to see it​

  • On an audit's page, the Compliance card has a tab for each framework, with how many requirements are met and not met, and the controls behind each.
  • In reports: when you create a report, choose the frameworks to include. Each gets a section listing its requirements, their status and their evidence, in the PDF, HTML, Excel and CSV.

DISA STIG​

From 1.24.0, each control of the Linux baseline names the rules of the DISA STIG for the machine's operating system that it checks:

MachineSTIG
Ubuntu 22.04Canonical Ubuntu 22.04 LTS STIG, V2R10 (30 September 2026)
Ubuntu 24.04Canonical Ubuntu 24.04 LTS STIG, V1R7 (30 September 2026)
RHEL 8, Rocky Linux 8, AlmaLinux 8Red Hat Enterprise Linux 8 STIG, V2R9 (30 September 2026)
RHEL 9, Rocky Linux 9, AlmaLinux 9Red Hat Enterprise Linux 9 STIG, V2R10 (30 September 2026)

Rocky Linux and AlmaLinux are rebuilds of RHEL, so their rules are the RHEL STIG's. Other systems, such as Debian, Ubuntu 20.04, Oracle Linux, SUSE and Alpine, get no STIG rules.

  • On an audit's page, each control shows its rule IDs, such as V-257985. Its details name the STIG and say what the rule asks for beyond the control.
  • The Compliance card's DISA STIG tab lists the STIG's rules that a control checks, with each rule's title as DISA publishes it.
  • In reports: each control's rules are in the PDF and HTML and in the CSV and Excel DISA STIG column. Choose DISA STIG among the frameworks for a section listing each rule.

A control is mapped only where it checks the same setting as the rule. Many STIG rules ask for more than DeaconGuard's control, such as passwords of 15 characters where the control asks for 12. Then the control passing doesn't pass the rule: the audit marks the rule Partly checked and says what the STIG asks for. A failed control fails the rule too.

This is not a STIG assessment. A STIG has 190 to 450 rules; DeaconGuard's baseline checks a few dozen of them. Most rules need settings DeaconGuard doesn't read, such as audit rules for each command, the STIG's banner text, FIPS mode and documentation. The mapping, and the notes on what each rule asks for, are DeaconGuard's own. DISA publishes the STIGs openly; rule titles are quoted as DISA publishes them.

Scans from before 1.24.0 show the rules too: they're added when the audit is read, from the operating system the scan recorded. No agent upgrade is needed.

The mapping​

NIST SP 800-53 Rev. 5​

RequirementEvidence from
AC-2Account managementACC-07, ACC-08, MACOS-10
AC-2(3)Disable accountsACC-09
AC-3Access enforcementACC-06, FS-01, FS-02, FS-03, FS-04, FS-05, FS-08, FS-09, FS-10, FS-12, FS-13, KRN-06, SSH-12
AC-3(3)Mandatory access controlMAC-01
AC-4Information flow enforcementNET-01
AC-6Least privilegeACC-01, FS-11, SSH-01
AC-7Unsuccessful logon attemptsACC-05, ACC-11, SSH-05
AC-8System use notificationSSH-13
AC-12Session terminationSSH-06
AC-17Remote accessMACOS-07, MACOS-08, SSH-01, SSH-02, SSH-09
AU-2Event loggingLOG-01, LOG-02, NET-08, SSH-14
AU-8Time stampsMACOS-18, TIME-01, TIME-02
AU-9Protection of audit informationLOG-04, LOG-05
AU-11Audit record retentionLOG-04
AU-12Audit record generationLOG-01, LOG-02, LOG-03, SSH-14
CM-6Configuration settingsACC-06, ACC-07, FS-01, FS-03, FS-05, FS-06, FS-07, FS-08, FS-09, FS-10, FS-11, FS-12, KRN-02, KRN-03, KRN-05, KRN-06, KRN-07, MACOS-02, NET-02, NET-03, NET-04, NET-05, NET-07, NET-09, SSH-10, SSH-12
CM-7Least functionalityFS-06, FS-07, MACOS-07, MACOS-08, MACOS-09, SSH-04, SVC-02, SVC-03, SVC-04, SVC-05, SVC-06
CM-14Signed componentsMACOS-03, UPD-03
IA-2Identification and authenticationACC-01, ACC-08, MACOS-10, MACOS-11, SSH-02, SSH-07, SSH-08
IA-5Authenticator managementACC-02, FS-02, FS-04, SSH-03
IA-5(1)Password-based authenticationACC-03, ACC-04, ACC-10
MP-7Media useSVC-07
RA-5Vulnerability monitoring and scanningpackages
SC-5Denial-of-service protectionNET-06, NET-07, SSH-09
SC-7Boundary protectionMACOS-05, MACOS-06, NET-01, NET-02, NET-03, NET-04, NET-05, NET-08, NET-09, SVC-01, SVC-02, SVC-06
SC-8Transmission confidentiality and integritySSH-11, SVC-03
SC-10Network disconnectSSH-06
SC-13Cryptographic protectionSSH-11
SC-28Protection of information at restMACOS-01
SC-39Process isolationKRN-04, MAC-01
SI-2Flaw remediationMACOS-12, MACOS-13, MACOS-14, MACOS-15, MACOS-16, MACOS-17, UPD-01, UPD-02, packages
SI-3Malicious code protectionMACOS-03, MACOS-04, MACOS-14, antivirus, malware, yara
SI-4System monitoringmalware
SI-7Software, firmware and information integrityMACOS-02, UPD-03, integrity
SI-16Memory protectionKRN-01, KRN-03

PCI DSS v4.0​

RequirementEvidence from
1.3.1Inbound traffic to the cardholder data environment is restrictedMACOS-05, MACOS-06, SVC-01, SVC-02
1.3.2Outbound traffic from the cardholder data environment is restrictedSVC-01
2.2.2Vendor default accounts are managedACC-07
2.2.4Only necessary services and functions are enabledMACOS-07, MACOS-08, MACOS-09, SSH-04, SVC-02, SVC-03, SVC-04, SVC-05, SVC-06
2.2.5Insecure services are justified and securedSVC-03
2.2.6System security parameters prevent misuseACC-06, FS-01, FS-02, FS-03, FS-04, FS-05, FS-06, FS-07, FS-08, FS-09, FS-10, FS-11, FS-12, KRN-01, KRN-02, KRN-03, KRN-04, KRN-05, KRN-06, KRN-07, MAC-01, MACOS-02, NET-01, NET-02, NET-03, NET-04, NET-05, NET-06, NET-07, NET-08, NET-09, SSH-09, SSH-10, SSH-12
2.2.7Administrative access is encryptedSSH-01, SSH-11, SVC-03
5.2.1Anti-malware is deployedMACOS-03, MACOS-04, MACOS-14, antivirus, malware, yara
5.3.2Anti-malware scans runantivirus, yara
6.3.3Security patches are installedMACOS-12, MACOS-13, MACOS-14, MACOS-15, MACOS-16, MACOS-17, UPD-01, UPD-02, packages
8.2.1Every user has a unique IDACC-01, ACC-08
8.2.2Shared and generic accounts are controlledMACOS-10, SSH-01
8.2.6Inactive accounts are removed or disabledACC-09
8.2.8Idle sessions require signing in againSSH-06
8.3.1Users are authenticatedACC-02, MACOS-11, SSH-02, SSH-03, SSH-07, SSH-08
8.3.2Authentication factors are unreadable when storedFS-02, FS-04
8.3.4Failed logins lock the accountACC-05, ACC-11, SSH-05
8.3.6Passwords have at least 12 charactersACC-04
8.3.7Recent passwords can't be reusedACC-10
8.3.9Passwords change at least every 90 daysACC-03
10.2.1Audit logs are enabledLOG-01, LOG-02, LOG-03, SSH-14
10.3.1Read access to audit logs is limitedLOG-05
10.5.1Audit logs are retainedLOG-04
10.6.1Clocks are synchronizedMACOS-18, TIME-01, TIME-02
11.3.1Internal vulnerability scans runpackages
11.5.2Changes to critical files are detectedintegrity

HIPAA Security Rule (45 CFR 164 Subpart C)​

RequirementEvidence from
164.308(a)(1)(ii)(A)Risk analysispackages
164.308(a)(5)(ii)(B)Protection from malicious softwareMACOS-03, MACOS-04, MACOS-14, antivirus, malware, yara
164.308(a)(5)(ii)(C)Log-in monitoringACC-05, ACC-11, SSH-05
164.308(a)(5)(ii)(D)Password managementACC-03, ACC-04, ACC-10
164.310(d)(1)Device and media controlsSVC-07
164.312(a)(1)Access controlACC-06, ACC-07, FS-01, FS-02, FS-03, FS-04, FS-13, MAC-01, MACOS-07, MACOS-08, SSH-01, SSH-04, SSH-10, SSH-12, SVC-02
164.312(a)(2)(i)Unique user identificationACC-01, ACC-08, MACOS-10
164.312(a)(2)(iii)Automatic logoffSSH-06
164.312(a)(2)(iv)Encryption and decryptionMACOS-01
164.312(b)Audit controlsLOG-01, LOG-02, LOG-03, LOG-04, LOG-05, MACOS-18, SSH-14, TIME-01, TIME-02
164.312(c)(1)IntegrityFS-01, FS-05, FS-08, FS-09, FS-11, MACOS-02, UPD-03, integrity
164.312(d)Person or entity authenticationACC-02, MACOS-11, SSH-02, SSH-03, SSH-07, SSH-08
164.312(e)(1)Transmission securityMACOS-05, SSH-11, SVC-01, SVC-03

ISO/IEC 27001:2022 Annex A​

RequirementEvidence from
5.16Identity managementACC-08, MACOS-10
5.17Authentication informationACC-02, ACC-03, ACC-04, ACC-10, FS-02, FS-04
5.18Access rightsACC-07, ACC-09
7.10Storage mediaSVC-07
8.2Privileged access rightsACC-01, SSH-01
8.3Information access restrictionFS-13, MACOS-09
8.5Secure authenticationACC-05, ACC-11, MACOS-11, SSH-02, SSH-03, SSH-05, SSH-06, SSH-07, SSH-08
8.7Protection against malwareMACOS-03, MACOS-04, MACOS-14, antivirus, malware, yara
8.8Management of technical vulnerabilitiesMACOS-12, MACOS-13, MACOS-14, MACOS-15, MACOS-16, MACOS-17, UPD-01, UPD-02, packages
8.9Configuration managementACC-06, FS-01, FS-02, FS-03, FS-04, FS-05, FS-06, FS-07, FS-08, FS-09, FS-10, FS-11, FS-12, KRN-01, KRN-02, KRN-03, KRN-04, KRN-05, KRN-06, KRN-07, MAC-01, MACOS-02, SSH-04, SSH-09, SSH-10, SSH-12, SVC-03, SVC-04, SVC-05
8.15LoggingLOG-01, LOG-02, LOG-03, LOG-04, LOG-05, SSH-14
8.16Monitoring activitiesintegrity, malware
8.17Clock synchronizationMACOS-18, TIME-01, TIME-02
8.19Installation of software on operational systemsMACOS-03, UPD-03
8.20Networks securityMACOS-05, MACOS-06, MACOS-07, MACOS-08, NET-01, NET-02, NET-03, NET-04, NET-05, NET-06, NET-07, NET-08, NET-09, SVC-01, SVC-02, SVC-06
8.24Use of cryptographyMACOS-01, SSH-11

DISA STIG​

The rules each control checks, by STIG. Controls not listed check no rule of these STIGs.

ControlCanonical Ubuntu 22.04 LTSCanonical Ubuntu 24.04 LTSRHEL 8RHEL 9The STIG asks for more
ACC-01V-230534V-258059
ACC-02V-260571V-270713V-251706V-258120
ACC-03V-260546V-270731V-230366V-258041The STIG asks for PASS_MAX_DAYS 180 or less.
ACC-04V-260565V-270732V-230369V-258107The STIG asks for a minimum length of 15 characters.
ACC-05V-260549V-270690V-230333V-258054The STIG asks for a lock after 3 failed logins.
ACC-06V-260555V-270716V-230383V-258074The STIG asks for UMASK 077.
ACC-07V-288817V-288819V-258046
ACC-08V-260543V-270720V-230371V-258045
ACC-09V-260547V-270683V-230373V-258049The STIG asks for INACTIVE=35 or less.
ACC-11V-260549V-270690V-230333V-258054The STIG asks for a lock after 3 failed logins.
SSH-01V-230296V-257985The STIG asks for PermitRootLogin no, which also refuses key logins as root.
SSH-03V-260526V-270717V-230380V-257984The STIG rule also asks for PermitEmptyPasswords no and PermitUserEnvironment no (SSH-03 and SSH-10).
SSH-04V-260529V-270708V-230555V-258007
SSH-06V-260528V-270743V-244525V-257996The STIG asks for ClientAliveInterval 600 or less.
SSH-07V-257992
SSH-08V-258005
SSH-10V-260526V-270717V-230330V-257993The STIG rule also asks for PermitEmptyPasswords no and PermitUserEnvironment no (SSH-03 and SSH-10).
SSH-11V-260531, V-260532V-270667, V-270668V-230251, V-230252V-257989, V-257991The STIG allows only FIPS 140-3 approved algorithms.
SSH-13V-260525V-270691V-230225V-257981The STIG asks for its own notice and consent banner text.
SSH-14V-257982The STIG asks for LogLevel VERBOSE.
NET-01V-250317V-257970
NET-02V-244553V-257958
NET-03V-230536V-257968
NET-04V-244551V-257959
NET-05V-230549V-257962The STIG asks for rp_filter 1; this control also accepts 2.
NET-06V-260522V-270753V-257957
NET-07V-230537V-257966
NET-08V-284948V-257960
NET-09V-230544V-257972
KRN-01V-260474V-270772V-230280V-257809
KRN-02V-260472V-270749V-230269V-257797
KRN-03V-230547V-257800The STIG asks for kptr_restrict 1; this control also accepts 2.
KRN-04V-230546V-257811The STIG asks for ptrace_scope 1; this control also accepts 2 and 3.
KRN-06V-230267, V-230268V-257801, V-257802
KRN-07V-230313, V-230314V-257813, V-257814The STIG asks for both '* hard core 0' and systemd-coredump Storage=none; this control passes with either.
SVC-01V-260515V-270655V-244544V-257936The STIG asks for ufw to be enabled and running. The STIG asks for firewalld to be active.
SVC-03V-260482V-270648V-230487, V-230533V-257831, V-257835
SVC-04V-230553V-257837
SVC-07V-260540V-270718V-230503V-258034The STIG also asks for blacklist usb-storage.
LOG-01V-260591V-270657V-244542V-258152
LOG-03V-230298V-258142The STIG asks for rsyslog; this control also accepts systemd-journald and syslog-ng.
FS-01V-257895
FS-02V-257934The STIG asks for mode 0000.
FS-03V-257891
FS-04V-257893The STIG asks for mode 0000.
FS-06V-230511, V-230512V-257866, V-257868
FS-07V-230508, V-230509, V-230510V-257863, V-257864, V-257865
FS-09V-260513V-270750V-230243V-257929
FS-10V-230326, V-230327V-257930, V-257931
FS-13V-230321V-257890
UPD-03V-260476V-270695V-230264V-257822
TIME-01V-257944The STIG asks for chronyd; this control accepts any time service.
MAC-01V-260557V-270660V-230240V-258078The STIG asks for apparmor.service to be enabled and active.