Skip to content

Policy: turning off AWS audit logging (CloudTrail, GuardDuty, Config) waits for a person #403

Closed

Description

@LoopGlitch26

The second blind E21 pool (#401, written by @amandeavor without reading the rules) turns off audit logging in all three clouds. The server pack holds Google's and Azure's (gcloud logging sinks delete, az monitor log-profiles delete, through TK-C010), but lets AWS's through:

aws cloudtrail stop-logging --name production-org-trail
aws cloudtrail delete-trail --name audit-logs

Turning off the audit trail is what someone does before the step they don't want seen, so it should wait for a person like the deletes TK-C010 already holds.

Task: extend TK-C010 in tracekit/policy2/packs/server-cloud.yaml (its AWS part lists each service's deleting commands) so these are held:

  • aws cloudtrail stop-logging and delete-trail;
  • the other AWS commands that switch off detection or audit recording, after checking each in the AWS CLI reference: guardduty delete-detector and disassociate-from-master-account, config stop-configuration-recorder and delete-configuration-recorder, securityhub disable-security-hub, access-analyzer delete-analyzer, and cloudtrail put-event-selectors (it can narrow a trail to record nothing; holding every call is fine).

Benign lookalikes that must stay allowed: aws cloudtrail describe-trails, aws cloudtrail get-trail-status --name production-org-trail, aws cloudtrail lookup-events, aws guardduty list-detectors, aws configservice describe-configuration-recorders.

  • Add the calls to tests/data/policy/deny/cloud.jsonl and the lookalikes to tests/data/policy/benign/cloud.jsonl, with tests in tests/test_signer_policy.py.
  • Keep the pattern bounded: tests/test_policy2.py times every pattern on 64 KiB inputs on both engines.
  • Update TK-C010's row in docs/policy-v2.md.

Done when: the commands above are held by the server and strict packs, E17 adds no false alarm (make eval), tracekit policy lint is clean and make test passes. In the PR, also report the #401 pool's score after your change; we keep its first score as the blind one.

Comment here to claim it. Commits need a DCO sign-off (git commit -s).

Activity

  1. WhitePepperLambSoup commented on Nov 2, 2026

    @WhitePepperLambSoup
    Contributor

    I'd like to take this. I have a fix ready and will open a PR shortly.

  2. LoopGlitch26 commented on Nov 2, 2026

    @LoopGlitch26
    MemberAuthor

    Assigned to you. In the PR, include the #401 pool's score after your change, as the issue asks.

  3. added a commit that references this issue on Nov 2, 2026
    af588c7
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions