The library documents itself · Security & governance
stzSecurityEvent
42 own methods · 0 forms written with extensions, listed under their method
the source: base/security/stzSecurityEvent.ring(opens in a new tab) · All classes · The area reference: Security & governance
Under each method, its extensions (Q CS XT Z ZZ IB W U): bold and ticked, it exists; struck, it does not. The extensions and what they mean
No method of this class is run on this page: the class reaches files, the network, processes, the clock, chance or sound, and an example run here would only be an example of its effects. Each method carries the explanation the library gives of itself.
Method
Explanation, as the source carries it
init
(no comment in the source: the name reads as a sentence) initno extension
Kind
readsno extension
Severity
(no comment in the source: the name reads as a sentence) severityno extension
Technique
(no comment in the source: the name reads as a sentence) techniqueno extension
Meaning
(no comment in the source: the name reads as a sentence) meaningno extension
Actor
(no comment in the source: the name reads as a sentence) actorno extension
Posture
(no comment in the source: the name reads as a sentence) postureno extension
ActorKinds
(no comment in the source: the name reads as a sentence) actor kindsno extension
Action
(no comment in the source: the name reads as a sentence) actionno extension
Risk
(no comment in the source: the name reads as a sentence) riskno extension
Subject
(no comment in the source: the name reads as a sentence) subjectno extension
Origin
(no comment in the source: the name reads as a sentence) originno extension
Outcome
(no comment in the source: the name reads as a sentence) outcomeno extension
Reason
(no comment in the source: the name reads as a sentence) reasonno extension
AtWall
(no comment in the source: the name reads as a sentence) at wallno extension
AtMono
(no comment in the source: the name reads as a sentence) at monono extension
TraceId
(no comment in the source: the name reads as a sentence) trace idno extension
IsRefusal
"granted" and "observed" are not refusals; "refused" and "failed" are. Written as an explicit list rather than `!= "granted"` because a fourth outcome arrived later (see Observed) and the negative form would have silently swept it in -- an expired session would have counted as a refusal in every pivot.no extension
ByActor
building (fluent; every setter returns This) --------------- WHO: an stzSystemActor contributes its own facts -- name, posture, capability kinds. Nothing is invented here.no extension
ByActorNamed
For a caller with no actor object yet (an unauthenticated request, a username at the login door).no extension
About
WHICH thing. THE REDACTION LAW lives here: an object contributes its DESCRIPTOR (stzSecret.Descriptor() is the redacted form), never its value -- this class never calls Reveal(). A string is taken as already-safe; callers pass descriptors like "user:admin", "key:billing", "route:/pay".no extension
Doing
(no comment in the source: the name reads as a sentence) doingno extension
AtRisk
(no comment in the source: the name reads as a sentence) at riskno extension
FromOrigin
(no comment in the source: the name reads as a sentence) from originno extension
OccurredAt
The deterministic form (the house "...At(now)" convention): an event that did not happen NOW carries its own wall clock -- a replayed or imported record, or a guard that needs exact window arithmetic instead of machine speed. The monotonic stamp is left alone: it orders THIS process's events and cannot be borrowed.no extension
Granted
outcomesno extension
Refused
(no comment in the source: the name reads as a sentence) refusedno extension
Failed
The gate admitted it and the act still did not complete.no extension
Observed
NOT A VERDICT -- something simply happened (incident I2's session seams). A session reaching its expiry was neither granted nor refused: no gate ran, nobody was told no. Forcing such a fact into "refused" would have made every pivot that counts refusals over-count, and would have taught an investigator that routine housekeeping was an attack. The ledger's job is to witness, and some of what it witnesses carries no judgment at all.no extension
AsInfo
severity (the catalog's default, overridable)no extension
AsWarning
(no comment in the source: the name reads as a sentence) as warningno extension
AsError
(no comment in the source: the name reads as a sentence) as errorno extension
Record
the native recordno extension
CanonicalString
The separator is reserved: a field's own pipes fold to "/" so the ledger can split the line back into fields without a field's content (a reason quoting a message, say) shifting every field after it. Sanitizing at the source beats parsing bravely later.no extension
OcsfSeverityId
interop: OCSF (the SIEM schema) ---------------------------- OCSF severity_id: 1 Informational, 3 Medium, 4 High.no extension
OcsfStatusId
OCSF status_id: 1 Success, 2 Failure.no extension
OcsfClassUid
Best-effort class mapping, honestly bounded: auth/sso/oauth are Identity & Access Management (category 3, class 3002 Authentication); http.* is Network Activity (4 / 4002 HTTP Activity); everything else is Application Activity (6 / 6003 API Activity). Facts that do not map cleanly ride in "unmapped", which is what that OCSF field is for.no extension
OcsfCategoryUid
(no comment in the source: the name reads as a sentence) ocsf category uidno extension
ToOcsfJson
(no comment in the source: the name reads as a sentence) to ocsf jsonno extension
AsLine
legibility ------------------------------------------------- One line, human first: who did what to which, how it ended, why.no extension
Explain
(no comment in the source: the name reads as a sentence) explainno extension
Show
(no comment in the source: the name reads as a sentence) showno extension

