STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 4 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Symantec Edge SWG ALG Security Technical Implementation Guide

V-279176

CAT II (Medium)

The Edge SWG must limit the number of concurrent sessions to an organization-defined number for all accounts and/or account types.

Rule ID

SV-279176r1170660_rule

STIG

Symantec Edge SWG ALG Security Technical Implementation Guide

Version

V1R1

CCIs

CCI-000054CCI-001094CCI-002385CCI-004866

Discussion

Network element management includes the ability to control the number of users and user sessions that utilize a network element. Limiting the number of current sessions per user is helpful in limiting risks related to denial-of-service (DoS) attacks. This requirement addresses concurrent sessions for information system accounts and does not address concurrent sessions by single users via multiple system accounts. The maximum number of concurrent sessions must be the same as the requirements specified for the application for which it serves as intermediary. This policy only applies to application gateways/firewalls (e.g., identity management or authentication gateways) that provide user account services as part of the intermediary services.

Check Content

1. In the Edge SWG Web UI, navigate to the Visual Policy Manager (VPM).
2. Navigate to the Proxy Auth CPL Layer.

Under a <Proxy> section, if there is no text that contains a user.login.count, this is a finding.

Fix Text

1. In the Edge SWG Web UI, navigate to the VPM.
2. Navigate to the Proxy Auth CPL Layer.
3. Under a new <Proxy> section, add the following line. Ensure it is indented:
    FORCE_DENY user.login.count=4.. user.login.log_out(yes)

Note: Login count is organizationally defined, so "4" can be changed to what the site requires.