@@ -748,7 +748,6 @@ For backwards compatibility, use of other combinations of options other what is
### 5.2.5 Software Bill of Materials
<mark>AMS: Stefane is working on this. Skip for now.</mark>
-**[REQ-SBOM-0]:** Operating system dependencies and application dependencies are clearly separated in the provided SBOM.
-**[REQ-SBOM-1a]:** Unique, unambiguous, and machine-readable identification of all components and dependencies are provided in the SBOM.
@@ -785,18 +784,7 @@ In addition, the managed device can have a configuration port, management API, f
-**[REQ-AUTH-6]:** All access to administrative interfaces, control functions, and sensitive operations shall be subject to strong authentication of users, services, or integrated components.
-**[REQ-AUTH-7]:** Priviledged interfaces shall be protected with [5.2.4 State-of-the-art cryptographic libraries].
These requirements are generally binding, and there is no low-medium-high tiering available.
<mark>TODO: define usage of machine credentials better, consider the cli over ssh controlled nms scenario</mark>
@@ -811,14 +799,7 @@ This section can include topic specific requirements.
### 5.3.1 Mitigations for user identity integrity
> This section shall have:
>
> - How the system users identities should be maintained
> - How the least amount of privileges principles are enforced to user groups
<mark>AMS: Killian and Mohammad are focusing on this. Skip for now.</mark>
-**[REQ-ID-0]** An network management system shall implement and document appropriate safeguards to ensure the validity of users identity according to the requirements of the forseeable use.
### 5.3.2 Mitigations for ingested data integrity and confidentiality
<mark>AMS: Srinath and Mohamad are focusing on this. Skip for now.</mark>
The update of a system has to be done often enough to keep the number of known vulnerabilities in minimum.
Therefore, it is important to test all system upgrades and design the upgrade procedure in a way, that keeps the system within the set [5.3.8 High Availability] targets.
Pre-Update Acquisition & Distribution:
- Tampered update packages during storage or transmission
- Update retrieved from an untrusted or unauthenticated source
- Use of revoked or compromised signing keys
Installation & Execution:
- Authenticity or integrity verification bypass
- Downgrade to a vulnerable version
- Rollback protections bypass
- Loss of availability if update fails or is interrupted
Requirements:
-**[REQ-UPDATES-0]:** The product shall verify the authenticity and integrity of update packages using a cryptographic digital signature verification prior to installation.
-**[REQ-UPDATES-1]:** The product shall maintain a monotonic version counter or equivalent mechanism to prevent installation of updates with an older vulnerable version.
-**[REQ-UPDATES-2]:** If the product supports intentional rollback, this action shall require explicit authorization and shall be based on separately versioned and signed rollback metadata.
-**[REQ-UPDATES-3]:** The product shall apply updates in an atomic manner such that incomplete or failed updates do not result in a partially updated state. In the event that an update cannot be completed successfully, the product shall automatically restore a previously operational software state, ensuring the product remains functional.
These requirements are generally binding, and there is no low-medium-high tiering available.
-**[REQ-UPDATES-0]** Authenticate the source of the update package with.
-**[REQ-UPDATES-1]** Verify integrity of the upddate before installation (hash checks).
-**[REQ-UPDATES-2]** Use secure channels for update delivery (e.g., TLS).
<mark>Consider makgin [REQ-UPDATES-3] only for high tier one.</mark>
