Summary of Audit-Specific STIG ID's

Published Mar 23 2019 11:44 AM 1,628 Views
Microsoft
First published on TECHNET on Dec 04, 2010

The DoD Database Security Technical Implementation Guide (STIG) has quite a few requirements in the area of auditing, but they're scattered throughout the document. Here's a list of all the audit-related STIG ID's that I found.


From the Security Readiness Review: "The majority of Microsoft SQL Server security auditing is provided by the trace facility. Traces may be created using system stored procedures or with Microsoft SQL Profiler. The trace must be running in order for security event data to be collected for analysis."


DG = Database, General
DM = Database, Microsoft


Audit IDs


DG0029: Database Auditing
Changes made to the DBMS configuration or its objects and data must be recorded.
This ID requires that C2 Security be turned on for standard and enterprise editions. (Common Criteria replaces C2 Security and is available as of SQL Server 2005 SP2.)

DG0030: DBMS Audit Data Maintenance
Retain the audit trail information at least 1 year with at least the last 30 days online.

DG0031: DBMS Audit of Changes to Data
Only applicable if required by an application.

DG0032: DBMS Audit Record Access
File-level Access Control Lists (ACLs) must be managed on audit logs to prevent unauthorized access.

DG0041: DBMS installation account use logging
The account used to install SQL Server should have no special SQL Server privileges after installation.

DG0052: DBMS Software Access Audit
Periodically review the audit logs for unexpected application names.

DG0054: DBMS Software Access Audit Review
Audit log review procedures must be documented in the written Security Plan.
Manual reviews must be weekly and documented unless automated alerts are used.

DG0060: DBMS Shared Account Authorization
Applications must pass individual user information where feasible for audit accountability.

DG0067: DBMS Account Password External Storage
Application passwords should not be stored in the clear.
The DBA must maintain a record of authorized applications.
Audit reviews (see DG0052) should find new applications to be evaluated for password storage compliance.

DG0074: DBMS Inactive Accounts
Audit expired accounts and accounts unused for 30 days.

DG0080: DBMS Application User Privilege Assignment Review
Assignment of privileges must be reviewed and reported to auditors at least monthly.

DG0083: DBMS Audit Report Automation
An efficient audit review method is required: The Database STIG V8R1 section 3.3.17 that DG0083 is based on is more ambiguous, and merely requires that the audit data be presented in an "efficient way." This is easy to comply with and can be performed without 3rd party tools, and we can filter and summarize events such as failed login attempts. To summarize, I believe it is only possible to comply with the STIG on this requirement, not the Checklist.

DG0085: Minimum DBA Privilege Assignment
Audit privilege upgrades by DBAs if their data access is restricted.

DG0095: DBMS Audit Trail Data Review
Documented daily review is required for audit traces, system error logs, system logs (Windows), and application logs (Windows). This is the responsibility of the IAO, not the DBA.

DG0099: DBMS Access To External Local Executables
Enable auditing on execution of stored procedures; Review the audit data after a sufficient period to capture all operational usage, and then restrict access to unused extended stored procedures. If no operational issues arise after a sufficient time (you should double the period used before), remove the unused extended stored procedures.

DG0111: DBMS Dedicated Software Directory and Partition
Audit log files must be in a dedicated directory.

DG0114: Critical DBMS Files Fault Protection
Audit log files must be on fault-tolerant storage devices.

DG0116: DBMS Privileged Role Assignments
Only personnel authorized to manage the system audit configuration may be SQL Server System Administrators.

DG0140: DBMS Security Data Access
Enable auditing for access to any security data where supported by the DBMS. If auditing for security data access results in an unacceptable adverse impact on application operation, scale back the audit to a reasonable and acceptable level. Document any incomplete audit with acceptance of the risk of incomplete audit in the System Security Plan.

DG0141: DBMS Access Control Bypass
Enable auditing of failed or both failed and successful logins.

DG0142: DBMS Privileged Action Audit
The default trace must be enabled or all of its events must be included in a custom trace.

DG0145: DBMS Audit Record Content
This ID requires:
1. C2 Security be turned on for standard and enterprise editions. (Common Criteria replaces C2 Security and is available as of SQL Server 2005 SP2.)
OR
2. A custom audit trace with a specific list of events must always be running.

DG0158: DBMS Remote Administration Audit
Audit all actions by DBAs, regardless of remote vs. local, because SQL Server does not distinguish remote vs. local administrative sessions, and most SQL Server administration is remote.

DG0159: Review of DBMS Remote Adminstrative Access
If DG0158 is implemented, the IAO will review the remote adminstrative activity daily.

DG0161: DBMS Audit Tool
SQL Server Alerts can create and log alerts and SQL Server Database Mail can be used to send email alerts to DBAs and IAOs to satisfy the immediate-reporting requirement.

DG0166: Protection of DBMS Asymmetric Encryption Keys
Examine evidence that an audit record is created whenever the asymmetric key is accessed by other than authorized users.

DG0172: DBMS Classification Level Audit
Changes to data security labels will be audited if the data owner requires it. See SQL Server Row-level or Cell-level Security .

DG0175: DBMS Host And Component STIG Compliancy
Regularly audit the security configuration of related applications and the application servers to confirm their continued compliance with security requirements.

DG0176: DBMS Audit Log Backups
Configure and ensure SQL Server audit trace files, instance, and other error log files are included in regular backups.

DG0198: DBMS Remote Administration Encryption
Verify during audit reviews that:
1. Administrative access is limited to local connections.
OR
2. Administrative access is limited to a dedicated and encrypted port.

--------------------------------------------------

DM0510: C2 Audit Mode
This ID requires that C2 Security be turned on for standard and enterprise editions. (Common Criteria replaces C2 Security and is available as of SQL Server 2005 SP2.)

DM1761: Scan For Startup Stored Procedures
C2/Common Criteria requires a default audit trace to run at SQL Server startup.

DM5267: Trace Rollover On Audit Trace
Audit traces must use TRACE_FILE_ROLLOVER option 2 and SHUTDOWN_ON_ERROR option 4.


%3CLINGO-SUB%20id%3D%22lingo-sub-383703%22%20slang%3D%22en-US%22%3ESummary%20of%20Audit-Specific%20STIG%20ID's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-383703%22%20slang%3D%22en-US%22%3E%0A%20%26lt%3Bmeta%20http-equiv%3D%22Content-Type%22%20content%3D%22text%2Fhtml%3B%20charset%3DUTF-8%22%20%2F%26gt%3B%3CSTRONG%3E%20First%20published%20on%20TECHNET%20on%20Dec%2004%2C%202010%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%3CP%3EThe%20DoD%20Database%20Security%20Technical%20Implementation%20Guide%20(STIG)%20has%20quite%20a%20few%20requirements%20in%20the%20area%20of%20auditing%2C%20but%20they're%20scattered%20throughout%20the%20document.%20Here's%20a%20list%20of%20all%20the%20audit-related%20STIG%20ID's%20that%20I%20found.%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3CEM%3E%20From%20the%20Security%20Readiness%20Review%3A%20%22The%20majority%20of%20Microsoft%20SQL%20Server%20security%20auditing%20is%20provided%20by%20the%20trace%20facility.%20Traces%20may%20be%20created%20using%20system%20stored%20procedures%20or%20with%20Microsoft%20SQL%20Profiler.%20The%20trace%20must%20be%20running%20in%20order%20for%20security%20event%20data%20to%20be%20collected%20for%20analysis.%22%20%3C%2FEM%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3EDG%20%3D%20Database%2C%20General%20%3CBR%20%2F%3E%20DM%20%3D%20Database%2C%20Microsoft%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3CSTRONG%3E%20Audit%20IDs%20%3C%2FSTRONG%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3CSTRONG%3EDG0029%3A%20Database%20Auditing%20%3CBR%20%2F%3E%20%3C%2FSTRONG%3E%20Changes%20made%20to%20the%20DBMS%20configuration%20or%20its%20objects%20and%20data%20must%20be%20recorded.%20%3CBR%20%2F%3E%20This%20ID%20requires%20that%20C2%20Security%20be%20turned%20on%20for%20standard%20and%20enterprise%20editions.%20(Common%20Criteria%20replaces%20C2%20Security%20and%20is%20available%20as%20of%20SQL%20Server%202005%20SP2.)%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3E%20DG0030%3A%20DBMS%20Audit%20Data%20Maintenance%20%3CBR%20%2F%3E%20%3C%2FSTRONG%3E%20Retain%20the%20audit%20trail%20information%20at%20least%201%20year%20with%20at%20least%20the%20last%2030%20days%20online.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3EDG0031%3A%20DBMS%20Audit%20of%20Changes%20to%20Data%20%3CBR%20%2F%3E%20%3C%2FSTRONG%3E%20Only%20applicable%20if%20required%20by%20an%20application.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3EDG0032%3A%20DBMS%20Audit%20Record%20Access%20%3CBR%20%2F%3E%20%3C%2FSTRONG%3E%20File-level%20Access%20Control%20Lists%20(ACLs)%20must%20be%20managed%20on%20audit%20logs%20to%20prevent%20unauthorized%20access.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3EDG0041%3A%20DBMS%20installation%20account%20use%20logging%20%3CBR%20%2F%3E%20%3C%2FSTRONG%3E%20The%20account%20used%20to%20install%20SQL%20Server%20should%20have%20no%20special%20SQL%20Server%20privileges%20after%20installation.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3EDG0052%3A%20DBMS%20Software%20Access%20Audit%20%3CBR%20%2F%3E%20%3C%2FSTRONG%3E%20Periodically%20review%20the%20audit%20logs%20for%20unexpected%20application%20names.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3EDG0054%3A%20DBMS%20Software%20Access%20Audit%20Review%20%3CBR%20%2F%3E%20%3C%2FSTRONG%3E%20Audit%20log%20review%20procedures%20must%20be%20documented%20in%20the%20written%20Security%20Plan.%20%3CBR%20%2F%3E%20Manual%20reviews%20must%20be%20weekly%20and%20documented%20unless%20automated%20alerts%20are%20used.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3EDG0060%3A%20DBMS%20Shared%20Account%20Authorization%20%3CBR%20%2F%3E%20%3C%2FSTRONG%3E%20Applications%20must%20pass%20individual%20user%20information%20where%20feasible%20for%20audit%20accountability.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3EDG0067%3A%20DBMS%20Account%20Password%20External%20Storage%20%3CBR%20%2F%3E%20%3C%2FSTRONG%3E%20Application%20passwords%20should%20not%20be%20stored%20in%20the%20clear.%20%3CBR%20%2F%3E%20The%20DBA%20must%20maintain%20a%20record%20of%20authorized%20applications.%20%3CBR%20%2F%3E%20Audit%20reviews%20(see%20DG0052)%20should%20find%20new%20applications%20to%20be%20evaluated%20for%20password%20storage%20compliance.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3EDG0074%3A%20DBMS%20Inactive%20Accounts%20%3CBR%20%2F%3E%20%3C%2FSTRONG%3E%20Audit%20expired%20accounts%20and%20accounts%20unused%20for%2030%20days.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3EDG0080%3A%20DBMS%20Application%20User%20Privilege%20Assignment%20Review%20%3CBR%20%2F%3E%20%3C%2FSTRONG%3E%20Assignment%20of%20privileges%20must%20be%20reviewed%20and%20reported%20to%20auditors%20at%20least%20monthly.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3EDG0083%3A%20DBMS%20Audit%20Report%20Automation%20%3CBR%20%2F%3E%20%3C%2FSTRONG%3E%20An%20efficient%20audit%20review%20method%20is%20required%3A%20The%20Database%20STIG%20V8R1%20section%203.3.17%20that%20DG0083%20is%20based%20on%20is%20more%20ambiguous%2C%20and%20merely%20requires%20that%20the%20audit%20data%20be%20presented%20in%20an%20%22efficient%20way.%22%20This%20is%20easy%20to%20comply%20with%20and%20can%20be%20performed%20without%203rd%20party%20tools%2C%20and%20we%20can%20filter%20and%20summarize%20events%20such%20as%20failed%20login%20attempts.%20To%20summarize%2C%20I%20believe%20it%20is%20only%20possible%20to%20comply%20with%20the%20STIG%20on%20this%20requirement%2C%20not%20the%20Checklist.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3EDG0085%3A%20Minimum%20DBA%20Privilege%20Assignment%20%3CBR%20%2F%3E%20%3C%2FSTRONG%3E%20Audit%20privilege%20upgrades%20by%20DBAs%20if%20their%20data%20access%20is%20restricted.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3EDG0095%3A%20DBMS%20Audit%20Trail%20Data%20Review%20%3CBR%20%2F%3E%20%3C%2FSTRONG%3E%20Documented%20daily%20review%20is%20required%20for%20audit%20traces%2C%20system%20error%20logs%2C%20system%20logs%20(Windows)%2C%20and%20application%20logs%20(Windows).%20This%20is%20the%20responsibility%20of%20the%20IAO%2C%20not%20the%20DBA.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3EDG0099%3A%20DBMS%20Access%20To%20External%20Local%20Executables%20%3CBR%20%2F%3E%20%3C%2FSTRONG%3E%20Enable%20auditing%20on%20execution%20of%20stored%20procedures%3B%20Review%20the%20audit%20data%20after%20a%20sufficient%20period%20to%20capture%20all%20operational%20usage%2C%20and%20then%20restrict%20access%20to%20unused%20extended%20stored%20procedures.%20If%20no%20operational%20issues%20arise%20after%20a%20sufficient%20time%20(you%20should%20double%20the%20period%20used%20before)%2C%20remove%20the%20unused%20extended%20stored%20procedures.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3EDG0111%3A%20DBMS%20Dedicated%20Software%20Directory%20and%20Partition%20%3CBR%20%2F%3E%20%3C%2FSTRONG%3E%20Audit%20log%20files%20must%20be%20in%20a%20dedicated%20directory.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3EDG0114%3A%20Critical%20DBMS%20Files%20Fault%20Protection%20%3CBR%20%2F%3E%20%3C%2FSTRONG%3E%20Audit%20log%20files%20must%20be%20on%20fault-tolerant%20storage%20devices.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3EDG0116%3A%20DBMS%20Privileged%20Role%20Assignments%20%3CBR%20%2F%3E%20%3C%2FSTRONG%3E%20Only%20personnel%20authorized%20to%20manage%20the%20system%20audit%20configuration%20may%20be%20SQL%20Server%20System%20Administrators.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3EDG0140%3A%20DBMS%20Security%20Data%20Access%20%3CBR%20%2F%3E%20%3C%2FSTRONG%3E%20Enable%20auditing%20for%20access%20to%20any%20security%20data%20where%20supported%20by%20the%20DBMS.%20If%20auditing%20for%20security%20data%20access%20results%20in%20an%20unacceptable%20adverse%20impact%20on%20application%20operation%2C%20scale%20back%20the%20audit%20to%20a%20reasonable%20and%20acceptable%20level.%20Document%20any%20incomplete%20audit%20with%20acceptance%20of%20the%20risk%20of%20incomplete%20audit%20in%20the%20System%20Security%20Plan.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3EDG0141%3A%20DBMS%20Access%20Control%20Bypass%20%3CBR%20%2F%3E%20%3C%2FSTRONG%3E%20Enable%20auditing%20of%20failed%20or%20both%20failed%20and%20successful%20logins.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3EDG0142%3A%20DBMS%20Privileged%20Action%20Audit%20%3CBR%20%2F%3E%20%3C%2FSTRONG%3E%20The%20default%20trace%20must%20be%20enabled%20or%20all%20of%20its%20events%20must%20be%20included%20in%20a%20custom%20trace.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3EDG0145%3A%20DBMS%20Audit%20Record%20Content%20%3CBR%20%2F%3E%20%3C%2FSTRONG%3E%20This%20ID%20requires%3A%20%3CBR%20%2F%3E%201.%20C2%20Security%20be%20turned%20on%20for%20standard%20and%20enterprise%20editions.%20(Common%20Criteria%20replaces%20C2%20Security%20and%20is%20available%20as%20of%20SQL%20Server%202005%20SP2.)%20%3CBR%20%2F%3E%20OR%20%3CBR%20%2F%3E%202.%20A%20custom%20audit%20trace%20with%20a%20specific%20list%20of%20events%20must%20always%20be%20running.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3EDG0158%3A%20DBMS%20Remote%20Administration%20Audit%20%3CBR%20%2F%3E%20%3C%2FSTRONG%3E%20Audit%20all%20actions%20by%20DBAs%2C%20regardless%20of%20remote%20vs.%20local%2C%20because%20SQL%20Server%20does%20not%20distinguish%20remote%20vs.%20local%20administrative%20sessions%2C%20and%20most%20SQL%20Server%20administration%20is%20remote.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3EDG0159%3A%20Review%20of%20DBMS%20Remote%20Adminstrative%20Access%20%3CBR%20%2F%3E%20%3C%2FSTRONG%3E%20If%20DG0158%20is%20implemented%2C%20the%20IAO%20will%20review%20the%20remote%20adminstrative%20activity%20daily.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3EDG0161%3A%20DBMS%20Audit%20Tool%20%3CBR%20%2F%3E%20%3C%2FSTRONG%3E%20SQL%20Server%20Alerts%20can%20create%20and%20log%20alerts%20and%20SQL%20Server%20Database%20Mail%20can%20be%20used%20to%20send%20email%20alerts%20to%20DBAs%20and%20IAOs%20to%20satisfy%20the%20immediate-reporting%20requirement.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3EDG0166%3A%20Protection%20of%20DBMS%20Asymmetric%20Encryption%20Keys%20%3CBR%20%2F%3E%20%3C%2FSTRONG%3E%20Examine%20evidence%20that%20an%20audit%20record%20is%20created%20whenever%20the%20asymmetric%20key%20is%20accessed%20by%20other%20than%20authorized%20users.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3EDG0172%3A%20DBMS%20Classification%20Level%20Audit%20%3CBR%20%2F%3E%20%3C%2FSTRONG%3E%20Changes%20to%20data%20security%20labels%20will%20be%20audited%20if%20the%20data%20owner%20requires%20it.%20See%20%3CA%20href%3D%22http%3A%2F%2Fwww.microsoft.com%2Ftechnet%2Fprodtechnol%2Fsql%2F2005%2Fmultisec.mspx%22%20title%3D%22SQL%20Server%20Row-level%20or%20Cell-level%20Security%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%20SQL%20Server%20Row-level%20or%20Cell-level%20Security%20%3C%2FA%3E%20.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3EDG0175%3A%20DBMS%20Host%20And%20Component%20STIG%20Compliancy%20%3CBR%20%2F%3E%20%3C%2FSTRONG%3E%20Regularly%20audit%20the%20security%20configuration%20of%20related%20applications%20and%20the%20application%20servers%20to%20confirm%20their%20continued%20compliance%20with%20security%20requirements.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3EDG0176%3A%20DBMS%20Audit%20Log%20Backups%20%3CBR%20%2F%3E%20%3C%2FSTRONG%3E%20Configure%20and%20ensure%20SQL%20Server%20audit%20trace%20files%2C%20instance%2C%20and%20other%20error%20log%20files%20are%20included%20in%20regular%20backups.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3EDG0198%3A%20DBMS%20Remote%20Administration%20Encryption%20%3CBR%20%2F%3E%20%3C%2FSTRONG%3E%20Verify%20during%20audit%20reviews%20that%3A%20%3CBR%20%2F%3E%201.%20Administrative%20access%20is%20limited%20to%20local%20connections.%20%3CBR%20%2F%3E%20OR%20%3CBR%20%2F%3E%202.%20Administrative%20access%20is%20limited%20to%20a%20dedicated%20and%20encrypted%20port.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20--------------------------------------------------%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3E%20DM0510%3A%20C2%20Audit%20Mode%20%3CBR%20%2F%3E%20%3C%2FSTRONG%3E%20This%20ID%20requires%20that%20C2%20Security%20be%20turned%20on%20for%20standard%20and%20enterprise%20editions.%20(Common%20Criteria%20replaces%20C2%20Security%20and%20is%20available%20as%20of%20SQL%20Server%202005%20SP2.)%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3E%20DM1761%3A%20Scan%20For%20Startup%20Stored%20Procedures%20%3CBR%20%2F%3E%20%3C%2FSTRONG%3E%20C2%2FCommon%20Criteria%20requires%20a%20default%20audit%20trace%20to%20run%20at%20SQL%20Server%20startup.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3EDM5267%3A%20Trace%20Rollover%20On%20Audit%20Trace%20%3CBR%20%2F%3E%20%3C%2FSTRONG%3E%20Audit%20traces%20must%20use%20TRACE_FILE_ROLLOVER%20option%202%20and%20SHUTDOWN_ON_ERROR%20option%204.%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3C%2FP%3E%0A%20%0A%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-383703%22%20slang%3D%22en-US%22%3EFirst%20published%20on%20TECHNET%20on%20Dec%2004%2C%202010%20The%20DoD%20Database%20Security%20Technical%20Implementation%20Guide%20(STIG)%20has%20quite%20a%20few%20requirements%20in%20the%20area%20of%20auditing%2C%20but%20they're%20scattered%20throughout%20the%20document.%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-383703%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESQLServerSecurity%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Version history
Last update:
‎Mar 23 2019 11:44 AM
Updated by: