At a Glance
After an attack on a nearby international compound in Kabul breached the perimeter and exposed serious failures in its planning and command, Jay Jordan was selected by senior regional management to build a complete security infrastructure for a replacement site housing more than 350 international personnel.
The selection was based specifically on his systems-based approach to security planning. The site had no coherent security structure, no emergency response plans and only minimal access control in place when the project began. Everything had to be built from the ground up, in one of the most dangerous cities in the world.
Over ten months, a complete security infrastructure was designed and implemented: hardened access control, integrated surveillance, a structured command framework, detailed emergency response planning for every credible scenario, and a combined security force of 108 personnel organised and managed under a unified operating doctrine. The guiding principle throughout was to control the environment before any incident began, rather than rely on response alone. The compound suffered no successful attack or breach during the entire operational period.
Operational Overview
Location
North Kabul, Afghanistan
Period
September 2019 – July 2020
Environment
Active conflict zone — one of the highest-threat environments globally during the period
Personnel protected
350+ international staff, NGO workers and operational teams
Security force managed
100+ personnel, including Gurkha and local national guard elements
Threat environment
Coordinated attacks, vehicle-borne explosive devices, insider threats, indirect fire, kidnap
Role
Jay Jordan — Project & Security Manager
Outcome
Zero successful attacks or breaches across the entire ten-month operational period
The Threat Environment
Kabul during 2019 and 2020 was one of the highest-threat environments in the world. International compounds operating in the city faced a realistic and near-term threat from coordinated complex attacks designed to breach perimeters and overwhelm security forces, vehicle-borne explosive devices targeting entry points, suicide attacks, insider threats from within the workforce, indirect fire including rockets and grenades, and kidnap operations targeting foreign nationals.
The compound faced heightened exposure due to its concentration of international personnel, its proximity to high-value diplomatic and military facilities, and the sustained operational activity of multiple armed groups within the city. Serious incidents against international facilities in Kabul during this period were not exceptional occurrences. They were a regular feature of the operating environment.
Any security infrastructure built for this site had to be capable of withstanding not one type of attack but many, including simultaneous and sustained hostile incidents, without losing command coherence or placing personnel at greater risk through confusion in the response.
The Compound
fThe compound was a substantial facility in North Kabul, previously occupied by the German military. It consisted of five multi-storey accommodation blocks, office infrastructure, dining facilities, medical facilities, gymnasium and welfare areas, hardened perimeter systems and multiple entry control points. It was designed to house more than 300 personnel in single occupancy accommodation and at the time of the project was housing over 350 international staff, multinational NGO personnel and operational management teams.
The compound’s proximity to a British Embassy annex led to the development of working relationships with British military elements and Afghan security forces, which later became an important part of the mutual support framework built during the project.
Despite its physical scale, the site was operationally highly vulnerable when the project began. There was no coherent security structure, no emergency response plans, no integrated surveillance capability, no unified command framework and only minimal access control in place. The guard force that existed was not operating under a coherent doctrine. The project required the complete development of a security infrastructure from nothing.
The Challenge
The project was initiated following a catastrophic attack on a previous accommodation compound housing international personnel in Kabul. Insurgents successfully breached the site. The attack exposed serious and systemic failures across defensive planning, command structure, access control and emergency response. What became clear was that the conventional approach to compound security, a guard force, a fence and a plan that had never been properly tested, was fundamentally inadequate for the environment.
Following the incident, senior regional management specifically selected Jay Jordan to lead the replacement project. The selection was based explicitly on his systems-based approach to operational planning and security management. The requirement was not to replicate the previous model with more personnel or better equipment. The requirement was to build an entirely different kind of operating environment, one structured from the ground up to maintain order, command and protective coherence under the most serious of circumstances.
The Security Philosophy
The entire approach was built around one principle: control the environment before the attack begins.
The previous incident had demonstrated what happens when a security system is designed only to respond to threats. When something serious occurs in an uncontrolled environment, confusion follows. Command breaks down. Communication fails. The response compounds the problem rather than containing it.
The replacement site was designed around the opposite logic. Rather than waiting for an incident and responding to it, every element of the compound was structured to shape the conditions under which any incident would unfold. Who could enter the site and how. Where people could move and when. How information would flow during a crisis. Who held decision authority at each stage. What the response to each category of serious incident would be, in advance, before the pressure arrived.
This philosophy draws directly from experience in operating environments where the quality of planning done before an incident determines whether the response succeeds or fails. In genuinely high-threat environments, the decisions that matter most are not made in the moment. They are made in the weeks and months before anything happens. The role of the security infrastructure is to ensure that when something does happen, the response is already structured, already rehearsed and already unambiguous.
Every design decision made at the compound, from the physical layout of entry points to the communications protocols in the operations room, was made with that logic as its foundation.
What Was Built
Over ten months, a complete security infrastructure was designed, built and implemented across the site. The scope of the work included the following components:
01. Security risk assessment
A comprehensive assessment of vulnerabilities was developed across every element of the compound: perimeter, access points, accommodation blocks, life-support systems, surveillance capability, emergency response readiness and medical limitations. Threat scenarios were modelled, attack likelihood assessed and mitigation priorities established in order of consequence. This assessment formed the foundation for every subsequent decision.
02. Access control and entry management
The compound’s entry systems were completely redesigned and hardened. Layered access control was introduced across all entry points, with structured vehicle and pedestrian screening, reinforced control procedures, access authorisation frameworks and lockdown capability. The objective was to ensure that no unauthorised person could move freely within the compound and that any hostile actor attempting to breach the perimeter encountered a structured, controlled environment rather than an open one.
03. Surveillance and monitoring
A surveillance system was integrated across the full compound and connected to a central operations room, monitored continuously. The system provided real-time visibility of all entry point activity and perimeter conditions, allowing the operations room to maintain situational awareness across the entire site at all times.
04. Command and communications
One of the primary lessons from previous incidents in Afghanistan was the collapse of command and communications during active hostilities. A structured command hierarchy was established with clear response protocols, communications procedures, accountability systems and coordinated lockdown procedures. The operations room maintained active communication capability with external military and police coordination structures. During any serious incident, there was no ambiguity about who held authority, what the response would be and how information would flow.
05. Emergency response planning
Detailed response frameworks were developed for a full range of serious scenarios: a perimeter breach, a mass casualty incident, an insider threat, an evacuation, an indirect fire attack and a prolonged lockdown. Every credible scenario was planned for, documented and understood by the relevant personnel before any of them occurred.
06. Rapid response and external support
A dedicated rapid response structure was established and coordinated with external support elements including Afghan National Police Special Forces, military assets and allied security partners in the area. Mutual support protocols and escalation procedures were established to ensure that external reinforcement could be called upon and integrated quickly and coherently when required.
07. Guard force organisation and management
A combined security force of 108 personnel was organised, trained and managed under a unified operating framework. This included Gurkha guard force personnel, local national guards, security supervisors and operational management staff. The primary challenge was coordinating all armed personnel under a single, coherent operational doctrine capable of functioning effectively during the stress and pressure of an active attack, without the breakdown in command coherence that had characterised the previous incident.
08. Physical hardening and site redesign
The compound’s physical layout was assessed and restructured. Controlled movement corridors were established, defensive positions were set, structural choke points were introduced and emergency shelter capability was reviewed and strengthened. The design ensured that any hostile actor who breached the outer perimeter would immediately encounter a controlled, structured defensive environment rather than the freedom of movement that had made previous incidents so difficult to manage.
09. SOP development
A complete framework of operating procedures was developed covering all aspects of security operations on site: access management, guard force conduct, incident reporting, emergency response, communications protocols, visitor handling and command procedures. For the first time, everyone operating on the compound was working from the same documented, understood and enforced framework.
Operational Outcomes
The project successfully achieved all primary objectives. The compound was transformed from a site with no coherent security structure into a hardened, fully coordinated operating environment with a tested infrastructure and an unambiguous command framework.
Outcome
Result
Operational period
10 months
Personnel protected
350+
Security personnel managed
100+
Successful attacks or breaches
Zero
Command or communications failures during the period
Zero
Emergency response frameworks developed
Full suite covering all credible scenarios
External support structures established
Afghan National Police Special Forces, military elements, allied partners
Key Capabilities Demonstrated
01. Designing security infrastructure from the ground up
The full assessment of an exposed, vulnerable environment and the complete build of a coherent, tested and operational protective system where nothing usable previously existed.
02. Systems-based security thinking
Building protection as one connected, interdependent system, where every element, from access control to command structure to emergency planning, is designed to support every other element. The result is a security environment that holds coherence under pressure rather than fragmenting at the moment it is most needed.
03. Managing large, complex security operations
Organising and leading a multinational security force of 108 personnel, coordinating with external military and police structures, and maintaining operational coherence across a site housing more than 350 people over a sustained ten-month period.
04. Command clarity under pressure
Designing command and communications structures that maintain integrity during serious incidents, so that the response to any event is immediate, organised and controlled, and no time is lost to confusion or unclear authority.
05. Comprehensive threat and vulnerability assessment
Identifying and prioritising risk across the full operating environment, from physical access to personnel conduct to emergency response capability, and addressing those risks in order of consequence rather than visibility.
06. Emergency preparedness
Developing and operationalising detailed response frameworks for the full range of serious scenarios before any of them occurred, so that the response to any incident is planned rather than improvised.
07. Sustained operational management
Maintaining the integrity of a complex, multi-layered security infrastructure over a ten-month operational period in a genuinely hostile environment, with zero successful incidents against the compound.
What This Means for Our Clients
The environments are different. The discipline is not.
Whether the requirement is a private residence, a family office managing multiple principals and properties, an executive whose profile has changed, or an organisation managing sensitive operations, the approach Pegasus Ops brings is the same one that protected 350 people in Kabul.
Understand the environment fully before recommending anything. Identify where the real vulnerabilities are, not just the obvious ones. Build protection that works as one connected system rather than a set of separate measures. Establish clear lines of authority and clear response frameworks before they are needed. And ensure that when something does happen, the response is already structured.
Private clients do not face the threats that compound in Kabul faced. But the failures that make security systems inadequate are the same in every environment: fragmented planning, unclear command, untested responses and an assumption that visible presence is the same thing as genuine protection. That thinking, applied in proportion to every environment we work in, is what every client receives.