[Forgot Password]
Login  Register Subscribe












Paid content will be excluded from the download.

Download | Alert*
view XML


Platform: win10Date: (C)2016-09-23   (M)2017-10-18

Audit Policy: Logon-Logoff: Network Policy Server This subcategory reports events generated by RADIUS (IAS) and Network Access Protection (NAP) user access requests. These requests can be Grant, Deny, Discard, Quarantine, Lock, and Unlock. Auditing this setting will result in a medium or high volume of records on NPS and IAS servers. Events for this subcategory include: Note: All the events in the Network Policy Server subcategory are available only in Windows Vista Service Pack 1 and in Windows Server 2008. - 6272: Network Policy Server granted access to a user. - 6273: Network Policy Server denied access to a user. - 6274: Network Policy Server discarded the request for a user. - 6275: Network Policy Server discarded the accounting request for a user. - 6276: Network Policy Server quarantined a user. - 6277: Network Policy Server granted access to a user but put it on probation because the host did not meet the defined health policy. - 6278: Network Policy Server granted full access to a user because the host met the defined health policy. - 6279: Network Policy Server locked the user account due to repeated failed authentication attempts. - 6280: Network Policy Server unlocked the user account. - 8191: Network Policy Server unlocked the user account. 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.


Technical Mechanism: (1) GPO: Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Logon/Logoff\Audit Policy: Logon-Logoff: Network Policy Server (2) REG: ### (3) WMI: ###


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

OVAL    1
XCCDF    2

© 2013 SecPod Technologies