Default security event catalogue
Shipped default policies cover these semantic events. Producer identity scopes are checked before processing; events are redacted before the durable queue. Each event still needs valid contract fields and its policy's required context. An SDK memory-buffer acceptance is not collector, Azure or Sentinel acceptance.
| Semantic type | Security purpose | Required investigation context | Default policy |
|---|---|---|---|
authentication_failure, account_lockout | Authentication abuse and account compromise | Time, application, result and actor; source and correlation recommended | BWR-POL-AUTH-FAILURE |
role_membership_changed | Privilege grants and removals | Actor, target user, role change, correlation; action role.add or role.remove, successful outcome | BWR-POL-ROLE-MEMBERSHIP 1.0.0 |
sensitive_data_exported | Sensitive export investigation | Actor, export ID, classification, record count, correlation; successful data.export | BWR-POL-SENSITIVE-EXPORT 1.0.0 |
sensitive_data_detected | Collector privacy-control intervention | Detector/rule metadata, never original detected value | BWR-POL-PRIVACY-DETECT |
collector_canary | Synthetic delivery validation | Unique canary identity and synthetic marker | BWR-POL-EVIDENCE-CANARY |
OWASP ASVS 5.0 logging pack
The signed owasp-asvs-app-logging pack adds these application
event types. It composes with the defaults above and never redefines them. Required fields,
actions and the ASVS 5.0 requirements each type supports are in the
pack catalogue.
| Semantic type | Security purpose | Pack policy |
|---|---|---|
authentication_success | Successful sign-in and re-authentication, with method | BWR-PACK-ASVS-AUTH-SUCCESS |
mfa_challenge, mfa_success, mfa_failure | MFA outcomes and push bombing | BWR-PACK-ASVS-MFA |
mfa_factor_enrolled, mfa_factor_removed, password_reset_requested, password_reset_completed, password_changed | Factor and password lifecycle | BWR-PACK-ASVS-FACTOR-LIFECYCLE |
account_status_changed | Account create, disable, enable, delete, unlock | BWR-PACK-ASVS-ACCOUNT-STATUS |
session_terminated, session_rotated | Logout, timeout, revocation, rotation | BWR-PACK-ASVS-SESSION |
authorisation_failure | Function, object, field and stale-grant denials | BWR-PACK-ASVS-AUTHZ-FAILURE |
sensitive_data_accessed, sensitive_record_changed | Sensitive reads, creates, updates and deletes | BWR-PACK-ASVS-SENSITIVE-DATA |
admin_action, configuration_changed, permission_changed | Privileged and configuration changes | BWR-PACK-ASVS-ADMIN |
input_validation_failure, business_logic_violation, anti_automation_triggered | Control bypass attempts; suppressed above 20 a minute per address | BWR-PACK-ASVS-CONTROL-BYPASS, BWR-PACK-ASVS-SUPPRESSION-SUMMARY |
application_error, security_control_failure | Unexpected errors and control failures | BWR-PACK-ASVS-ERRORS |
database_audit | Normalised database audit records (notes) | BWR-PACK-ASVS-DB-AUDIT |
Opt-in, generated by the collector when a policy uses suppression or when health
records are enabled (no default policy; the bundle must accept them, see
examples/policies/suppression and
examples/policies/collector-health):
| Semantic type | Security purpose | Content | Example policy |
|---|---|---|---|
telemetry_aggregation_summary (action telemetry.suppressed) | Accounts for every event suppressed in one window, so volume is visible in Sentinel even when individual events are not stored | Suppressing policy id, suppressed event type, key fields and redacted key values, admitted and suppressed counts, window bounds, first and last suppressed times; security.decision is aggregate | BWR-POL-SUPPRESSION-SUMMARY |
collector_health (category collector-health, action collector.health; BOWER_HEALTH_RECORD_INTERVAL_SECONDS) | Proves the collector and its delivery path work; its absence and its contents drive the operational alerts | Queue, storage, delivery, intake and source-silence state, syslog listener and Windows Event Log counters as deltas; metadata only, numbers below eight digits | BWR-POL-COLLECTOR-HEALTH (the collector refuses to start without an accepting policy) |
Destination: BowerSecurity_CL through the configured approved output. Default
application policies never sample. Retention is a destination/operator decision;
the sample Bicep retains 90 interactive days and 365 total days, which includes
archive. Synthetic canaries must be excluded from operational detections.
Ownership: application teams own correct emission and source semantics; Security Operations owns policy population and triage. Unknown types remain denied. See population changes, producer scopes and Entra destination gates.
Extending software support
Language-neutral HTTP envelopes allow additional software to integrate, but do not establish a tested integration. For each software/version, require bounded mapping, explicit high-value selection, privacy fixtures, durable source progress, replay/backpressure/cancellation tests and destination field assertions. Prefer native Sentinel connectors when they already supply the required security signal. SQL library support does not imply an installed polling service. Broad JSONL, Windows Event Log and audit-API coverage and extra language SDKs remain separately scoped integrations; no claim of support for every software package is made.
Event identity
Every event type uses globally unique, retry-stable IDs across producers.
Collector HTTP 409 event-identity-conflict is an intake outcome, not a new
security event type. Preserve upstream events pending producer repair; see
event identity conflict recovery.