controls::no login exists with the name sa

Overview

The sa login (e.g. principal) is a widely known and often widely used SQL Server account. Therefore, there should not be a login called sa even when the original sa login (principal_id = 1) has been renamed.

Enforcing this control reduces the probability of an attacker executing brute force attacks against a well-known principal name.

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 mssql_secured::controls::no_login_exists_with_the_name_sa: skip to your hiera data. This will skip this control for ALL databases.
2) Add mssql_secured::controls::no_login_exists_with_the_name_sa::dbname: skip to your hiera data. This will skip this control for specified database only.
3) Add an entry with the content no_login_exists_with_the_name_sa to the array value mssql_secured::skip_list in your hiera data.

Attributes

Attribute Name Short Description
title The database to apply the control to.

title

The database to apply the control to.

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

mssql_secured::controls::control_name {'MSSQLSERVER':}

In this example, the string DB is the database to apply the control to.

Back to overview of controls::no_login_exists_with_the_name_sa