[Forgot Password]
Login  Register Subscribe

30479

 
 

423868

 
 

248149

 
 

909

 
 

194803

 
 

282

Paid content will be excluded from the download.


Download | Alert*
CCE
view XML

CCE-42930-8

Platform: cpe:/o:microsoft:windows_10Date: (C)2016-09-23   (M)2023-07-04



Ensure No Auditing for 'Audit Policy: Account Management: Application Group Management' This subcategory reports each event of application group management on a computer, such as when an application group is created, changed, or deleted or when a member is added to or removed from an application group. If you enable this Audit policy setting, administrators can track events to detect malicious, accidental, and authorized creation of application group accounts. Events for this subcategory include: - 4783: A basic application group was created. - 4784: A basic application group was changed. - 4785: A member was added to a basic application group. - 4786: A member was removed from a basic application group. - 4787: A non-member was added to a basic application group. - 4788: A non-member was removed from a basic application group. - 4789: A basic application group was deleted. - 4790: An LDAP query group was created. - 4791: A basic application group was changed. - 4792: An LDAP query group was deleted. Refer to the Microsoft Knowledgebase article 'Description of security events in Windows Vista and in Windows Server 2008' for the most recent information about this setting: http://support.microsoft.com/kb/947226. Counter Measure: Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files. Potential Impact: If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.


Parameter:

[audit_none/audit_success/audit_failure/audit_success_failure]


Technical Mechanism:

(1) GPO: Computer ConfigurationWindows SettingsSecurity SettingsAdvanced Audit Policy ConfigurationAudit PoliciesAccount ManagementAudit Policy: Account Management: Application Group Management

CCSS Severity:CCSS Metrics:
CCSS Score : 4.2Attack Vector: LOCAL
Exploit Score: 0.8Attack Complexity: LOW
Impact Score: 3.4Privileges Required: HIGH
Severity: MEDIUMUser Interaction: NONE
Vector: AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:LScope: UNCHANGED
 Confidentiality: LOW
 Integrity: LOW
 Availability: LOW
  

References:
Resource IdReference
SCAP Repo OVAL Definitionoval:org.secpod.oval:def:35498


OVAL    1
oval:org.secpod.oval:def:35498
XCCDF    1
xccdf_org.secpod_benchmark_general_Windows_10

© SecPod Technologies