| Finding ID |
Severity |
Title |
Description |
|
V-256963
|
High |
The Automation Controller NGINX web server must employ cryptographic mechanisms (TLS/DTLS/SSL) to prevent the unauthorized disclosure of information during transmission. |
Preventing the disclosure of transmitted information requires that the Automation Controller web server take measures to employ some form of cryptographic mechanism in order to protect the information during transmission. This is usually achieved through the use of Transport Layer Security (TLS).
Transmission of data can take place between the... |
|
V-256944
|
High |
All Automation Controller NGINX front-end web server files must be verified for their integrity (e.g., checksums and hashes) before becoming part of the production web server. |
Being able to verify that a patch, upgrade, certificate, etc., being added to the web server is unchanged from the producer of the file is essential for file validation and nonrepudiation of the information.
The Automation Controller NGINX web server host must have a mechanism to verify that files are... |
|
V-256967
|
Medium |
All accounts installed with the Automation Controller NGINX web server's software and tools must have passwords assigned and default passwords changed. |
During installation of the Automation Controller NGINX web server software, accounts are created for the web server to operate properly. The accounts installed can have either no password installed or a default password, which will be known and documented by the vendor and the user community.
The first thing an... |
|
V-256966
|
Medium |
Automation Controller NGINX web servers must install security-relevant software updates within the configured time period directed by an authoritative source (e.g., IAVM, CTOs, DTMs, and STIGs). |
Security flaws with software applications are discovered daily. Red Hat constantly updates and patches Automation Controller to address newly discovered security vulnerabilities. Organizations (including any contractor to the organization) are required to promptly install security-relevant software updates (e.g., patches, service packs, and hot fixes). Flaws discovered during security assessments, continuous... |
|
V-256965
|
Medium |
The Automation Controller NGINX web servers must maintain the confidentiality and integrity of information during preparation for transmission. |
Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, including, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information.
An example of this would be an SMTP queue. This queue... |
|
V-256964
|
Medium |
Automation Controller NGINX web servers must maintain the confidentiality of controlled information during transmission through the use of an approved TLS version. |
Transport Layer Security (TLS) is a required transmission protocol for a web server hosting controlled information. The use of TLS provides confidentiality of data in transit between the web server and client. FIPS 140-2 approved TLS versions must be enabled and non-FIPS-approved SSL versions must be disabled.
NIST SP 800-52... |
|
V-256962
|
Medium |
The Automation Controller NGINX web server must be protected from being stopped by a nonprivileged user. |
An attacker has at least two reasons to stop an Automation Controller NGINX web server. The first is to cause a DoS, and the second is to put in place changes the attacker made to an Automation Controller NGINX web server configuration.
To prohibit an attacker from stopping the Automation... |
|
V-256961
|
Medium |
The Automation Controller NGINX web server application, libraries, and configuration files must only be accessible to privileged users. |
Automation Controller NGINX web servers can be modified through parameter modification, patch installation, upgrades to the web server or modules, and security parameter changes. With each of these changes, there is the potential for an adverse effect such as a DoS, web server instability, or hosted application instability.
To limit... |
|
V-256960
|
Medium |
Nonprivileged accounts on the hosting system must only access Automation Controller NGINX web server security-relevant information and functions through a distinct administrative account. |
It is important that Automation Controller NGINX web server security features are separated from nonprivileged users. Special “privileged” roles need to be developed so that only they can have access to those features and administer the web server, when necessary. These privileged roles will be better trained in the security... |
|
V-256959
|
Medium |
Debugging and trace information, within Automation Controller NGINX web server, used to diagnose the web server must be disabled. |
It is important that Automation Controller NGINX web server debugging and trace information used to diagnose the web server is disabled, because debugging information can yield information about the Automation Controller NGINX webserver, like web server type, version, patches installed, plugins, modules, the hosted app’s code type. Back ends used... |
|
V-256958
|
Medium |
The Automation Controller NGINX web server must display a default hosted application web page, not a directory listing, when a requested web page cannot be found. |
It is important that Automation Controller NGINX web server display a default hosted application web paged and not a directory listing when a requested web page cannot be found, because the web server will be vulnerable to intrusion. For this reason, access to directory listings must be disabled.
If a... |
|
V-256957
|
Medium |
The Automation Controller NGINX web server must limit the character set used for data entry. |
It is important that Automation Controller NGINX web server limit the character set used for data entry and disallow Unicode use in hosted applications to avoid application compromise. Definition of the available character set for data entry can trap efforts to bypass security checks. The presence of nonstandard characters may... |
|
V-256956
|
Medium |
The Automation Controller NGINX web server document directory must be in a separate partition from the web server's system files. |
It is important that Automation Controller NGINX web server restricts the ability of clients to launch denial-of-service (DoS) attacks against other information systems or networks by disallowing access to system files via document and system file partitioning. DoS attacks are an attempt to negatively affect the availability of the server... |
|
V-256955
|
Medium |
Cookies exchanged between any Automation Controller NGINX web server and any client, such as session cookies, must have security settings that disallow cookie access outside the originating Automation Controller NGINX web server and hosted application. |
It is important that cookies exchanged between any Automation Controller NGINX webserver and any client have security settings that do not allow cookie access outside the originating Automation Controller server and the hosted application. This is because exchanged cookies may have session information such as user credentials that enable the... |
|
V-256954
|
Medium |
All Automation Controller NGINX web server accounts accessing the directory tree, the shell, or other operating system functions and utilities must only be administrative accounts. |
AIT is important to limit access to Automation Controller nginx web servers and provide access on a need-to-know basis. For example, only System Administrators must have access to all the system's capabilities, while the web administrator and associated staff require access and control of the web content and Automation Controller... |
|
V-256953
|
Medium |
Only authenticated system administrators or the designated PKI Sponsor for an Automation Controller NGINX web server must have access to any Automation Controller NGINX web server's private key. |
Each Automation Controller NGINX web server's private key is used to prove the identity of the server to clients and securely exchange the shared secret key used to encrypt communications between the Automation Controller NGINX web server and clients.
By gaining access to the private key, an attacker can pretend... |
|
V-256952
|
Medium |
All Automation Controller NGINX web servers must be configured to use a specified IP address and port. |
From a security perspective, it is important that all Automation Controller NGINX web servers are configured to use a specified IP address and port because “listening” on all IP addresses poses a vulnerability to the web server.
Not confining the web server to a specified IP address and port puts... |
|
V-256950
|
Medium |
All Automation Controller NGINX web servers must have Web Distributed Authoring (WebDAV) disabled. |
Automation Controller NGINX web servers can be installed with functionality that, just by its nature, is not secure. Web Distributed Authoring (WebDAV) is an extension to the HTTP protocol that, when developed, was meant to allow users to create, change, and move documents on a server, typically a web server... |
|
V-256949
|
Medium |
All Automation Controller NGINX web servers must have Multipurpose Internet Mail Extensions (MIME) that invoke OS shell programs disabled. |
Controlling what a user of a hosted application can access is part of the security posture of the Automation Controller NGINX web server.
Any time a user can access more functionality than is needed for the operation of the hosted application, it poses a security issue. A user with too... |
|
V-256948
|
Medium |
All Automation Controller NGINX webserver accounts not utilized by installed features (i.e., tools, utilities, specific services, etc.) must not be created and must be deleted when the web server feature is uninstalled. |
If web server accounts are not being used, they must be deleted when the web server is uninstalled. This is because the accounts become stale over time and are not tended to. Best practice also dictates that if accounts are not going to be used, they must not be created... |
|
V-256947
|
Medium |
All Automation Controller NGINX web servers must not be a proxy server for any process other than the Automation Controller application. |
The Automation Controller NGINX web server must be primarily a web server or a proxy server but not both, for the same reasons that other multi-use servers are not recommended. Scanning for web servers that will also proxy requests into an otherwise protected network is a very common anonymous attack.... |
|
V-256946
|
Medium |
All Automation Controller NGINX front-end web servers must not perform user management for hosted applications. |
Web servers require enterprise-wide user management capability in order to prevent unauthorized access, with features like attempt lockouts and password complexity requirements.
Unauthorized access to the web server makes the web server and the organization vulnerable to attack.
Note: The underlying NGINX web server does not perform user management or... |
|
V-256945
|
Medium |
Expansion modules must be fully reviewed, tested, and signed before they can exist on a production Automation Controller NGINX front-end web server. |
In the case of a production web server, areas for content development and testing will not exist, as this type of content is only permissible on a development website.
The process of developing on a functional production website entails a degree of trial and error and repeated testing. This process... |
|
V-256943
|
Medium |
The Automation Controller must generate the appropriate log records. |
Automation Controller's web server must log all details related to user sessions in support of troubleshooting, debugging, and forensic analysis.
Without a data logging feature, the organization loses an important auditing and analysis tool for event investigations.
Satisfies: SRG-APP-000016-WSR-000005, SRG-APP-000095-WSR-000056, SRG-APP-000096-WSR-000057, SRG-APP-000097-WSR-000058, SRG-APP-000098-WSR-000059, SRG-APP-000098-WSR-000060, SRG-APP-000099-WSR-000061, SRG-APP-000100-WSR-000064 |
|
V-256942
|
Medium |
The Automation Controller NGINX web server must use cryptography on all remote connections. |
Nondisplayed data on a web page may expose information that could put the organization at risk and negatively affect data integrity.
Automation Controller's web server must be configured such that all connections, regardless of their origin, between the server and the user are encrypted using cryptography. |
|
V-256941
|
Medium |
The Automation Controller servers must use encrypted communication for all channels given the high impact of those services to an organization's infrastructure. |
The Automation Controller communicates information about configuration of other information systems through its web interface and API, storing records about this information in a database. Although large portions are sanitized of sensitive information, due to the nature of this kind of information, it must always be maximally protected. Leaked details... |
|
V-256940
|
Medium |
The Automation Controller web server must manage sessions. |
Session management on client and server is required to protect identity and authorization information.
Sessions for the Automation Controller web server, if compromised, could lead to execution of jobs on remote endpoints as if authenticated.
Satisfies: SRG-APP-000001-WSR-000002, SRG-APP-000001-WSR-000001, SRG-APP-000295-WSR-000012, SRG-APP-000295-WSR-000134 |
|
V-256951
|
Low |
All Automation Controller NGINX web servers must protect system resources and privileged operations from hosted applications. |
Automation Controller NGINX web servers may host too many applications. Each application will need certain system resources and privileged operations to operate correctly. The Automation Controller NGINX web servers must be configured to contain and control the applications and protect the system resources and privileged operations from those not needed... |