START WITH THE FOUNDATIONS

Physical Security Foundations

Connect detection, access decisions and recorded evidence.

Free · No sign-in required3 lessonsWorked examples & practiceBeginner

0 of 3 lessons checked · Progress is saved in this browser.

  1. 01 / SYSTEM VIEWCredential or event
  2. 02 / SYSTEM VIEWDecision
  3. 03 / SYSTEM VIEWResponse and evidence

This map connects the course ideas; it is not a detailed engineering schematic.

LESSON 1 / 3 · FREE

Authentication versus access decisions

Your goal: Distinguish identification from permission to enter.

Understand the idea

A credential identifies an asserted user or token. The controller applies a policy involving permissions, time and door state. Logging an event is not the same as granting access, and possession of a credential does not establish every permission. Life-safety behavior requires its own approved design.

Worked example

A fictional log shows 80 granted and 20 denied requests. Grant fraction is 80 percent; this is a usage observation, not a target security score.

Try it yourself

For 90 granted requests among 120 total, find grant percentage.

Should knowing a user’s identity automatically grant every door?

Background reference ↗ · Original teaching text and fictional practice values.

Continue to lesson 2: Pixels and scene coverage →

LESSON 2 / 3 · FREE

Pixels and scene coverage

Your goal: Interpret a supplied horizontal sampling estimate.

Understand the idea

A camera distributes image pixels across a field of view. Dividing horizontal pixels by scene width gives an average horizontal sampling estimate at a specified plane. Lighting, optics, compression, motion and angle affect useful detail; pixel arithmetic alone does not guarantee recognition.

Worked example

A 1,920-pixel image spanning 12 m averages 160 pixels/m at that plane. It is not a universal identification requirement.

Try it yourself

A supplied 1,600-pixel image spans 8 m. Find average pixels per meter.

Does this average guarantee face identification?

Background reference ↗ · Original teaching text and fictional practice values.

Continue to lesson 3: Recording storage →

LESSON 3 / 3 · FREE

Recording storage

Your goal: Estimate data volume using a supplied average rate.

Understand the idea

Video storage depends on actual encoded rate, time and retention policy. Use consistent bits and bytes, and account for overhead and variability when planning. Access to recordings and retention decisions are organizational privacy and security controls, not simply disk-capacity settings.

Worked example

A constant 8 megabits/s stream is 1 MB/s in decimal units, or 3,600 MB in one hour before overhead.

Try it yourself

At 4 megabits/s for 1,000 seconds, calculate decimal megabytes.

Which rate should a storage estimate explicitly state?

Background reference ↗ · Original teaching text and fictional practice values.

Choose your next step →

Finish with evidence of your understanding.

Explain each worked example in your own words, check the units and identify one assumption that could change the result. Then use the linked labs or roadmap to apply the ideas to a broader task.

Practice progress is a study aid, not a professional qualification or proof of field competence.

Continue in Physical Security

Apply these foundations in an available course, lab or roadmap. The linked resource’s access rules still apply.

Open the full studio → · Choose another discipline →

About this introductory course

These original lessons use simplified models and explicitly supplied practice values. Calculations teach concepts; they do not select real equipment, establish code compliance or authorize field work. Follow the linked references and advanced resources for deeper study.

Updated · Study progress stays in this browser. There is no certificate or paid gate for these lessons.