controls::login via host tcp ip socket is configured correctly

Overview

A large number of authentication METHODs are available for hosts connecting using TCP/IP sockets, including:

  • trust
  • reject
  • md5
  • scram-sha-256
  • password
  • gss
  • sspi
  • ident
  • pam
  • ldap
  • radius
  • cert

METHODs trust, password, and ident are not to be used for remote logins. METHOD md5 is the most popular and can be used in both encrypted and unencrypted sessions,however, it is vulnerable to packet replay attacks. It is recommended that scram-sha-256 be used instead of md5. Use of the gss, sspi, pam, ldap, radius, and cert METHODs, while more secure than md5, are dependent upon the availability of external authenticating processes/services and thus are not covered in this benchmark.

Excelent Compliance Solution.

Puppet is an excellent solution to ensure your databases are CIS or STIG compliant. Now you’re looking at information about only one compliance control, but managing total compliance isn’t hard either!

If you you like he prospect of easy way into continuous compliancy with minimal fuss and bother, we suggest taking a look at our solution as your go-to option. Plus, our team can help you get up and running so that you can focus on other areas of your business. What are you waiting for? Get started today!

Benchmarks

This control is used in the following benchmarks:

Skipping

To deliberately skip this control (e.g. meaning don’t use Puppet to enforce this setting), we provide you with three ways:

1) Add pg_secured::controls::login_via_host_tcp_ip_socket_is_configured_correctly: skip to your hiera data. This will skip this control for ALL databases.
2) Add pg_secured::controls::login_via_host_tcp_ip_socket_is_configured_correctly::dbname: skip to your hiera data. This will skip this control for specified database only.
3) Add an entry with the content login_via_host_tcp_ip_socket_is_configured_correctly to the array value pg_secured::skip_list in your hiera data.

Attributes

Attribute Name Short Description
exclude  
preferred_value  
title The instance to apply the control to.

title

The instance to apply the control to.

All controls need an instance to apply the control to. Here is a simple example:

pg_secured::controls::control_name { 'instance':}

In this example, the string instance is the instance to apply the control to.

Back to overview of controls::login_via_host_tcp_ip_socket_is_configured_correctly

exclude

The objects to exclude from the control actions. Type: Array[String[1]]

Default:pg_secured::lookup_setting('exclude', [])

Back to overview of controls::login_via_host_tcp_ip_socket_is_configured_correctly

preferred_value

The authentication method to use for remote connections. Type: Enum['reject','md5','scram-sha-256','gss','sspi','pam','ldap','radius','cert']

Default:pg_secured::lookup_setting('preferred_value', 'scram-sha-256')

Back to overview of controls::login_via_host_tcp_ip_socket_is_configured_correctly