Fundamental Principles and Concepts of a Security Operations Management System (SOMS)
What this domain tests
Domain 1 is the vocabulary and rationale layer of the exam. Questions ask you to separate concepts (risk versus risk treatment, client versus affected party), to recognise the principles the standard is built on, and to see how Plan–Do–Check–Act and the process approach shape every later clause.
Core rules and concepts
- SOMS: the interrelated processes used to plan, implement, monitor and improve private security operations so that legal, client and human-rights obligations are met.
- Who it applies to: private security companies and the organizations that contract them; it scales with the size and context of the operation.
- Two anchors: respect for human rights (International Bill of Human Rights; UN Guiding Principles on Business and Human Rights) and the rule of law. These are design inputs, not optional add-ons - they drive assessment and control.
- Supporting principles: proportionality, accountability, transparency, due diligence, continual improvement.
- Risk-based thinking: controls come from two linked assessments - security risk and human rights risk - not from habit or tradition.
- PDCA: Plan (context, risk, objectives), Do (operational control), Check (monitoring, internal audit, management review), Act (corrective action, improvement).
- Process approach: each process has an owner, inputs, outputs, criteria and monitoring.
Worked example
A guarding contract at a port. A guard detains a trespasser for 40 minutes before police arrive. Trace it: the clause 6 planning risk assessment had flagged unlawful detention as a human-rights risk; clause 8 operational control required immediate handover to authorities plus a written incident report; competence requirements demanded documented training; the incident was logged, reviewed at management review, and a corrective action amended the handover procedure. Risk → control → competence → record → review → improvement is the answer structure the exam rewards.
Traps that cost marks
- Treating human rights as a separate CSR programme rather than as a design input to daily operations.
- Assuming the standard forbids use of force; it requires lawful, proportionate, minimum force with accountability.
- Confusing the client (who buys the service) with an affected party (who feels its effects).