Details
Non-organizational users include all information system users other than organizational users, which includes organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors, guest researchers, individuals from allied nations).
Non-organizational users must be uniquely identified and authenticated for all accesses other than those accesses explicitly identified and documented by the organization when related to the use of anonymous access, such as accessing a web server.
Accordingly, a risk assessment is used in determining the authentication needs of the organization.
Scalability, practicality, and security are simultaneously considered in balancing the need to ensure ease of use for access to federal information and information systems with the need to protect and adequately mitigate risk to organizational operations, organizational assets, individuals, other organizations, and the Nation.
NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.
Solution
To drop a role, as the database administrator (shown here as ‘postgres’), run the following SQL:
$ sudo su – postgres
$ psql -c ‘DROP ROLE
To create a role, as the database administrator, run the following SQL:
$ sudo su – postgres
$ psql -c ‘CREATE ROLE
For the complete list of permissions allowed by roles, see the official documentation: https://www.postgresql.org/docs/current/static/sql-createrole.html
Supportive Information
The following resource is also helpful.
This security hardening control applies to the following category of controls within NIST 800-53: Identification and Authentication.This control applies to the following type of system Unix.
References
- 800-53|IA-8
- CAT|II
- CCI|CCI-000804
- Rule-ID|SV-214061r508027_rule
- STIG-ID|PGS9-00-001400
- STIG-Legacy|SV-87519
- STIG-Legacy|V-72867
- Vuln-ID|V-214061