The Edge SWG must be configured with only one local account to be used as the account of last resort in the event the authentication server is unavailable.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-279256	SYME-ND-000590	SV-279256r1170694_rule	CCI-001358	medium
Description
Authentication for administrative (privileged level) access to the device is required at all times. An account can be created on the device's local database for use when the authentication server is down or connectivity between the device and the authentication server is not operable. This account is referred to as the account of last resort since it is intended to be used as a last resort and when immediate administrative access is absolutely necessary. The account of last resort logon credentials must be stored in a sealed envelope and kept in a safe. The safe must be periodically audited to verify the envelope remains sealed. The signature of the auditor and the date of the audit should be added to the envelope as a record. Administrators should secure the credentials and disable the root account (if possible) when not needed for system administration functions.
STIG			Date
Symantec Edge SWG NDM Security Technical Implementation Guide			2026-02-25

Related Frameworks

1 mapping across 4 frameworks

SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

IAC-08Role-Based Access Control (RBAC)

1.00

DISA STIG Benchmark (XCCDF)V1R2intersects(normalised)
DISA CCI List2025-01-23equal to(normalised)
SCF Secure Traceability Relationship Mapping (STRM)2026.2equal to

NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (3) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-2Account Management

1.00

DISA STIG Benchmark (XCCDF)V1R2intersects(normalised)
DISA STIG Benchmark (XCCDF)V5R3our copyintersects(normalised)
DISA STIG Benchmark (XCCDF)V5R3intersects(normalised)
DISA CCI List2025-01-23equal to(normalised)

AC-2(3)Disable Accounts

1.00

DISA STIG Benchmark (XCCDF)V1R2intersects(normalised)
DISA STIG Benchmark (XCCDF)V2R3our copyintersects(normalised)
DISA STIG Benchmark (XCCDF)V2R3intersects(normalised)
DISA CCI List2025-01-23equal to(normalised)

AC-2(7)Privileged User Accounts

1.00

DISA STIG Benchmark (XCCDF)V1R2intersects(normalised)
DISA CCI List2025-01-23equal to(normalised)

CCI1 mapping

CCI-001358

1.00

DISA STIG Benchmark (XCCDF)V1R2intersects(normalised)

NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 4 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

PR.AA-05

1.00

DISA STIG Benchmark (XCCDF)V1R2intersects(normalised)
DISA CCI List2025-01-23equal to(normalised)
SCF Secure Traceability Relationship Mapping (STRM)2026.2equal to
NIST OLIR Informative ReferenceOLIR 153 (2025-04-07)intersects(normalised)SCF Focal Document mapping (catalog)SCF 2026.2 focalintersects(normalised)

Details

Check Text (C-279256r1170694_chk)

1. Log in to the Edge SWG SSH CLI. 2. Enter "enable" and "configure terminal". 3. Issue the command "show security local-user-list". If any user exists in either the "local_user_database" or "local" list, this is a finding. Note: The admin user is not included in either list as it is the emergency account of last resort.

Fix Text (F-83711r1170531_fix)

1. Log in to the Edge SWG SSH CLI. 2. Enter "enable" and "configure terminal". 3. Issue the command "security local-user-list edit local". 4. To delete any local user, type "user delete <username> force". 5. Enter "view" to show any other users that may remain.