Skip to content

Standards mapping: CIS, OWASP and MITRE ATT&CK tags

Every rule cites the sources it is grounded in. In SARIF output the same mapping is also published as tags on each rule, so findings can be filtered by a CIS control, an OWASP rule or an ATT&CK technique.

Source Version Tag shape Rules tagged
CIS Docker Benchmark v1.9.0 external/cis-docker/<control> 23 of 28
OWASP Docker Security Cheat Sheet unversioned external/owasp-docker/rule-<number> 23 of 28
MITRE ATT&CK v18 external/mitre-attack/<technique> 25 of 28

What a tag claims

A tag says the rule relates to the named control or technique. It does not say that a file with no findings complies with the benchmark. compose-lint reads a Compose file, not a running daemon, so most of the CIS Docker Benchmark is outside what it can see: host configuration, daemon configuration, file permissions and image builds are not checked at all.

An ATT&CK tag is mitigation coverage. Fixing the finding helps against the technique. compose-lint detects nothing at runtime.

Do not present a clean compose-lint run as benchmark compliance.

Where the tags appear

The tags are in properties.tags on each rule in --format sarif output. They are not in text or JSON output.

In GitHub Code Scanning, filter the alert list with tag:, for example tag:external/cis-docker/5.4 or tag:external/mitre-attack/T1611.

There is no security tag. GitHub already treats every compose-lint result as a security result, because each rule carries a security-severity. Use the severity filters to select them.

ATT&CK is also published as a SARIF taxonomy, with a relationship from each rule to its techniques, for consumers that read that form. GitHub Code Scanning does not.

Stability

The tags are informational. They are not part of the machine-readable output contract, so a tag can be corrected, added or removed in any release. The changelog records each change. The decision is recorded in ADR-043.

A CIS tag does not carry the benchmark version. The numbers are the ones in v1.9.0; CIS renumbers controls between versions, so check the version first if a number looks wrong against your copy.

Rule mapping

Rule CIS Docker Benchmark OWASP Docker Security MITRE ATT&CK
CL-0001 external/cis-docker/5.32 external/owasp-docker/rule-1 external/mitre-attack/T1610
external/mitre-attack/T1609
external/mitre-attack/T1611
external/mitre-attack/T1612
external/mitre-attack/T1552.007
external/mitre-attack/T1613
CL-0002 external/cis-docker/5.5 external/owasp-docker/rule-3 external/mitre-attack/T1611
external/mitre-attack/T1685
CL-0003 external/cis-docker/5.26 external/owasp-docker/rule-4 external/mitre-attack/T1548.001
CL-0004 external/cis-docker/5.28 external/owasp-docker/rule-13 external/mitre-attack/T1204.003
CL-0005 external/cis-docker/5.14 external/owasp-docker/rule-5a none
CL-0006 external/cis-docker/5.4 external/owasp-docker/rule-3 external/mitre-attack/T1040
external/mitre-attack/T1557
external/mitre-attack/T1548.001
CL-0007 external/cis-docker/5.13 external/owasp-docker/rule-8 none
CL-0008 external/cis-docker/5.10 none external/mitre-attack/T1046
CL-0009 external/cis-docker/5.22
external/cis-docker/5.2
external/cis-docker/5.3
external/owasp-docker/rule-6 external/mitre-attack/T1685
CL-0010 external/cis-docker/5.16
external/cis-docker/5.17
none external/mitre-attack/T1611
CL-0011 external/cis-docker/5.4 external/owasp-docker/rule-3 external/mitre-attack/T1611
external/mitre-attack/T1557
external/mitre-attack/T1040
external/mitre-attack/T1529
CL-0013 external/cis-docker/5.6 external/owasp-docker/rule-8 external/mitre-attack/T1552.001
CL-0014 external/cis-docker/2.14 none external/mitre-attack/T1070
CL-0016 external/cis-docker/5.18 none external/mitre-attack/T1611
external/mitre-attack/T1552.001
CL-0017 external/cis-docker/5.20 none external/mitre-attack/T1611
CL-0018 none external/owasp-docker/rule-2 external/mitre-attack/T1611
external/mitre-attack/T1078
CL-0019 none external/owasp-docker/rule-13 external/mitre-attack/T1204.003
external/mitre-attack/T1525
CL-0020 none external/owasp-docker/rule-12 external/mitre-attack/T1552.001
CL-0021 none external/owasp-docker/rule-12 external/mitre-attack/T1552.001
CL-0022 none external/owasp-docker/rule-8 none
CL-0024 external/cis-docker/5.4 external/owasp-docker/rule-3 external/mitre-attack/T1611
CL-0025 external/cis-docker/5.6 external/owasp-docker/rule-8 external/mitre-attack/T1611
CL-0026 external/cis-docker/5.11
external/cis-docker/5.12
external/owasp-docker/rule-7 external/mitre-attack/T1496
external/mitre-attack/T1499
CL-0027 external/cis-docker/5.4 external/owasp-docker/rule-3 external/mitre-attack/T1055
external/mitre-attack/T1003
external/mitre-attack/T1552.001
external/mitre-attack/T1611
CL-0028 external/cis-docker/5.4 external/owasp-docker/rule-3 external/mitre-attack/T1070
external/mitre-attack/T1499
external/mitre-attack/T1003
CL-0029 external/cis-docker/5.4 external/owasp-docker/rule-3 external/mitre-attack/T1499
external/mitre-attack/T1496
CL-0030 external/cis-docker/5.4 external/owasp-docker/rule-3 external/mitre-attack/T1613
CL-0031 external/cis-docker/5.32 external/owasp-docker/rule-1 external/mitre-attack/T1610
external/mitre-attack/T1609
external/mitre-attack/T1611
external/mitre-attack/T1612
external/mitre-attack/T1552.007
external/mitre-attack/T1552.001
external/mitre-attack/T1613

Rules with no tag from a source

A rule is left untagged for a source only for a recorded reason.

CIS Docker Benchmark

  • CL-0018: the nearest control, 4.1, asks that the image defines a user; it is an image-build control and does not cover a Compose user: key.
  • CL-0019: no control asks for a digest; 5.28 is about stale cached images and is CL-0004's.
  • CL-0020: the secrets controls cover Dockerfiles (4.9) and swarm (7.4), not a Compose environment: value.
  • CL-0021: same as CL-0020.
  • CL-0022: no control covers tmpfs mount options.

OWASP Docker Security Cheat Sheet

  • CL-0008: Rule 5 is about traffic between containers and does not mention host networking; no rule on the sheet does.
  • CL-0010: no rule on the sheet covers host PID or IPC namespaces.
  • CL-0014: Rule 10 is about the daemon's log level; the rule cites the OWASP Logging Cheat Sheet, a different document.
  • CL-0016: no rule on the sheet covers host devices.
  • CL-0017: no rule on the sheet covers mount propagation.

MITRE ATT&CK

  • CL-0005: published ports are attack surface that enables a technique; the rule has no technique of its own.
  • CL-0007 and CL-0022: defence in depth that denies an attacker a place to stage tools, which is too indirect to name a technique.