Skip to main content

Security policy population change (COV-01, COV-05)

This release adds optional exact, case-sensitive eventActions, eventResults and eventSeverities predicates. Predicates combine with category/type using AND; values within one predicate use OR. Omitted predicates preserve old matching and canonical policy hashes. Empty/null predicates and unknown results/severities fail loading. Unrecognised event types still fail closed. Upgrade both collector runtimes before installing policies that use these new keys; older strict loaders reject them instead of silently accepting broader input.

Versioned population diff​

PopulationBeforeAfter
Authentication failure / lockoutAccepted with required contextUnchanged
Evidence canary / privacy alertAccepted with required contextUnchanged
SDK role add/removeDefault denyNew BWR-POL-ROLE-MEMBERSHIP 1.0.0; actor, target, changed role and correlation required
SDK sensitive exportDefault denyNew BWR-POL-SENSITIVE-EXPORT 1.0.0; actor, export ID, classification, count and correlation required
Successful generic cloud inventory/readAccepted by broad cloud category/typeRejected locally even if upstream subscription broadens
Named IAM, logging-control and security configuration changesAcceptedRetained by explicit action lists; AWS detach-policy and remove-group-member operations added upstream and locally
Denied/failed cloud API operationsAcceptedRetained by new denied-operation policies, irrespective of API action
Low/informational cloud findingsAcceptedRejected; medium/high/critical retained
Unknown software/event typesDeniedDenied

AWS and GCP existing policies move from 1.0.0 to 1.1.0. AWS pack is 1.1.0; GCP pack is 1.1.1 for its additional exact detection-method correction. New denied-operation policies start at 1.0.0. Exact action populations live in packs/*/policies; there is no suffix wildcard or inferred arbitrary method support. CloudFormation condition identifiers such as AppLogs are not API actions and remain denied. Source variants need reviewed additions and new fixtures. This is a class-level fixture population diff, not a measured claim about tenant volume, coverage or cost. Unknown tenant distributions remain unmeasured.

Regression evidence​

DefaultSignalCoverageTests hosts the actual collector with shipped default policies and explicit single-trust-domain test configuration. All three public SDK methods must reach its durable queue. It also checks approved cloud actions, broadened inventory feeds and malformed predicates. Rust policy_evaluator and policy_loader tests pinned the same selection cases (the Rust collector was retired in November 2026); default policy hash vectors are generated from C#. Existing policy hashes remain pinned and unchanged.

Investigation contract​

Role changes retain actor, target user, grant/revoke action and approved role change values. Exports retain actor, export identity, classification, count and correlation; no exported content is collected. New Sentinel columns append TimeObserved, EventOutcomeReason, Target, Change, and Attributes to the existing schema. DCRs accept only the already-redacted envelope; rich context never authorises raw request/response forwarding. Destination query validation of these fields is still required in the intended workspace before release claims.