4.1 Legal Standards for Use of Force

4.1 Legal Standards for Use of Force

Quick Answer: A California security guard’s force authority is the authority of a private person, not a peace officer. California Penal Code rules on lawful resistance, self-defense, defense of others, and limited force during a lawful citizen’s arrest set the outer legal boundary. Your Private Patrol Operator (PPO) license conditions, client contract, and company use-of-force policy often set a stricter inner boundary. On post, you follow the most restrictive of those layers. Excessive force can trigger criminal prosecution, civil lawsuits, employer discipline, and Bureau of Security and Investigative Services (BSIS) action — and private security has no qualified immunity.

Why AUF Topic 1 Matters

Appropriate Use of Force (AUF) training begins with legal standards because every physical intervention is judged against them. The BSIS Power to Arrest and Appropriate Use of Force Training Manual (July 2023) and the AUF syllabus require guards to understand: (1) the statutes that authorize or limit force by private persons; (2) licensee and client contractual obligations; and (3) civil and criminal liability. If you memorize techniques without the legal frame, you will fail both the 100% PTA/AUF exam and real-world risk management.

This section trains the decision logic you must apply before, during, and after any use of force. Later sections cover the objectively reasonable standard, force options, duty to intercede, and BSIS incident reporting. Start here: what law allows, what your contract forbids, and what liability looks like when those diverge.

Layer 1 — California Statutes Governing Private-Person Force

Security guards registered under the Private Security Services Act (Business and Professions Code Chapter 11.5) are not peace officers. You do not have Penal Code 836 arrest powers or the specialized force frameworks written for sworn officers. Your force authority is generally the same as any other private person’s, shaped by:

Imminent threat is a recurring Manual concept: a future or speculative danger is not enough. Courts and the Manual emphasize that a bare statement of fear is insufficient — there must be objective facts known at the time. You will see this again in Section 4.2 under the objectively reasonable standard.

Deadly force for an unarmed guard is extraordinarily constrained. Even armed guards with a separate BSIS Firearms Permit face narrow necessity rules. Property theft, verbal threats without capacity, or a subject fleeing with merchandise do not authorize deadly force. If your post is unarmed, treat deadly force as almost never available — and never as a “policy option” for convenience.

Layer 2 — Licensee and Client Contractual Obligations (Often Stricter Than Law)

AUF Topic 1 explicitly includes licensee and client contractual obligations. This is a classic exam trap: something can be lawful for a private person yet forbidden on your post.

Examples of stricter-than-law controls:

• Client forbids physical contact except to protect life — you may not use soft-control holds for shoplifting detention even if PC 490.5 would allow reasonable nondeadly force elsewhere.
• PPO policy bans chemical agents or impact weapons even if you personally own a legal device.
• Post orders require “observe and report only” for all non-violent property crimes.
• Contract requires two-guard confirmation before any detention.

On-post rule: follow company policy and post orders unless they would require you to commit a crime. If policy is more restrictive than Penal Code authority, policy wins for employment and licensing purposes. Violating post orders to “do what the law allows” still exposes you to termination, civil claims framed around negligent hiring/supervision, and BSIS scrutiny of professional conduct.

Read post orders at the start of every shift. If orders are silent on force, ask the supervisor — silence is not permission to invent a continuum.

Layer 3 — Company Use-of-Force Policy Controls On-Post Conduct

Company use-of-force policy is the day-to-day control system. It typically defines:

1. Authorized force options (presence, verbal commands, empty-hand control, approved tools).
2. Prohibited techniques (chokeholds, strikes to the head, hog-tying, prone restraint beyond training, improvised weapons).
3. When to disengage and call law enforcement.
4. Reporting triggers (any physical contact, medical aid, police response).
5. Supervisor notification timelines (often immediate, independent of the BSIS 7-day rule).

Policy does not create new criminal-law powers. It can only restrict and clarify. A policy that told you to use force beyond what California law allows would be unlawful to follow. In practice, reputable PPO policies are tighter than the Penal Code — and that is intentional risk management.

Civil and Criminal Liability for Excessive Force

Private security has no qualified immunity. That means:

Excessive force is force that is not objectively reasonable under the totality of circumstances — too much force for the threat, force after the threat ends, force used as punishment, or force that violates training/policy in a way that causes harm. You can be personally named in a lawsuit even if the employer is also sued. Employer liability (respondeat superior / negligent hiring) does not erase personal liability.

Insurance and “I was just following orders” are not exam-safe answers. If a supervisor orders an unlawful battery, you still face criminal and civil exposure for participating.

Decision Framework Before Using Force

Use this checklist every time:

1. Is there an imminent unlawful threat to persons (preferred justification) or a lawful detention/arrest need with policy authorization?
2. What does post policy allow at this threat level?
3. Is a lower option available (presence, verbal, create distance, call police)?
4. Can I articulate objective facts (not “I felt weird”)?
5. Stop when control is gained — continued force after compliance is a liability magnet.

Scenario: Lawful Authority vs. Policy Ban

You work an unarmed lobby post. Policy: observe-and-report only; no physical detention. A visitor shoves a receptionist. You can lawfully defend the receptionist with reasonable force as a private person. Policy still binds your employment expectations — but life-safety exceptions usually exist in well-written policies. If the shove is over and the aggressor is walking away, chasing and tackling for “payback” is excessive, violates policy, and creates battery exposure. Defend life when necessary; do not invent punishment force.

Exam and Practice Link

/practice/ca-security-guardPractice questions with detailed explanations