We have been advising on protective security for complex built-environment projects for some time now. Along the way, we have developed views — grounded in evidence, tested in practice — on how security analysis and design integration ought to work.
This insights series is where we share those views publicly.
What to expect
Our posts will cover topics across our practice areas:
- Threat and risk analysis — how probabilistic thinking and structured analytical methods produce better security decisions than checklists and compliance matrices.
- CPTED and place-based safety — evidence-based crime prevention that respects design intent and urban amenity.
- Protective design — hostile vehicle mitigation, blast engineering, and structural hardening that integrates with architecture rather than fighting it.
- Assurance and verification — how to demonstrate that security requirements have been met, traced, and documented across the asset lifecycle.
Our position
We believe protective security belongs in the design — not bolted on after the fact, and not imposed as a set of prescriptive requirements that ignore project context. Good security advisory translates threat and vulnerability into implications, options, and trade-offs that design teams and decision-makers can actually use.
That is the standard we hold ourselves to, and these posts will reflect it.
Stay connected
Follow us on LinkedIn for updates, or check back here as we publish new material.