Applies to
Describes the best practices, location, values, policy management, and security considerations for the Generate security audits security policy setting.
Reference
Jun 12, 2017 Except that we use a lot of SQL server. As a result, we need to be able to 'Generate Security Audits'. Which can be done via GPO for a domain user. Except this is NOT a domain user, it's a local user. So, we can go into the Local Security Policy and set it, that's fine. But is there a way to use group policy to add something like. So, in this article we will discuss how to grant elevated privileges over Active Directory and a server. There are differences and the differences are quite varied. In the end, you will know the different methods that are possible to grant elevated privileges in a Windows environment. What are Elevated Privileges?
This policy setting determines which accounts can be used by a process to generate audit records in the security event log. The Local Security Authority Subsystem Service (LSASS) writes events to the log. You can use the information in the security event log to trace unauthorized device access.
Constant: SeAuditPrivilege
Possible values
Best practices
Location
Computer ConfigurationWindows SettingsSecurity SettingsLocal PoliciesUser Rights Assignment
Default values
By default, this setting is Local Service and Network Service on domain controllers and stand-alone servers.
The following table lists the actual and effective default policy values for the most recent supported versions of Windows. Default values are also listed on the policy’s property page.
Policy management
This section describes features, tools, and guidance to help you manage this policy.
A restart of the computer is not required for this policy setting to be effective.
Any change to the user rights assignment for an account becomes effective the next time the owner of the account logs on.
Misuse of this user right can result in the generation of many auditing events, potentially hiding evidence of an attack or causing a denial-of-service (DoS) if the Audit: Shut down system immediately if unable to log security audits security policy setting is enabled.
Group Policy
Settings are applied in the following order through a Group Policy Object (GPO), which will overwrite settings on the local computer at the next Group Policy update:
Enable Registry Audit
When a local setting is greyed out, it indicates that a GPO currently controls that setting.
Security considerations
This section describes how an attacker might exploit a feature or its configuration, how to implement the countermeasure, and the possible negative consequences of countermeasure implementation.
Vulnerability
A malicious user could use accounts that can write to the Security log to fill that log with meaningless events. If the computer is configured to overwrite events as needed, malicious users could use this method to remove evidence of their unauthorized activities. If the computer is configured to shut down when it is unable to write to the Security log, and it is not configured to automatically back up the log files, this method could be used to create a DoS condition.
CountermeasurePenetration Testing
Ensure that only the Local Service and Network Service accounts have the Generate security audits user right assigned to them.
Generate Security Audits Registry Key WestPotential impactGenerate Security Audits Registry Key West
None. Restricting the Generate security audits user right to the Local Service and Network Service accounts is the default configuration.
Generate Security Audits Registry Key FreeRelated topicsComments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |