Account recovery
The process that restores access when authenticators are lost, which can become the weakest authenticator.
See it in practice
A chat-based photo reset can undo a passkey rollout if help desk treats it as a formality.
Connect the ideas: Identity, authentication, authorization, and recovery · Data protection, updates, backups, and resilience
Explore Account recovery in practice ↗
Alert
A notification that a rule or model wants a human to look at one or more records.
See it in practice
Impossible travel is an alert title; it is not the name of the incident.
Connect the ideas: Logs, alerts, and evidence · Triage a synthetic identity alert
Explore Alert in practice ↗
Attack surface management
The ongoing discovery, assessment, and reduction of ways an attacker could reach or affect an organization’s assets. Its scope may include external, internal, and cloud environments.
See it in practice
ASM is how Riverstone might notice a forgotten staging TrackPort still serving TLS on the internet.
Connect the ideas: Prioritize vulnerabilities and exposures · How systems communicate: network, DNS, HTTP, and TLS
Explore ASM in practice ↗
Asset
Anything whose disclosure, alteration, destruction, or downtime would harm a person or organization.
See it in practice
Riverstone treats YardOS pallet records as an asset because a wrong location can hide theft.
Connect the ideas: What we protect: assets, confidentiality, integrity, and availability · Data protection, updates, backups, and resilience
Explore Asset in practice ↗
Attestation
Evidence or a statement about a claimed device, workload, or control state that another party can evaluate against its requirements.
See it in practice
A device attestation that FleetLink is running on a managed phone can inform authorization without being authorization by itself.
Connect the ideas: Identity, authentication, authorization, and recovery · Least privilege, secure defaults, trust boundaries, and layered controls
Explore Attestation in practice ↗
Audit trail
An append-oriented history of security-relevant actions that can be shown to a later reviewer.
See it in practice
Priya’s approval to disable jordan.h should live in an audit trail, not only in a disappearing chat.
Connect the ideas: Logs, alerts, and evidence · Investigate, respond, and verify recovery
Explore Audit trail in practice ↗
Authentication
The act of verifying a claimed identity with authenticators such as passwords, passkeys, or certificates.
See it in practice
A password plus an MFA push that succeeds means the account proved itself, not that the assigned driver was present.
Connect the ideas: Identity, authentication, authorization, and recovery · Triage a synthetic identity alert
Explore Authentication in practice ↗
Authorization
The decision about whether a person, device, workload, or anonymous requester may perform a particular action on a resource.
See it in practice
Even after MFA, jordan.h should be denied an address export for a trailer assigned to someone else.
Connect the ideas: Identity, authentication, authorization, and recovery · Least privilege, secure defaults, trust boundaries, and layered controls
Explore Authorization in practice ↗
Availability
The property that authorized people can use a system or record when they need it.
See it in practice
Ransomware encrypting YardOS before the morning load is an availability failure.
Connect the ideas: What we protect: assets, confidentiality, integrity, and availability · Data protection, updates, backups, and resilience
Explore Availability in practice ↗
Backup
A copy of data kept so integrity and availability can be restored after loss, preferably beyond the production identity’s reach.
See it in practice
Nightly files on a share the YardOS account can encrypt are not a trustworthy backup until proven isolated.
Connect the ideas: Data protection, updates, backups, and resilience · Investigate, respond, and verify recovery
Explore Backup in practice ↗
Blast radius
How much additional loss a failure or a response action can cause beyond the original asset.
See it in practice
Deleting every FleetLink mailbox because one API timed out is a self-inflicted blast radius.
Connect the ideas: Least privilege, secure defaults, trust boundaries, and layered controls · Investigate, respond, and verify recovery
Explore Blast radius in practice ↗
Cloud access security broker
A control point for observing or constraining use of cloud services, including unsanctioned ones.
See it in practice
CASB might have shown the contractor forwarding a TrackPort export to a personal inbox.
Connect the ideas: Data protection, updates, backups, and resilience · From principles to frameworks and product categories
Explore CASB in practice ↗
Confidentiality, Integrity, Availability
A shorthand for naming whether a loss is disclosure, unauthorized change, or downtime.
See it in practice
Maya writes CIA in the incident note so a later product discussion still names the failed property.
Connect the ideas: What we protect: assets, confidentiality, integrity, and availability · From principles to frameworks and product categories
Explore CIA triad in practice ↗
Cloud-native application protection platform
A bundled category covering cloud posture, workload, and related application-risk features; boundaries vary by vendor.
See it in practice
A CNAPP purchase does not automatically include TrackPort’s in-app authorization tests.
Connect the ideas: From principles to frameworks and product categories · Prioritize vulnerabilities and exposures
Explore CNAPP in practice ↗
Compensating control
An alternative safeguard used in place of a specified control, with evidence that it provides comparable protection for the intended security objective.
See it in practice
If a legacy application cannot enforce MFA, restricting it behind a gateway that requires MFA may be a compensating control if direct access is blocked and the coverage is verified.
Connect the ideas: Prioritize vulnerabilities and exposures · Least privilege, secure defaults, trust boundaries, and layered controls
Explore Compensating control in practice ↗
Confidentiality
The property that information is available only to people or systems authorized to see it.
See it in practice
A contractor emailing TrackPort addresses to a personal inbox is a confidentiality failure.
Connect the ideas: What we protect: assets, confidentiality, integrity, and availability · Identity, authentication, authorization, and recovery
Explore Confidentiality in practice ↗
Control
A process, configuration, or technology meant to reduce a named risk or detect a named failure.
See it in practice
Phishing-resistant MFA is a control for TrackPort account takeover, not a general luck charm.
Connect the ideas: Least privilege, secure defaults, trust boundaries, and layered controls · From principles to frameworks and product categories
Explore Control in practice ↗
Coverage
An explicit statement of which sources, time windows, and rows were actually collected, including truncation.
See it in practice
“EDR not connected” is a coverage statement that belongs on CASE-8821, not a silent gap.
Connect the ideas: Logs, alerts, and evidence · Understand and build toward an Agentic SOC
Explore Coverage in practice ↗
Cloud security posture management
Checks of cloud configuration against policy, such as public storage or open security groups.
See it in practice
Review backup-bucket delete and retention-bypass permissions alongside retention locks; a delete permission alone does not prove a protected object can be erased.
Connect the ideas: Data protection, updates, backups, and resilience · From principles to frameworks and product categories
Explore CSPM in practice ↗
Continuous threat exposure management
A program for repeatedly finding, prioritizing, and reducing exposed attack surface rather than running a yearly scan.
See it in practice
CTEM would keep the VPN appliance in an owned queue instead of a quarterly PDF.
Connect the ideas: Prioritize vulnerabilities and exposures · From principles to frameworks and product categories
Explore CTEM in practice ↗
Common Vulnerabilities and Exposures
A public identifier for a specific disclosed vulnerability record.
See it in practice
The VPN finding should be tracked by CVE identifier so KEV membership can be checked without relying on a scanner nickname.
Connect the ideas: Threat, vulnerability, likelihood, impact, and uncertainty · Prioritize vulnerabilities and exposures
Explore CVE in practice ↗
Common Vulnerability Scoring System
FIRST’s method for describing characteristics and technical severity of a vulnerability, not a full remediation order.
See it in practice
Two CVSS-critical findings can still be queued differently once exposure and KEV are considered.
Connect the ideas: Threat, vulnerability, likelihood, impact, and uncertainty · Prioritize vulnerabilities and exposures
Explore CVSS in practice ↗
Dynamic application security testing
Testing a running application from the outside to find exploitable behavior.
See it in practice
DAST against TrackPort staging can show whether the parser proof-of-concept actually works.
Connect the ideas: Prioritize vulnerabilities and exposures · How systems communicate: network, DNS, HTTP, and TLS
Explore DAST in practice ↗
Data classification
Labeling records by the harm of disclosure, alteration, or loss so protection and retention can follow.
See it in practice
Customer addresses are confidential; public tracking FAQs are not in the same class.
Connect the ideas: What we protect: assets, confidentiality, integrity, and availability · Data protection, updates, backups, and resilience
Explore Data classification in practice ↗
Defense in depth
Layering independent controls so that one failure does not become a complete compromise.
See it in practice
MFA plus scoped tokens plus a contractor VLAN still matter if any one of them is mis-set.
Connect the ideas: Least privilege, secure defaults, trust boundaries, and layered controls · From principles to frameworks and product categories
Explore Defense in depth in practice ↗
Data loss prevention
Controls that detect or block sensitive data leaving a channel such as email, web, or endpoint.
See it in practice
DLP on email could have blocked the address export, but only if TrackPort fields were classified.
Connect the ideas: What we protect: assets, confidentiality, integrity, and availability · Data protection, updates, backups, and resilience
Explore DLP in practice ↗
Domain Name System
The lookup system that maps a name people type to an address a computer can contact.
See it in practice
If DNS for track.riverstone.example points at an unexpected IP, the customer may never reach Riverstone.
Connect the ideas: How systems communicate: network, DNS, HTTP, and TLS
Explore DNS in practice ↗
Endpoint detection and response
Telemetry and response capability on laptops and servers for process, file, and similar host activity.
See it in practice
EDR showing no FleetLink process contradicts a FleetLink user-agent and becomes useful tension in the case.
Connect the ideas: Triage a synthetic identity alert · Investigate, respond, and verify recovery
Explore EDR in practice ↗
Encryption
Transforming data so only holders of the appropriate key can read it, protecting confidentiality in transit or at rest.
See it in practice
TLS encrypts the TrackPort session; it does not encrypt backups if those copies are stored in cleartext elsewhere.
Connect the ideas: How systems communicate: network, DNS, HTTP, and TLS · Data protection, updates, backups, and resilience
Explore Encryption in practice ↗
Exploit Prediction Scoring System
FIRST’s estimate of the probability that a vulnerability will be exploited in the wild over the next 30 days.
See it in practice
A low EPSS on the wiki plugin is a forecast, not a promise it will never be used against Riverstone.
Connect the ideas: Threat, vulnerability, likelihood, impact, and uncertainty · Prioritize vulnerabilities and exposures
Explore EPSS in practice ↗
Evidence
A record you are willing to cite in a decision, with enough provenance to explain what it can prove.
See it in practice
A raw TrackPort export log with collection time is evidence; a Slack rumor is not.
Connect the ideas: Logs, alerts, and evidence · Investigate, respond, and verify recovery
Explore Evidence in practice ↗
Exploit
A method or code that uses a vulnerability to cause an unauthorized effect.
See it in practice
A public proof-of-concept against TrackPort’s document parser is an exploit path, not yet proof of local use.
Connect the ideas: Threat, vulnerability, likelihood, impact, and uncertainty · Prioritize vulnerabilities and exposures
Explore Exploit in practice ↗
Exposure
Whether and how a vulnerability or service can actually be reached in this environment.
See it in practice
An internal wiki plugin has less exposure than an internet-facing VPN even with a similar CVSS.
Connect the ideas: Threat, vulnerability, likelihood, impact, and uncertainty · Prioritize vulnerabilities and exposures
Explore Exposure in practice ↗
False positive
An alert that did not represent the harmful event the detector was meant to catch.
See it in practice
A VPN egress that looks like impossible travel can be a false positive for “stolen account” and still worth a look.
Connect the ideas: Logs, alerts, and evidence · Triage a synthetic identity alert
Explore False positive in practice ↗
Federation
Trusting authentication assertions from an external identity provider instead of storing every password locally.
See it in practice
FleetLink federates to Riverstone’s identity provider, so TrackPort should not keep a second password for Jordan.
Connect the ideas: Identity, authentication, authorization, and recovery · Least privilege, secure defaults, trust boundaries, and layered controls
Explore Federation in practice ↗
Governance, risk, and compliance
The organizational functions that set policy, track risk, and collect assurance evidence. Not a product that grants safety.
See it in practice
GRC can own the exception record when the VPN patch waits for a maintenance window.
Connect the ideas: From principles to frameworks and product categories · Prioritize vulnerabilities and exposures
Explore GRC in practice ↗
Hashing
A one-way fingerprint of data used to detect change or store verifiers, not a reversible way to hide records you must later read.
See it in practice
Hashing bills of lading can detect tampering; it cannot restore the document after ransomware.
Connect the ideas: What we protect: assets, confidentiality, integrity, and availability · Data protection, updates, backups, and resilience
Explore Hashing in practice ↗
Hypertext Transfer Protocol
The application protocol that names methods, paths, headers, and bodies for web requests.
See it in practice
GET /exports/addresses with a session cookie is an HTTP request whose meaning TrackPort must authorize.
Connect the ideas: How systems communicate: network, DNS, HTTP, and TLS · Identity, authentication, authorization, and recovery
Explore HTTP in practice ↗
Identity and access management
The capability for creating identities, authenticating them, authorizing actions, and managing their lifecycle.
See it in practice
IAM is how Riverstone should issue contractor accounts with an expiry instead of sharing a clipboard password.
Connect the ideas: Identity, authentication, authorization, and recovery · From principles to frameworks and product categories
Explore IAM in practice ↗
Idempotency
The property that repeating the same operation has the same intended effect on state as performing it once; separate audit records may still be created.
See it in practice
Disable-account should be idempotent; retrying a transfer of funds or a unique firewall rule may not be.
Connect the ideas: Investigate, respond, and verify recovery · Understand and build toward an Agentic SOC
Explore Idempotency in practice ↗
Identity
The record an organization uses for a person, device, or workload that can be authenticated.
See it in practice
jordan.h is an identity record; it is not automatically the human Jordan Hale.
Connect the ideas: Identity, authentication, authorization, and recovery · Triage a synthetic identity alert
Explore Identity in practice ↗
Identity governance and administration
Processes and tools for reviewing who should have which access and removing what is no longer justified.
See it in practice
An IGA review should have caught jordan.h still sitting in Warehouse-Admins after the Friday job ended.
Connect the ideas: Least privilege, secure defaults, trust boundaries, and layered controls · From principles to frameworks and product categories
Explore IGA in practice ↗
Impact
How badly people or the business are hurt if the loss actually happens.
See it in practice
Taking the driver VPN down stalls FleetLink assignments and the Oakland dock wave.
Connect the ideas: What we protect: assets, confidentiality, integrity, and availability · Threat, vulnerability, likelihood, impact, and uncertainty
Explore Impact in practice ↗
Incident
An event or set of events that actually or potentially causes a security loss requiring coordinated handling.
See it in practice
The unassigned address export is an incident even if Jordan later proves the travel was real.
Connect the ideas: Logs, alerts, and evidence · Investigate, respond, and verify recovery
Explore Incident in practice ↗
Indicator of compromise
An observable such as an address, hash, or account pattern that may indicate a compromise, with limited shelf life.
See it in practice
203.0.113.40 is an IOC candidate for this case, not a permanent blocklist of a whole country.
Connect the ideas: Triage a synthetic identity alert · Investigate, respond, and verify recovery
Explore Indicator of compromise in practice ↗
Integrity
The property that data and processes remain complete and unaltered except by authorized action.
See it in practice
A dock scanner marking a full pallet empty attacks integrity so the goods can be stolen.
Connect the ideas: What we protect: assets, confidentiality, integrity, and availability · Data protection, updates, backups, and resilience
Explore Integrity in practice ↗
Internet Protocol address
A numeric locator used to deliver packets to a host on a network.
See it in practice
203.0.113.40 in the 02:14 log is an address, not proof of which human held the phone.
Connect the ideas: How systems communicate: network, DNS, HTTP, and TLS · Triage a synthetic identity alert
Explore IP address in practice ↗
Known Exploited Vulnerabilities
CISA’s catalog of vulnerabilities with evidence of exploitation in the wild.
See it in practice
The VPN’s KEV listing is observed evidence from somewhere; it is not a Riverstone incident by itself.
Connect the ideas: Threat, vulnerability, likelihood, impact, and uncertainty · Prioritize vulnerabilities and exposures
Explore KEV in practice ↗
Least privilege
Granting each identity only the actions, objects, and time window required for the current job.
See it in practice
Contractor access to dock 3 on Friday is least privilege; Warehouse-Admins is not.
Connect the ideas: Least privilege, secure defaults, trust boundaries, and layered controls · Investigate, respond, and verify recovery
Explore Least privilege in practice ↗
Likelihood
How plausible it is that a threat will cause a loss in this environment, given exposure and evidence.
See it in practice
Internet exposure plus a KEV listing raises likelihood for the VPN relative to an internal wiki plugin.
Connect the ideas: Threat, vulnerability, likelihood, impact, and uncertainty · Prioritize vulnerabilities and exposures
Explore Likelihood in practice ↗
Log
A record emitted by a system that something happened, which may later be used as evidence.
See it in practice
The identity-provider line at 02:14 is a log, not a conclusion about Jordan’s intent.
Connect the ideas: Logs, alerts, and evidence · Triage a synthetic identity alert
Explore Log in practice ↗
Managed detection and response
A service that combines tooling with people who triage and investigate on a customer’s behalf.
See it in practice
MDR can watch Riverstone overnight, but Riverstone still owns authorization for destructive actions.
Connect the ideas: From principles to frameworks and product categories · Understand and build toward an Agentic SOC
Explore MDR in practice ↗
Mean time to detect
An operational metric for how long events of a type remain unnoticed; it is only as honest as the clock and the catalog of events.
See it in practice
If export logs are delayed 40 minutes, MTTD for export abuse cannot be five minutes no matter the alert banner.
Connect the ideas: Logs, alerts, and evidence · Triage a synthetic identity alert
Explore Mean time to detect in practice ↗
Multifactor authentication
Authentication that requires more than one factor, such as something you know plus something you have.
See it in practice
Riverstone’s phone prompt is MFA, and a two-second approval can still be social engineering.
Connect the ideas: Identity, authentication, authorization, and recovery · Triage a synthetic identity alert
Explore MFA in practice ↗
Network detection and response
Detection and investigation based on network traffic or metadata rather than host agents alone.
See it in practice
NDR might show an unusual volume of encrypted outbound traffic even if a laptop’s EDR agent was tampered with; encrypted metadata alone does not reveal the request’s contents.
Connect the ideas: How systems communicate: network, DNS, HTTP, and TLS · From principles to frameworks and product categories
Explore NDR in practice ↗
Non-repudiation
Evidence supporting a claim that a particular party originated or approved something, so a later denial can be evaluated. Reliable identity binding and record integrity matter.
See it in practice
A digitally signed approval can support a later dispute about who authorized a shipment; a shared login and an editable log cannot provide the same assurance.
Connect the ideas: Identity, authentication, authorization, and recovery · Logs, alerts, and evidence
Explore Non-repudiation in practice ↗
Privileged access management
Controls that broker, record, and constrain powerful administrative identities and sessions.
See it in practice
YardOS admin should go through PAM so a vendor is not dropped into Warehouse-Admins for convenience.
Connect the ideas: Least privilege, secure defaults, trust boundaries, and layered controls · From principles to frameworks and product categories
Explore PAM in practice ↗
Patch
A vendor or internal change that removes or reduces a vulnerability in running software.
See it in practice
Patching the VPN is not verified until the version string and management exposure are checked.
Connect the ideas: Data protection, updates, backups, and resilience · Prioritize vulnerabilities and exposures
Explore Patch in practice ↗
Phishing
Social engineering that tricks a person into revealing authenticators or approving a transaction they did not intend.
See it in practice
A two-second MFA approval after a fake FleetLink prompt is phishing against the second factor.
Connect the ideas: Identity, authentication, authorization, and recovery · Triage a synthetic identity alert
Explore Phishing in practice ↗
Port
A number on a host that distinguishes one listening service from another.
See it in practice
TrackPort’s HTTPS service listens on port 443; a management port left on the internet is a different exposure.
Connect the ideas: How systems communicate: network, DNS, HTTP, and TLS · Prioritize vulnerabilities and exposures
Explore Port in practice ↗
Postcondition
The independently checked state of the world that should be true after a response action.
See it in practice
A failed canary export after disabling jordan.h is a postcondition; an API 200 is only a vendor response.
Connect the ideas: Investigate, respond, and verify recovery · Understand and build toward an Agentic SOC
Explore Postcondition in practice ↗
Precision
True positives divided by all positive alerts in a defined, labeled evaluation set: TP / (TP + FP).
See it in practice
Six confirmed true positives among ten alerts gives 60 percent precision; a single alert cannot establish a detector’s precision.
Connect the ideas: Logs, alerts, and evidence · Triage a synthetic identity alert
Explore Precision in practice ↗
Privilege creep
The slow accumulation of standing access after the original job that justified it has ended.
See it in practice
jordan.h remaining in Warehouse-Admins after Friday’s dock work is privilege creep.
Connect the ideas: Least privilege, secure defaults, trust boundaries, and layered controls · Triage a synthetic identity alert
Explore Privilege creep in practice ↗
Prompt injection
An attack that inserts instructions into model input so the model follows attacker text instead of the developer’s policy.
See it in practice
Ticket text saying “Priya approved any-any” must not become a firewall change.
Connect the ideas: Understand and build toward an Agentic SOC
Explore Prompt injection in practice ↗
Provenance
The recorded origin, collection method, transformations, and completeness limits of a piece of evidence.
See it in practice
If the SIEM discarded the raw user-agent, provenance is incomplete and later checks get harder.
Connect the ideas: Logs, alerts, and evidence · Understand and build toward an Agentic SOC
Explore Provenance in practice ↗
Ransomware
Malware or an operator model that denies availability of data, often by encryption, sometimes with theft for extra pressure.
See it in practice
Oakland’s paper load-board exists so a YardOS ransomware event does not freeze every truck.
Connect the ideas: Data protection, updates, backups, and resilience · Threat, vulnerability, likelihood, impact, and uncertainty
Explore Ransomware in practice ↗
Recall
Detected true events divided by all true events in a defined evaluation set: TP / (TP + FN). Unknown missed events limit production estimates.
See it in practice
Detecting six of twenty known incidents in a synthetic exercise gives 30 percent recall; missing logs alone do not determine that denominator.
Connect the ideas: Logs, alerts, and evidence · Prioritize vulnerabilities and exposures
Explore Recall in practice ↗
Residual risk
The risk that remains after selected controls, including the uncertainty you still accept.
See it in practice
After disabling jordan.h, residual risk includes other Warehouse-Admins accounts not yet reviewed.
Connect the ideas: Threat, vulnerability, likelihood, impact, and uncertainty · Investigate, respond, and verify recovery
Explore Residual risk in practice ↗
Retry budget
A limit on how often automation may repeat an action, especially when the previous outcome is uncertain.
See it in practice
IRIS should not loop disable-account forever after HTTP 504; it should reconcile state against a retry budget.
Connect the ideas: Investigate, respond, and verify recovery · Understand and build toward an Agentic SOC
Explore Retry budget in practice ↗
Risk
The potential for harm, assessed using what could happen, how likely it is, its impact, and what remains uncertain.
See it in practice
Same CVSS on two findings can still yield different risk once exposure and KEV are written down.
Connect the ideas: Threat, vulnerability, likelihood, impact, and uncertainty · From principles to frameworks and product categories
Explore Risk in practice ↗
Secure access service edge
A category combining wide-area networking with cloud-delivered security services.
See it in practice
SASE might carry contractor traffic, but YardOS still needs an application-level role for dock 3.
Connect the ideas: How systems communicate: network, DNS, HTTP, and TLS · From principles to frameworks and product categories
Explore SASE in practice ↗
Static application security testing
Analysis of source or bytecode for vulnerability patterns without running the program.
See it in practice
SAST might flag string concatenation in YardOS SQL, which is a different issue than the VPN KEV.
Connect the ideas: Prioritize vulnerabilities and exposures · From principles to frameworks and product categories
Explore SAST in practice ↗
Software bill of materials
An inventory of software components and their relationships, used to investigate exposure when vulnerabilities are disclosed.
See it in practice
An SBOM for TrackPort would tell Devon whether the parser library is in production before the scanner does.
Connect the ideas: Prioritize vulnerabilities and exposures · From principles to frameworks and product categories
Explore SBOM in practice ↗
Software composition analysis
Inspection of dependencies and libraries for known vulnerabilities and license issues.
See it in practice
SCA is how the medium-CVSS parser library showed up in the Friday backlog.
Connect the ideas: Prioritize vulnerabilities and exposures · From principles to frameworks and product categories
Explore SCA in practice ↗
Secrets management
Storing, rotating, and auditing passwords, keys, and tokens so they are not copied into chat or source.
See it in practice
The YardOS service account password on a clipboard is a secrets-management failure as well as an identity failure.
Connect the ideas: Identity, authentication, authorization, and recovery · Least privilege, secure defaults, trust boundaries, and layered controls
Explore Secrets management in practice ↗
Secure defaults
Initial settings that reduce avoidable exposure and protect users without requiring them to discover and enable essential safeguards.
See it in practice
A newly created TrackPort role should see zero shipments until a customer scope is added.
Connect the ideas: Least privilege, secure defaults, trust boundaries, and layered controls · Data protection, updates, backups, and resilience
Explore Secure defaults in practice ↗
Session
State linking multiple requests; an authenticated session associates later requests with a previously authenticated identity until it expires or is revoked.
See it in practice
Revoking jordan.h sessions is containment that does not require deleting the identity record.
Connect the ideas: Identity, authentication, authorization, and recovery · Investigate, respond, and verify recovery
Explore Session in practice ↗
Shared responsibility
The split of security duties between a cloud or SaaS provider and the customer, which varies by service.
See it in practice
The identity provider hosts MFA; Riverstone still decides who is in Warehouse-Admins.
Connect the ideas: Identity, authentication, authorization, and recovery · Data protection, updates, backups, and resilience
Explore Shared responsibility in practice ↗
Security information and event management
A capability that collects, parses, stores, and searches security telemetry and often fires alerts.
See it in practice
Riverstone’s SIEM joining identity and TrackPort logs is how Maya sees the 02:16 export beside the login.
Connect the ideas: Logs, alerts, and evidence · From principles to frameworks and product categories
Explore SIEM in practice ↗
Security orchestration, automation, and response
Tooling that runs playbooks across security systems, which still needs scoped authority and verification.
See it in practice
A SOAR play that disables accounts must not treat a model summary as the approval record.
Connect the ideas: From principles to frameworks and product categories · Understand and build toward an Agentic SOC
Explore SOAR in practice ↗
Security operations center
The people and process that detect, investigate, and respond to security events. Distinct from System and Organization Controls reporting.
See it in practice
Riverstone’s SOC is Maya’s on-call function, not an audit report named SOC 2.
Connect the ideas: Triage a synthetic identity alert · Investigate, respond, and verify recovery
Explore SOC in practice ↗
Security service edge
Cloud-delivered security services such as secure web access without requiring the networking half of SASE.
See it in practice
SSE can inspect outbound web traffic from dispatch laptops without being a substitute for IAM.
Connect the ideas: How systems communicate: network, DNS, HTTP, and TLS · From principles to frameworks and product categories
Explore SSE in practice ↗
Single sign-on
A pattern where one authentication to an identity provider is reused across multiple applications.
See it in practice
FleetLink and TrackPort both trust Harbor identity SSO, so a stolen SSO session is wider than one app password.
Connect the ideas: Identity, authentication, authorization, and recovery · Triage a synthetic identity alert
Explore SSO in practice ↗
SaaS security posture management
Configuration and access review for software-as-a-service tenants such as email or identity portals.
See it in practice
SSPM can show that the identity provider still allows SMS fallback after the passkey rollout.
Connect the ideas: Identity, authentication, authorization, and recovery · From principles to frameworks and product categories
Explore SSPM in practice ↗
Threat
A person, process, or event that might cause a loss to an asset.
See it in practice
Opportunistic ransomware crews scanning internet VPNs are a threat to Riverstone’s driver login path.
Connect the ideas: Threat, vulnerability, likelihood, impact, and uncertainty · Prioritize vulnerabilities and exposures
Explore Threat in practice ↗
Transport Layer Security
A protocol that encrypts and integrity-protects an application conversation and checks a certificate for a name.
See it in practice
TLS 1.3 can hide shipment HTML from cafe Wi-Fi without deciding which customer may see which trailer.
Connect the ideas: How systems communicate: network, DNS, HTTP, and TLS
Explore TLS in practice ↗
Triage
A short, time-boxed judgment of severity, uncertainty, and next action when an alert arrives.
See it in practice
Maya’s five-minute disable of jordan.h with a missing-log list is triage, not a completed investigation.
Connect the ideas: Triage a synthetic identity alert · Investigate, respond, and verify recovery
Explore Triage in practice ↗
Trust boundary
A place where identity, network, or data assumptions change and a fresh check is required.
See it in practice
The internet-to-VPN boundary is not the same as the application authorization boundary inside TrackPort.
Connect the ideas: How systems communicate: network, DNS, HTTP, and TLS · Least privilege, secure defaults, trust boundaries, and layered controls
Explore Trust boundary in practice ↗
Uncertainty
What you still do not know, written explicitly so it is not filled with false precision.
See it in practice
Maya does not know whether a geofence already limits VPN logins, so that stays an open question.
Connect the ideas: Threat, vulnerability, likelihood, impact, and uncertainty · Logs, alerts, and evidence
Explore Uncertainty in practice ↗
Vulnerability
A weakness in a system, process, or person that makes a loss easier to cause.
See it in practice
An unpatched VPN appliance is a vulnerability even before anyone exploits it at Riverstone.
Connect the ideas: Threat, vulnerability, likelihood, impact, and uncertainty · Prioritize vulnerabilities and exposures
Explore Vulnerability in practice ↗
Web application firewall
A control that inspects web application traffic and applies rules to detect or block unwanted requests, often including known attack patterns.
See it in practice
A WAF rule may buy time against the document-parser exploit; it does not patch TrackPort.
Connect the ideas: How systems communicate: network, DNS, HTTP, and TLS · Prioritize vulnerabilities and exposures
Explore WAF in practice ↗
Extended detection and response
A vendor category for stitching multiple telemetry sources; it is not automatic coverage of every outcome.
See it in practice
Buying XDR does not by itself prove TrackPort exports would be detected.
Connect the ideas: From principles to frameworks and product categories · Understand and build toward an Agentic SOC
Explore XDR in practice ↗
Zero trust
An architecture approach that grants no implicit trust from network location or asset ownership and evaluates access to resources using identity, device, and other context.
See it in practice
Zero trust does not mean “VPN is obsolete”; it means VPN membership is not authorization to data.
Connect the ideas: Least privilege, secure defaults, trust boundaries, and layered controls · Understand and build toward an Agentic SOC
Explore Zero trust in practice ↗
Zero trust network access
Access that brokers application connectivity per identity and policy instead of placing users on a flat network.
See it in practice
ZTNA to YardOS is still not authorization to export TrackPort addresses.
Connect the ideas: Least privilege, secure defaults, trust boundaries, and layered controls · From principles to frameworks and product categories
Explore ZTNA in practice ↗
No matches yet. Try a shorter word or the expanded acronym.