Skip to main content

Implementing Auditing


Auditing Overview

Auditing enables you to determine which activities are occurring on your system and allows you to track access to objects, files and folders; and modifications made to the objects, files and folders. Auditing also enables you to collect information associated with resource access and usage on your system by allowing you to audit system logon, file access, and object access. Security auditing events are written to the Security log of the system and can be accessed from the Event Viewer tool. Because event logs grow over time and typically consume valuable disk space, you have to regularly delete event log entries contained in the Security log.
The types of events which you should audit are listed below:
  • Computer logons and computer logoffs
  • Access to objects, and files and folders
  • System events.
  • Performance of user and computer account management activities.
To prevent auditing from consuming valuable system resources, you should only audit events which are necessary, and audit access to confidential data. This is mainly due to the following characteristics of auditing:implementing auditing Implementing Auditing
  • When auditing is enabled, auditing uses memory resources and processor resources.
  • The audit log utilizes hard disk space.
  • Sorting through huge amounts of logged audited entries can be a cumbersome and time-consuming task.
As mentioned previously, events that are audited are written to the Security log. You can use the Event Viewer tool to view information on these events.
An audit entry in Event Viewer contains the following information
  • Event Type: Error, Warning, or Information, and Success Audit or Failure Audit
  • Date and time when the event occurred.
  • Software or program which logged the event.
  • User which carried out the activity which caused the event being logged.
  • Computer on which the activity was done
  • Event ID
  • Event Description
Event Viewer allows you to perform the following actions on the Security log entries which it stores:
  • View events
  • Sort events by type and time.
  • Filter events
  • View and analyze advanced event log information.
  • Connect to the Event Viewer tool of a remote computer.
  • Export the file to a .TXT, .CSV, or .EVT file
The activities which you need to perform to implement auditing are listed here:
  • You need to determine and enable the event categories that you want to audit. The different event categories that you can audit are listed here:
    • Account logon events
    • Account management
    • Directory service access
    • Logon events
    • Object access
    • Policy change
    • Privilege use
    • Process tracking
    • System events
  • You need to define the objects that should be audited.
  • You need to specify the actions which should be logged in the audit log. You can audit:
    • Successes only
    • Failure only
    • Successes and Failures
  • You need to configure the size for the audit log.
  • You need to determine whether auditing will be implemented for the following:
    • Local computer
    • Domain controller
    • Active Directory domain
    • Organization unit (OU)

How to enable auditing for the local computer

  1. Click Start, Administrative Tools, and then click Local Security Policy.
  2. In the left pane, in Security Settings, expand Local Polices.
  3. Click Audit Policy.
  4. In the details pane, right-click the particular event category which you want to audit and then select Properties from the shortcut menu.
  5. The Properties dialog box of the event category opens.
  6. Select one or both of the following options: Success, Failure.
  7. Click OK.

How to enable auditing for a domain controller

  1. Click Start, Administrative Tools, and then click Active Directory Users And Computers.
  2. In the left console pane, right-click the Domain Controllers OU, and then select Properties from the shortcut menu.
  3. Click the Group Policy tab.
  4. You can add a new policy, or choose an existing policy. Click Edit.
  5. In the Group Policy Object Editor console, in the left console tree, expand Computer Configuration, Windows Settings, Security Settings, Local Policies and then expand Audit Policy.
  6. In the details pane, right-click the particular event category which you want to audit; and then select Properties from the shortcut menu.
  7. When the Properties dialog box of the event category opens, select one or both of the following options: Success, Failure
  8. Click OK.

How to enable auditing for an Active Directory domain or organizational unit

  1. Click Start, Administrative Tools, and then click Active Directory Users And Computers.
  2. Right-click the domain or OU for which you want to configure auditing and then select Properties from the shortcut menu.
  3. Click the Group Policy tab, add a new policy, and click Edit
  4. In the Group Policy Object Editor expand Computer Configuration, Windows Settings, Security Settings, Local Policies and then expand Audit Policy
  5. Right-click the particular event category which you want to audit; and then select Properties from the shortcut menu.
  6. Select one or both of the following options: Success, Failure
  7. Click OK.

How to enable auditing for objects stored in Active Directory

Before you can implement auditing for Active Directory objects, you have to first enable the Audit Directory Service Access option
  1. Click Start, Administrative Tools, and then click Active Directory Users And Computers.
  2. Click the View menu item and verify that Advanced features are enabled.
  3. Select the Active Directory object which you want to configure auditing for.
  4. Click the Action menu and then select Properties.
  5. Click the Security tab when the Properties dialog box of the object opens.
  6. Click Advanced
  7. The Advanced Security Settings dialog box for the Active Directory object opens.
  8. Click the Auditing tab.
  9. Click Add
  10. Specify the users or groups for which you want to audit object access.
  11. Click OK.
  12. When the Auditing Entry For dialog box opens, select the event(s) that you want to audit by choosing either one of, or both of the following options: Successful, Failed; alongside the particular event(s).
  13. Use the Apply Onto list box to specify where the auditing should occur.
  14. Click OK.

How to enable auditing for files and folders

  1. Open Windows Explorer.
  2. Right-click the file or folder which you want to configure auditing for, and then select Properties from the shortcut menu.
  3. Click the Security tab.
  4. Click the Advanced button.
  5. Click the Auditing tab on the Advanced Security Settings dialog box.
  6. Click Add.
  7. Specify the users or groups for which you want to audit file or folder access. Click OK.
  8. Select the events that you want to audit by checking either the Successful option, Failed option, or both of these options alongside the particular event(s).
  9. Click OK.

How to enable auditing for printers

  1. Click Start, and then select Printers And Faxes.
  2. When the Printers And Faxes system folder opens, right-click the printer which you want to configure auditing for, and then select Properties from the shortcut menu.
  3. Click the Security tab
  4. Click the Advanced button
  5. Click the Auditing tab on the Advanced Security Settings dialog box of the printer.
  6. Click Add.
  7. Specify the users or groups for which you want to audit printer access. Click OK.
  8. Select the events that you want to audit by checking either the Successful option, Failed option, or both of these options alongside the particular event(s).
  9. Use the Apply Onto list box to specify the location where auditing should occur.
  10. Click OK.

How to view Security log information in Event Viewer

  1. Open Event Viewer.
  2. In the left pane, click Security.
  3. The details pane is populated with all events that exist in the Security log.
  4. You can double-click on an event entry to view its properties.

How to configure the size of the Security log

  1. Open Event Viewer.
  2. In the left pane, right-click Security and then select Properties on the shortcut menu.
  3. The Security Properties dialog box opens.
  4. On the General tab, enter the maximum log file size in the Maximum Log Size field. You can specify a value from 64 KB to 4,194,240 KB for the maximum log file size.
  5. In the When Maximum Log File Size Is Reached area, there are a number of options which you can choose.
  6. Select the Overwrite Events As Needed option if you want the oldest events in the Security log replaced by newer events which are logged.
  7. Select the Overwrite Events Older Than _ Days option if you want to specify the time duration after which events should be removed.
  8. Select the Do Not Overwrite Events (Clear Log Manually) option if you want to manually clear events.
  9. Click OK.

How to find specific audited events in the Security log

  1. Open Event Viewer.
  2. In the left pane, click Security.
  3. Click the View menu, and then click the Find option.
  4. The Find In dialog box for the Security log opens.
  5. In the Event Types area of the Find In dialog box, specify the types of the event which you want to find.
  6. In the Event Source list, select the source that logged the event(s) which you want to find.
  7. In the Category list, select the event category.
  8. In the Event ID box, provide the event identity number.
  9. In the User box, provide the user name.
  10. In the Computer box, provide the computer name.
  11. In the Description box, provide an event description.
  12. In the Search Direction section of the Find In dialog box, set how the security log should be searched. The search can be performed from bottom to top or from top to bottom.
  13. Click the Find Next button
  14. The security log is searched, based on the search criteria that were defined.
  15. All events that are matched are highlighted.
  16. You can click Find Next to continue searching the security log for events which match your search criteria.
  17. Click the Close button to stop the search.

How to manually remove entries from the Security log

  1. Open Event Viewer.
  2. In the left pane, right-click Security and then select the Clear All Events command on the shortcut menu.
  3. The Event Viewer message box opens.
  4. Click Yes if you want to archive the existing entries in the Security log before it is deleted. You have to specify a name and a file format.
  5. Click No to delete the existing entries in the log.

Popular posts from this blog

HOW TO EDIT THE BCD REGISTRY FILE

The BCD registry file controls which operating system installation starts and how long the boot manager waits before starting Windows. Basically, it’s like the Boot.ini file in earlier versions of Windows. If you need to edit it, the easiest way is to use the Startup And Recovery tool from within Vista. Just follow these steps: 1. Click Start. Right-click Computer, and then click Properties. 2. Click Advanced System Settings. 3. On the Advanced tab, under Startup and Recovery, click Settings. 4. Click the Default Operating System list, and edit other startup settings. Then, click OK. Same as Windows XP, right? But you’re probably not here because you couldn’t find that dialog box. You’re probably here because Windows Vista won’t start. In that case, you shouldn’t even worry about editing the BCD. Just run Startup Repair, and let the tool do what it’s supposed to. If you’re an advanced user, like an IT guy, you might want to edit the BCD file yourself. You can do this

DNS Scavenging.

                        DNS Scavenging is a great answer to a problem that has been nagging everyone since RFC 2136 came out way back in 1997.  Despite many clever methods of ensuring that clients and DHCP servers that perform dynamic updates clean up after themselves sometimes DNS can get messy.  Remember that old test server that you built two years ago that caught fire before it could be used?  Probably not.  DNS still remembers it though.  There are two big issues with DNS scavenging that seem to come up a lot: "I'm hitting this 'scavenge now' button like a snare drum and nothing is happening.  Why?" or "I woke up this morning, my DNS zones are nearly empty and Active Directory is sitting in a corner rocking back and forth crying.  What happened?" This post should help us figure out when the first issue will happen and completely avoid the second.  We'll go through how scavenging is setup then I'll give you my best practices.  Scavenging s

AD LDS – Syncronizing AD LDS with Active Directory

First, we will install the AD LDS Instance: 1. Create and AD LDS instance by clicking Start -> Administrative Tools -> Active Directory Lightweight Directory Services Setup Wizard. The Setup Wizard appears. 2. Click Next . The Setup Options dialog box appears. For the sake of this guide, a unique instance will be the primary focus. I will have a separate post regarding AD LDS replication at some point in the near future. 3. Select A unique instance . 4. Click Next and the Instance Name dialog box appears. The instance name will help you identify and differentiate it from other instances that you may have installed on the same end point. The instance name will be listed in the data directory for the instance as well as in the Add or Remove Programs snap-in. 5. Enter a unique instance name, for example IDG. 6. Click Next to display the Ports configuration dialog box. 7. Leave ports at their default values unless you have conflicts with the default values. 8. Click N