phone icon nav Call Us 888-690-3282    Follow Us
phone icon nav Call Us 888-690-3282    Follow Us
Contact Us

Security and Auditing for SQL Server Database Administrators (DBAs)

Introduction

Security and auditing are paramount for protecting sensitive data and ensuring compliance with regulations. As a Microsoft SQL Server DBA, understanding authentication methods, encryption, and access control is crucial. In this whitepaper, we will explore SQL Server security features, auditing capabilities, and best practices.

Understanding SQL Server Security

Authentication Methods

  • Windows Authentication: Integrated with Active Directory.
  • SQL Server Authentication: Username and password.

Encryption and Data Protection

Transparent Data Encryption (TDE)

  • Protects data at rest.
  • Encrypts entire database files.

Always Encrypted

  • Encrypts sensitive data in transit and at rest.
  • Separates encryption keys from the database.

Access Control and Authorization

Logins and Users

  • Logins: Authenticate to SQL Server.
  • Users: Associated with a database.

Roles and Permissions

  • Fixed Server Roles: Predefined roles (e.g., sysadmin, dbcreator).
  • Database Roles: Custom roles within a database (e.g., db_datareader, db_datawriter).
  • Object Permissions: Control access to tables, views, stored procedures.

Auditing Features

Standard Auditing

  • Captures specific events (e.g., logins, privilege changes).
  • Use SQL Server Audit.

Fine-Grained Auditing

  • Define audit specifications based on specific conditions (e.g., time of day, IP address).
  • Use Extended Events or triggers.

Compliance and Security Best Practices

Regulatory Compliance

  • Understand industry-specific regulations (e.g., GDPR, HIPAA).
  • Implement necessary controls.

Security Best Practices

  • Least Privilege: Grant minimum necessary permissions.
  • Regular Auditing: Monitor access and changes.
  • Patch Management: Keep SQL Server up to date.

Monitoring and Troubleshooting

SQL Server Audit

  • Create audit specifications.
  • Review audit logs.

Troubleshooting Security Issues

  • Investigate failed logins and unauthorized access.
  • Use SQL Server error logs and event logs.

Conclusion

SQL Server security is a shared responsibility. As a DBA, collaborate with system administrators, developers, and compliance officers to implement robust security measures. Remember that protecting data is essential for maintaining trust with users and stakeholders.

Additional Reading >

Background

A large automotive plant operator has been using a custom application framework to build an application integral to their operations. Originally built using JDK8 and JBoss4 against an Oracle database, the application received periodic updates, with the last major update in 2020/2021. In 2024, the client and Performance One Data Solutions, a division of Ross Group Inc., embarked on a joint effort to upgrade the technology stack to enhance performance, security, and maintainability.

Objectives

The primary goals of the project were:

  1. Upgrade the Custom Application Framework from JDK8 to JDK21.
  2. Upgrade the jQuery integration to release 3.7.1.
  3. Upgrade the application to run on Wildfly 30 from Wildfly 11.
  4. Migrate the database backend from Oracle 12 to Microsoft SQL Server 2020.

Challenges and Solutions

Framework and Database Migration:

  • Challenge: The application framework was vetted against Microsoft SQL Server but was not deployed in a major application.
  • Solution: Performance One refactored the framework to conform to Java 9+ standards and regression-tested it against Microsoft SQL Server 2020.

Application Refactoring:

  • Challenge: Refactoring the client application to compile and run using the new tech stack.
  • Solution: Performance One took a copy of the client application and refactored it to compile and launch using JDK21, Wildfly 30, and Microsoft SQL Server.

Data Migration:

  • Challenge: Migrating data from Oracle to Microsoft SQL Server.
  • Solution: Performance One provided migrated data and created installation scripts to upgrade the client’s Microsoft SQL Server.

Report Conversion:

  • Challenge: Converting BIRT and Crystal reports against Microsoft SQL Server.
  • Solution: Performance One converted the reports and ensured they worked with Microsoft SQL Server.

Project Timeline

Initial Milestones:

    1. Complete Framework upgrade to JDK21/Wildfly 30.
    2. Provide migrated data from Oracle to Microsoft SQL Server.
    3. Regression test the application framework against Microsoft SQL Server 2020.
    4. Refactor the client’s application to compile and launch using the new tech stack.
    5. Create installation data script for Microsoft SQL Server compliance.
    6. Regression test the application installation processes.
    7. Make recommendations for unused application features.
    8. Validate and upgrade application code.

Additional Tasks

  • Database Procedures Conversion: Performance One converted the client’s database procedures, functions, and views to Microsoft SQL Server.
  • Report Migrations: Ongoing conversion of BIRT and Crystal report development.
  • Application Enhancements: Upgrading client’s application screens for jQuery 3.7.1, file attachment uploads, and integration with scanner devices using web sockets.
  • Server Maintenance: Wildfly server maintenance, release builds, and deployment handling, with a transition plan for client resources post-go-live.

Conclusion

Performance One Data Solutions partnered with the client to upgrade the technology stack, ensuring improved performance and maintainability. The collaboration between Performance One and the client team demonstrated effective problem-solving and adaptability, setting a strong foundation for future upgrades and enhancements.

Contact-Us

Let's Talk

Use our expertise to propel your business to the next level.