Ship compliance mapping packs and the OAI composition rules - #48
Closed
jhumel-code wants to merge 7 commits into
Closed
Ship compliance mapping packs and the OAI composition rules#48jhumel-code wants to merge 7 commits into
jhumel-code wants to merge 7 commits into
Conversation
CSDK-103, CSDK-120, CSDK-201, CSDK-202, ADK-008, LC-101 — single fatal 'safety layer off' switches that the ACaC deployment-readiness gate must catch via its critical-override. Calibration evidence: .superpowers/calibration in the engine repo.
Ships the five compliance mapping packs (NIST 800-53 r5, ISO 27002, SOC 2, EU AI Act, PCI DSS) and the OAI-025/107/112/113 rules, none of which were previously reachable from main. Also reclassifies permission-bypass and unrestricted-shell rules to critical. # Conflicts: # google_adk/builtin_tools.yaml
Collaborator
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Brings
feat/severity-reclassification-acacup onto currentmain. Every itemhere already existed on that branch but was unreachable from
main, so no userwas receiving any of it.
What lands
Compliance mapping packs (new).
mappings/*.ymlfor NIST SP 800-53 r5,ISO/IEC 27002:2022, SOC 2 (TSC 2017), the EU AI Act and PCI DSS. These are the
SME-reviewed crosswalk the engine's
compliance build-pack --mappingspathconsumes.
maincarried nomappings/directory at all, so that documentedpath had no data behind it.
Four rules that were tested but never shipped. OAI-025 (dead tool via
call-graph liveness), OAI-107 (handoff target wires shell tools), OAI-112 and
OAI-113 (transitive shell through handoff chains). These are the only rules
anywhere exercising
reachability_isandtransitive_capability_exceeds_direct,so both predicates currently reach no user.
Severity reclassification. Six permission-bypass / unrestricted-shell rules
move from high to critical: CSDK-103, CSDK-120, CSDK-201, CSDK-202, ADK-008 and
LC-101.
Merge conflict resolution
One conflict, in ADK-008.
mainhad corrected the title and widened the matcherto cover both
ExecuteBashTool(current google-adk) andBashTool(earlierreleases); the branch had only the older
BashTool-only matcher plus theseverity bump. Resolved by keeping
main's corrected title, explanation andwider matcher, and taking only the severity bump from the branch.
Verification
trustabl rules validateoutput on this branch is byte-identical to its outputon clean
origin/main, so this introduces no new schema, duplicate-ID orunknown-predicate errors. The 12 pre-existing errors are the known
missing-predicate drift (CSDK-017/018, CSDK-204, CSKILL-080..086) and are
untouched here.
Follow-up needed before this is fully compliant with the three-repo contract
The paired rulebook has not been updated yet:
severity: highin their rulebookfront-matter, which
tools/check_rulebook.pyfails on.schema_versionstays at 14, so the engine fixture (19) remains divergent.