SQL Server

SQL Server Security

Most SQL Server security work starts with a list. Who can connect, who is a sysadmin, and whether that list still matches the people who work here.

Access first, then controls around it

A hardening pass that ignores logins does not change the risk. We review authentication, server and database permissions, and auditing that you can actually read later. Encryption of data at rest and of backups is part of the same conversation when the data requires it.

Regulatory scope, including the controls a compliance review asks about, is described on database security and compliance. Encryption choices are on SQL Server encryption.

A security review covers

  • Sysadmin and other privileged logins
  • How applications connect, and the rights that login has
  • Auditing you can use after an incident
  • Whether the surface is larger than the application needs
  • Encryption and backup protection where the data requires them

Start with who can connect

The SQL Server version and whether this review is for an audit or for your own peace of mind. We will scope it before changing permissions.