Skip to content

v1.6.0

Latest

Choose a tag to compare

@github-actions github-actions released this 14 Nov 05:10
· 24 commits to main since this release
v1.6.0
ad1d18f

Added

  • SARIF rules are tagged with their CIS, OWASP and MITRE ATT&CK mapping.
    Each rule in --format sarif output now has properties.tags, for
    example external/cis-docker/5.4, external/owasp-docker/rule-3 and
    external/mitre-attack/T1611. GitHub Code Scanning can filter alerts on
    them with tag:. The mapping is the one the rules already cited; the new
    standards mapping page lists it for every rule and
    says what a tag claims. Existing alerts keep their identity: tags are not
    part of the fingerprint. The tags are informational and can change in any
    release (ADR-043).
    There is no security tag.
  • CL-0014 cites CIS Docker Benchmark 2.14, the control on centralized
    and remote logging. It is a daemon-level control, so the rule relates to
    it and does not satisfy it.

Changed

  • CIS Docker Benchmark citations are pinned to v1.9.0. They were pinned
    to v1.7.0. Every control number a rule cites was checked against the
    v1.9.0 text, and the numbers the other rules cite are unchanged.

Fixed

  • CL-0026 cites the right CIS controls. It cited 5.10 for memory limits
    and 5.11 for CPU priority. Those controls are 5.11 and 5.12; 5.10 is the
    host network namespace, which CL-0008 cites.

  • CL-0010's rule description no longer cites CIS 5.21 and 5.31. Those
    are the UTS and user namespace controls, which the rule stopped grading
    before 1.0. Its findings already cited only 5.16 and 5.17.

  • CL-0009 gives CIS 5.22 its published title.

  • The rule pages for CL-0024 to CL-0028 list their references. The rules
    cited OWASP and CIS sources that their pages did not show.

  • A YAML value its type cannot hold is reported as invalid YAML. A file
    with an explicit type tag on a value that does not fit it, such as
    !!int "abc", made check print a traceback and "internal error ... This
    is a bug". It is now the ordinary "Invalid YAML" error with a line and
    column, in text, JSON and SARIF, for a Compose file, an included file and
    the policy file. The exit code was already 2 and still is. The same holds
    for an untagged number too long to convert and, in the policy file, a
    date-shaped value naming a date that does not exist. init no longer
    stops on a service whose name is such a value.

  • CL-0008 and CL-0010 no longer cite an OWASP rule that does not cover
    them.
    CL-0008 (host network mode) cited the cheat sheet's Rule 5, which
    is about traffic between containers, and CL-0010 (host PID and IPC
    namespaces) cited Rule 3, which is about capabilities. Neither rule
    mentions what these two grade. Both keep their CIS references, which
    match exactly. In text output the reference line for these two rules is
    now the CIS control.