Audit Policy and Security Guidelines for Rouge Company

WEEK 8: SYSTEM ADMINISTRATION
(Student’s Name)
(Professor’s name)
(Course)
(Date)

Introduction
This week paper addresses audit policy which monitors event log details. In addition, this
paper proposes security guidelines for Rouge Company.
Part one: Audit Policy
For windows server, 2012 audit login is usually enabled by default for failure ad success.
Windows system audit enables one to track both attempted and actual access and the changes to
the objects. It also enables one to verify policies which one has put in place so as to secure the
organization network infrastructure. With auditing, one is able to track modifications to the
sensitive user accounts via the access of sensitive folders and files. For windows server, 2012
advanced audit policy is done via group policy objects as shown by figure one screenshot below.
The audit group policy settings contain various settings such as account Logon, DS Access,
Logon/Logoff, policy change, global Object Access Auditing, account management, and detailed
tracking (Matthews, 2014).
By implementing an audit policy, the windows system will be in a position to determine
the type of information about the organization system. With audit logon events policy it will
enable the system administrator to track all attempts made to the domain user account. At the
workstation level, this policy is able to record any attempt which uses a local account which is
stored in computer security account manager. With the audit process tracking policy, an
organization is able to track each and every program which executed by either the user or the
system. The system administrator is also able to determine the duration in which a program as
open. With audit directory service access policy, one is able to provide a low-level audit trail of
changes to the objects in Active Directory (Ferrill, 2015).