Definition
Monitoring electronic lock and door hardware states and access events (e.g., locked/unlocked, access granted/denied, door forced/held, tamper) to detect and respond to unauthorized entry.
How it works
Electronic lock monitoring collects status and events from door controllers, readers (badge/PIV, keypad), and door hardware (door position switch, request-to-exit, bolt/latch, tamper). The physical access control system (PACS) logs access decisions, correlates door-held/forced conditions, and generates alarms for response. Secure, supervised reader links, such as Open Supervised Device Protocol (OSDP), help detect wiring faults and reduce credential interception. Integration with video systems can pop relevant camera views on lock-related alarms.
Considerations
- Use encrypted, supervised reader-to-controller protocols to protect credentials and detect wiring faults.
- Harden door controllers and isolate the PACS network to limit the attack surface.
- Configure fail-safe or fail-secure behavior and emergency release to meet life-safety requirements.
- Tune alarms for door-held, door-forced, and invalid retries to reduce noise while catching misuse.
- Supervise inputs, provide backup power, and regularly test door, bolt, and tamper sensors to ensure reliability.
Implementation perspective
Electronic Lock Monitoring should be treated as a technical defensive capability rather than a product checkbox. In practice, teams should define the protected scope, the conditions under which the technique acts, and the observable evidence that demonstrates the intended behavior. For this technique, likely engineering context includes the relevant system, activity, and evidence sources.
Use the technique to identify suspicious, unauthorized, or abnormal activity through observable evidence and repeatable analysis.
Questions to ask
- Which events, states, or artifacts must be observed for the analysis to work?
- What analytic logic, threshold, comparison, or signature turns observations into a finding?
- How are expected false positives, blind spots, and environmental variations documented?
- Who receives the result, and what action is expected when the technique produces a finding?
Evidence and validation
- Telemetry and data-source configuration records
- Analytic logic, thresholds, signatures, and version history
- Test cases demonstrating expected positive and negative results
- Alert, triage, escalation, and tuning records
Common failure patterns
- Required telemetry is missing, delayed, or transformed in a way that invalidates the analysis.
- The technique produces alerts without an accountable triage and response process.
- Detection coverage is claimed from product deployment without testing the relevant analytic behavior.
This implementation perspective is original Bare Metal Cyber educational content. It does not replace the official D3FEND definition or establish that a specific product implements the technique.
Technique hierarchy
Top-level family
Parent techniques
Direct child techniques
None listed at this level.
Artifacts and ontology entities
These relationships describe how D3FEND connects a defensive technique to artifacts or other ontology entities. They describe graph semantics, not a product certification.
Explicit technique relationships
Authoritative sources
- Open this technique on the official D3FEND website ↗
- Open the official ontology resources ↗
- FIPS 201-3: Personal Identity Verification (PIV) of Federal Employees and Contractors ↗NIST · SpecificationReference
- Guidelines for the Use of PIV Credentials in Facility Acces ↗NIST · GuidelineReference
- NIST Special Publication 800-53 Revision 5 - Security and Privacy Controls for Information Systems and Organizations ↗NIST · GuidelineReference
- Open Supervised Device Protocol (OSDP) v2.2 ↗Security Industry Association (SIA) · SpecificationReference
Bare Metal Cyber is an independent educational publisher and is not affiliated with or endorsed by The MITRE Corporation. MITRE D3FEND™ and the D3FEND logo are trademarks of The MITRE Corporation. MITRE ATT&CK® and ATT&CK® are registered trademarks of The MITRE Corporation. Use of D3FEND source material is subject to the official Terms of Use.