Search the practice set
126 questions, 454 terms and 400 topics in 20 areas.
25 results for “Communicating Threat Models”
Cloud Pricing Models
The purchase options for cloud compute — on-demand, committed use, and spot — which differ by up to 90% for identical hardware.
Threat Modelling
A structured exercise that identifies what can go wrong with a design, before it is built, by walking the system's trust boundaries.
Attack Surface
The complete set of points where an untrusted actor can interact with a system — and the quantity that reduction genuinely reduces risk.
Burstable Instance
An instance that provides a low baseline CPU allocation and accrues credits while idle, spendable for short periods of full performance.
Causal Consistency
A model guaranteeing that operations which causally depend on one another are seen in the same order everywhere, while concurrent operations may be seen in any order.
Consistent Prefix Read
A guarantee that if a sequence of writes happens in a given order, a reader sees a prefix of that sequence — never an out-of-order subset.
Data-Flow Diagram
A diagram of how data moves between processes, stores and external entities, with trust boundaries drawn on it.
Instance Family
A group of instance types sharing a resource profile — general purpose, compute optimised, memory optimised, storage optimised, accelerated — chosen by which resource the workload…
Linearizability
The strongest single-object guarantee — every operation appears to take effect instantaneously at some point between its call and its return.
Read-Your-Writes Consistency
A session guarantee that a client always sees its own updates, even when reads are served from replicas that may lag.
STRIDE
A mnemonic for six threat categories — spoofing, tampering, repudiation, information disclosure, denial of service, elevation of privilege — walked across each component and data flow.
Run a threat model on a new payment integration: our service calls a third-party payment provider and receives webhooks. Where are the interesting threats?
Draw the boundaries first Three trust boundaries, and nearly every interesting threat lives on one of them: 1. User → our service (untrusted input, authenticate
A fleet of 200 instances averages 15% CPU and 85% memory. Finance wants a 40% cost reduction. What do you do?
The diagnosis The instance family is wrong. 15% CPU and 85% memory means the workload is memory bound running on general purpose or compute optimised instances,
A regulator asks whether customer data is encrypted. The team says yes, disks are encrypted. Is that a sufficient answer?
What disk encryption actually protects against Someone obtaining the physical medium or a raw storage snapshot. In a cloud context that means a provider employe
Communicating Threat Models
Making risk legible to people who will fund or accept it.
Cloud Pricing Models
On-demand, committed and spot, and the crossover arithmetic.
Compute Models
Instances, containers and functions, and what each is priced and shaped for.
Consistency Models
Linearizable, sequential, causal, eventual, and the session guarantees between them.
Operating Models
How delivery, platform and governance functions fit together.
Reference Models
Shared conceptual frames — layering, tiers, viewpoints — and their limits.
Threat Modelling
Walking trust boundaries with STRIDE before anything is built.
AI-Era Architecture
General material on architecting systems that include models.
Architecture Communication
General material on communicating architecture.
CQRS
Separating the write model from the read models that serve queries.
CQRS
Separate models for writing and reading, each optimised for its job.