hat
Lè konfigirasyon sekirite pou sistèm SQL sèvè Microsoft ou, ou ta dwe asire ke ou satisfè nenpòt nan kondisyon konfòmite òganizasyon ou a pou pwoteksyon done. Òganizasyon souvan bezwen konfòme yo ak règleman endistri espesifik konfòmite, ki manda odit nan tout aksè done. Pou adrese egzijans sa a, SQL sèvè bay yon seri de opsyon pou mete ann aplikasyon odit. Yon lòt kondisyon konfòmite komen se chifreman nan done pwoteje kont aksè san otorizasyon nan evènman an ki gen aksè nan dosye yo baz done konpwomèt. SQL sèvè sipòte egzijans sa a pa bay transparan done chifreman (TDE). Pou diminye risk pou enfomasyon enfòmasyon pa itilizatè ki gen aksè administratif nan yon baz done, kolòn ki genyen done sansib - tankou nimewo kat kredi oswa nimewo idantite nasyonal - ka chiffres lè l sèvi avèk karakteristik ki toujou chiffre. Modil sa a dekri opsyon ki disponib pou odit nan SQL sèvè, ki jan yo itilize ak jere karakteristik nan SQL Odit karakteristik, ak kouman yo aplike chifreman.Lessons
eng
When configuring security for your Microsoft SQL Server systems, you should ensure that you meet any of your organization’s compliance requirements for data protection. Organizations often need to adhere to industry-specific compliance policies, which mandate auditing of all data access. To address this requirement, SQL Server provides a range of options for implementing auditing. Another common compliance requirement is the encryption of data to protect against unauthorized access in the event that access to the database files is compromised. SQL Server supports this requirement by providing transparent data encryption (TDE). To reduce the risk of information leakage by users with administrative access to a database, columns containing sensitive data—such as credit card numbers or national identity numbers—can be encrypted using the Always Encrypted feature. This module describes the available options for auditing in SQL Server, how to use and manage the SQL Server Audit feature, and how to implement encryption.Lessons