Portcullis

Secure, resilient remote door control system built with General Dynamics Mission Systems

NAU Capstone Project
CS 476/486C
2025 – 2026

Requirements

Software & Security Requirements

These are the requirements outlined by General Dynamics Mission Systems.

  1. The system shall notify operators with a cautionary alert when there is a change in the state of an intrusion detector.
  2. The system shall notify operators with a cautionary alert when actions to enter controlled areas are detected.
  3. The status panel shall indicate access status to a shelter.
  4. The intrusion detector shall support three states: no access, authorized access, and unauthorized access.
  5. The system shall report authorized and unauthorized entries to shelters to the Control Center via an IP interface.
  6. The system shall use protected mechanisms (e.g., passwords) to authenticate the identity of system operators and administrators.
  7. The system shall protect against internal and external unauthorized access. (Did confirm this means within the organization and outside the organization)
  8. Fixed facilities shall incorporate intrusion detection capabilities.
  9. Intrusion detectors shall monitor and automatically report status changes to the control center.
  10. The system shall maintain functionality and reliable communication over high latency (high ping 400ms) network connections.
  11. The system shall automatically recover from network outages and resume normal operations without manual intervention.
  12. The system shall perform software and firmware upgrades manually initiated and able to complete over high latency (high ping 400ms) network connections. In case of a network outage during the upgrade, the system shall ensure it does not leave the system in an unrecoverable state.
  13. The system shall support SNMPv3 for securely reporting intrusion status and system status.
  14. The system shall use current industry-standard encryption protocols (e.g., TLS, HTTPS) for secure communication between all parts of the system.
  15. The system shall keep a history of intrusion and system events/alarms for auditing and analysis purposes.

These requirements will be expanded and also further classified using the MoSCoW prioritization method. The categories are Must-Have (MHx), Should-Have (SHx), Could-Have (CHx), and Won't-Have (WHx) where the smaller number marks the more important requirement of the classified requirements.

Must-Have Functional Requirements

  1. FR1 (MH1) - The system shall notify operators with a cautionary alert when there is a change in the state of an intrusion detector.
  2. FR2 (MH2) - The system shall notify operators with a cautionary alert when actions to enter controlled areas are detected.
  3. FR3 (MH3) - The status panel shall indicate access status to a shelter.
  4. FR4 (MH4) - The intrusion detector shall support three states: no access, authorized access, and unauthorized access.
  5. FR6 (MH5) - The system shall use protected mechanisms (e.g., passwords) to authenticate the identity of system operators and administrators.

Should-Have Functional Requirements

  1. FR5 (SH1) - The system shall report authorized and unauthorized entries to shelters to the Control Center via an IP interface.
  2. FR7 (SH2) - The system shall protect against internal and external unauthorized access.
  3. FR8 (SH3) - Intrusion detectors shall monitor and automatically report status changes to the control center.
  4. FR9 (SH4) - The system shall support SNMPv3 for securely reporting intrusion status and system status.
  5. FR10 (SH5) - The system shall use current industry-standard encryption protocols (e.g., TLS, HTTPS) for secure communication between all parts of the system.
  6. FR11 (SH6) - The system shall automatically recover from network outages and resume normal operations without manual intervention.
  7. FR12 (SH7) - The system shall keep a history of intrusion and system events/alarms for auditing and analysis purposes.

Performance Requirements

  1. PR1 - The system shall maintain functionality and reliable communication over high-latency (400 ms) network connections.
  2. PR2 - The system shall perform software and firmware upgrades manually initiated and able to complete over high-latency (400 ms) network connections; in case of outage, the system must remain recoverable.

Environmental Requirements

  1. ER1 - Fixed facilities shall incorporate intrusion detection capabilities.

Above all, a critical requirement is the system's resilience; it must ensure continuous operation on high-latency networks and maintain its secure state through power and network outages.