|
Foundational
Requirement
|
SL-C Component Capability
|
SL-C Component Level Achieved
|
|
FR1 - IAC
Identification and Authentication Control
|
The requirement is met via password access (something you know) combined with the physical adapter (something you have) and specific procedure (something you know). The password identifies the user/role.
|
SL2
Authentication is strong enough to resist generic attacks (SL2). Strength depends on password quality enforcement by the device firmware.
|
|
FR2 - UC
Use Control
|
The user is identified by the password), the device implements role-based access control (RBAC): specific password for configuration, specific password for commissioning.
|
SL2/SL3
Relies entirely on the device's internal firmware and configuration tool to enforce role-based privileges based on the entered password.
|
|
FR3 - SI
System Integrity
|
The physical optical link provides intrinsic protection against sniffing/tampering on the wire. Integrity is further protected by basic communication protocols (e.g., checksum or redundant data).
|
SL3
The isolated, point-to-point connection and data redundancy strongly secures integrity against remote or easy internal attacks.
|
|
FR4 - DC
Data Confidentiality
|
Data is transmitted via an isolated optical beam. While the data itself might not be encrypted, the physical confinement grants inherent confidentiality (no sniffing on the network).
|
SL2
Confidentiality is met due to physical isolation.
|
|
FR5 - RDF
Restricted Data Flow
|
Absolute Separation: The interface is completely disconnected from the network.
|
SL4
Physical isolation provides the highest level of flow restriction.
|
|
FR6 - TRE
Timely Response to Events
|
The device must log security events locally, including successful and failed login attempts and configuration changes, linked to the identified user/role. The incorrect password attempt is recorded in the device's memory.
|
SL3
failed access attempts (incorrect password entry) are recorded in the device's log memory
|
|
FR7 - RA
Resource Availability
|
Not susceptible to network DoS. Protected by physical access controls and firmware lockout mechanisms for password attempts. If an incorrect password is entered, the device enters lockout that makes the resource unavailable to both attacker and legitimate user upon the first violation.
|
SL3
Isolation prevents network-based DoS. Availability is protected by lockout mechanisms, with the device entering lockout and signaling with a specific code upon incorrect password entry.
|