Skip to content
S.G. Technologies
All insights
Compliance · 6 min read

Aligning physical security with ISO 31000 and ASIS standards

Standards aren't paperwork for its own sake. Anchoring physical security to ISO 31000 and ASIS guidance is what makes your decisions consistent, defensible and able to survive scrutiny.

When people hear “standards,” they often hear “paperwork” — a compliance tax that slows things down without making anyone safer. Used badly, that’s exactly what standards become. Used well, they do the opposite: they make security decisions consistent across sites and over time, and they give you something to point to when a board, a regulator or an insurer asks why you did what you did.

Two frameworks anchor most of the physical-security work we do: ISO 31000 for risk management and ASIS International guidance for security practice. Here’s what each contributes, and why the combination matters.

ISO 31000: a common language for risk

ISO 31000 isn’t a checklist of controls. It’s a way of thinking about risk that any part of the organisation can share. Its value is in the discipline it imposes:

  • Establish the context before assessing anything — what you’re protecting, for whom, and against what.
  • Identify, analyse and evaluate risks in a consistent way, so a risk at one site is weighed the same way as a risk at another.
  • Treat risks deliberately — accept, reduce, transfer or avoid — as a choice, not a default.
  • Monitor and review, because risk is not static.

The quiet benefit is comparability. When every site’s risk is assessed through the same lens, you can prioritise across the whole estate honestly. Without a shared framework, “this site feels risky” competes with “that site had an incident last year,” and budget follows whoever argues loudest.

ASIS: turning risk into security practice

Where ISO 31000 gives you the risk discipline, ASIS International guidance and its body of practice translate that into security specifics — how to assess physical protection, design layered controls, and benchmark what “good” looks like for surveillance, access control, perimeter and response.

ASIS also underpins the credentials that signal tested competence. Certifications like CPP (Certified Protection Professional), PSP (Physical Security Professional) and PCI (Professional Certified Investigator) exist because security judgement is hard to verify from the outside. They’re a shorthand for “this person has been examined against a recognised body of knowledge and is bound by a code of ethics.”

Why the combination beats either alone

ISO 31000 without security-specific practice gives you a sound process and vague controls. ASIS practice without a risk framework gives you good controls applied inconsistently. Together they close the loop:

  1. ISO 31000 ensures you’re solving the right risks, weighed consistently.
  2. ASIS practice ensures you’re solving them with sound security measures.
  3. The pairing produces decisions that are both justified (traceable to assessed risk) and competent (built on recognised practice).

That’s what makes a security posture defensible. “We followed a recognised risk process and applied recognised practice, and here is the evidence” is a position that holds up. “We bought what seemed sensible” is not.

It’s also a data-protection question

Physical security increasingly touches personal data — CCTV footage, access logs, visitor records. Aligning to recognised standards isn’t only about stopping intruders; it’s about handling that data responsibly, in line with Ghana’s Data Protection Act and equivalent privacy obligations. A standards-anchored approach builds that in rather than bolting it on later.

Making it practical

You don’t adopt a standard by printing it. In practice, alignment looks like:

  • A baseline assessment that benchmarks your current state against the framework, so you know your real gaps.
  • A prioritised plan that treats the highest risks first, with each action traceable to a finding.
  • A review cadence — re-assessment, documentation, retraining — because ISO 31000’s “monitor and review” is where most programmes quietly lapse.

Standards, applied this way, aren’t a brake on security. They’re what keeps it honest, consistent and able to withstand the scrutiny that serious security eventually attracts.

Want your physical security benchmarked against ISO 31000 and ASIS practice? Request an assessment and we’ll scope a gap analysis for your sites.

Share this article

Start with a risk assessment

Every SGT engagement starts with a structured, evidence-led assessment. Tell us about your sites and we'll scope it within one business day.

FAQ

Questions on this topic

What is ISO 31000 and how does it apply to physical security?
ISO 31000 is a risk-management standard rather than a checklist of security controls. Applied to physical security it imposes a shared discipline: establish the context (what you are protecting, for whom and against what), identify, analyse and evaluate risks in a consistent way, treat them deliberately by accepting, reducing, transferring or avoiding them, and monitor and review because risk is not static. Its quiet benefit is comparability across sites.
What does ASIS International guidance add that ISO 31000 does not?
ISO 31000 gives you the risk discipline; ASIS International guidance translates it into security specifics, such as how to assess physical protection, design layered controls and benchmark what good looks like for surveillance, access control, perimeter and response. ASIS also underpins credentials such as CPP, PSP and PCI, which signal that a practitioner has been examined against a recognised body of knowledge and is bound by a code of ethics.
Why should an organisation in Ghana align its physical security to ISO 31000 and ASIS standards?
Because it makes security decisions consistent across sites and over time, and defensible when a board, regulator or insurer asks why you did what you did. Saying you followed a recognised risk process, applied recognised practice and can show the evidence is a position that holds up; saying you bought what seemed sensible is not. It also builds responsible handling of CCTV footage, access logs and visitor records under Ghana's Data Protection Act into the programme from the start.
How do you implement ISO 31000 and ASIS alignment in a security programme?
You do not adopt a standard by printing it. Alignment takes three things: a baseline assessment that benchmarks your current state against the framework so you know your real gaps; a prioritised plan that treats the highest risks first, with each action traceable to a finding; and a review cadence of re-assessment, documentation and retraining. The monitor-and-review step is where most programmes quietly lapse, so the cadence matters as much as the first assessment.
Do security certifications such as CPP or PSP matter when choosing a security consultant?
They are a useful signal of tested competence. Security judgement is hard to verify from the outside, so ASIS certifications exist for that reason: CPP (Certified Protection Professional), PSP (Physical Security Professional) and PCI (Professional Certified Investigator). Each is shorthand for a person who has been examined against a recognised body of knowledge and is bound by a code of ethics, which is the assurance a client cannot easily obtain any other way.