PlatPhorm Dictionary

Endpoint Evidence Chain is a security audit record that preserves how security evidence was collected and handled for user device and server protection. It uses timestamps, hashes, owners, and storage controls so teams can support trustworthy investigation while keeping evidence, reliability, and public-safe operational boundaries clear.

“The security team used Endpoint Evidence Chain when a workstation reported suspicious activity, so the team could support trustworthy investigation before the risk review began.”

Incident Response Policy Decision is a security authorization decision that determines whether an action should be allowed for security event handling. It uses identity, resource, context, and policy evaluation so teams can enforce least privilege while keeping evidence, reliability, and public-safe operational boundaries clear.

“The security team used Incident Response Policy Decision when an alert escalated to response, so the team could enforce least privilege before the risk review began.”

Identity Detection Rule is a security security analytic that matches suspicious behavior or known indicators for user and workload identity. It uses logs, thresholds, signatures, and behavioral context so teams can surface actionable alerts while keeping evidence, reliability, and public-safe operational boundaries clear.

“The security team used Identity Detection Rule when a service account requested access, so the team could surface actionable alerts before the risk review began.”

Latency Health Probe is a networking availability check that tests whether a service or path can receive traffic for time between request and response. It uses timed requests, thresholds, and regional checks so teams can send traffic only to healthy targets while keeping evidence, reliability, and public-safe operational boundaries clear.

“The network engineering team used Latency Health Probe when a user saw slow responses, so the team could send traffic only to healthy targets before traffic crossed a service boundary.”

HTTP Failover Policy is a networking resilience policy that defines when traffic should move to another path or region for application-layer request routing. It uses health signals, priorities, and cooldown windows so teams can recover from outages predictably while keeping evidence, reliability, and public-safe operational boundaries clear.

“The network engineering team used HTTP Failover Policy when a client retried a request, so the team could recover from outages predictably before traffic crossed a service boundary.”

Packet Ingress Rule is a networking boundary rule that controls how external traffic enters a service for unit of network transmission. It uses hostnames, paths, protocols, and policy checks so teams can keep entry points predictable while keeping evidence, reliability, and public-safe operational boundaries clear.

“The network engineering team used Packet Ingress Rule when packet loss increased, so the team could keep entry points predictable before traffic crossed a service boundary.”

Supply Chain Abuse Throttle is a security anti-abuse control that slows or blocks suspicious repeated behavior for dependencies, builds, and artifacts. It uses rate limits, reputation signals, and challenge steps so teams can protect public access without a login wall while keeping evidence, reliability, and public-safe operational boundaries clear.

“The security team used Supply Chain Abuse Throttle when a package update arrived, so the team could protect public access without a login wall before the risk review began.”

Secrets Patch Window is a security remediation schedule that sets when a fix should be applied for keys, tokens, and credentials. It uses risk severity, testing needs, and maintenance constraints so teams can repair systems without unnecessary disruption while keeping evidence, reliability, and public-safe operational boundaries clear.

“The security team used Secrets Patch Window when a secret appeared in logs, so the team could repair systems without unnecessary disruption before the risk review began.”

Identity Forensic Snapshot is a security investigation artifact that captures system state for later review for user and workload identity. It uses logs, configuration, hashes, and time-bounded data so teams can analyze incidents without changing evidence while keeping evidence, reliability, and public-safe operational boundaries clear.

“The security team used Identity Forensic Snapshot when a service account requested access, so the team could analyze incidents without changing evidence before the risk review began.”

Vulnerability Attack Surface is a security exposure model that lists reachable systems, actions, and trust boundaries for weakness tracking and remediation. It uses asset inventory, route discovery, and permission mapping so teams can prioritize risk reduction while keeping evidence, reliability, and public-safe operational boundaries clear.

“The security team used Vulnerability Attack Surface when a scanner found a critical issue, so the team could prioritize risk reduction before the risk review began.”