<?xml version="1.0"?>
<standard status="released">
<standardinfo>
<title>NT4 Generic Security Standard</title>
<titleabbrev>LCZ-NT4-GSS</titleabbrev>
<edition>1.1</edition>
<pubdate>16 May 2009</pubdate>
<abstract>
<para>This document specifies generic technical security policy for implementations of <trademark>Microsoft</trademark> <trademark>Windows</trademark> NT4.0, and applies to workstation, server and domain controller implementations of NT4.0, whether standalone 
or part of a domain.
</para>
</abstract>
<revhistory>
<revision>
<revnumber>1.1</revnumber>
<date>16 May 2009</date>
<authorinitials>FOD</authorinitials>
<revremark>Revised for re-release</revremark>
</revision>
<revision>
<revnumber>1.0</revnumber>
<date>04 February 2003</date>
<authorinitials>LCZ</authorinitials>
<revremark>Initial Draft for public release</revremark>
</revision>
</revhistory>
<copyright>
<year>2001</year><year>2002</year><year>2003</year><year>2009</year>
<holder>Frank O'Dwyer</holder>
</copyright>
</standardinfo>
<intro>
<objectives>
<objective>To specify a baseline configuration for implementations of &lt;trademark&gt;Microsoft&lt;/trademark&gt; &lt;trademark&gt;Windows&lt;/trademark&gt; NT4.0. 
</objective>
<objective>To provide guidance to administators, developers and security personnel in securely implementing &lt;trademark&gt;Microsoft&lt;/trademark&gt; &lt;trademark&gt;Windows&lt;/trademark&gt; NT4.0. 
</objective>
</objectives>
<scope>
<para>Controls specified in this document apply to workstation, server, and domain controller implementations of NT4.0, whether used standalone or part of a domain.
</para>
<para>All of the organisation's NT4.0 information systems
will be subject to the policies specified within
this generic security standard. The policies will
be applied to new and existing installations.
</para>
</scope>
<out-of-scope>
<para>Compliance with this standard will not provide <quote>in depth</quote> security architecture or intelligent security design guidance
to projects. As a consequence, for high impact or safety-critical business applications, additional guidance will still need to be 
sought from the Information Security team consultancy function.  
</para>
<para>This is a generic standard. Controls specific to workstation, server, or domain controller implementations are not 
defined here but will be the subject of additional standards.
</para>
<para>Compliance with this standard does not negate the need for an overall security review 
of a proposed application. Contact the Information Security team if you are in doubt.
</para>
</out-of-scope>
<commonintrostuff/>
<relateddocs/>
<definitions>
<definition>
<para>An <quote>Information Asset</quote> equates to any computerised information system 
or component thereof and thus includes an application, an item of off the shelf software, hardware, media, 
a data item, a data item repository and associated communications networks.</para>
<para>The specification of 
the Information Asset in question will usually be given so that this document is unambiguous, except
where a control relates to any <quote>Information Asset</quote>. </para>
</definition>
<definition>
<para>The use of <quote>must</quote> or <quote>will</quote> indicates what the author considers to be a mandatory control.</para>
<para>However, whether the controls listed here are mandatory for your organisation is entirely at your organisation's discretion and
thus they should be interpreted as representing the strongest recommendation of the author.</para>
</definition>
<definition>
<para>The use of <quote>should</quote> or <quote>recommended</quote> or <quote>ought</quote> indicates
that the author believes that the controls in question are worthwhile and should be implemented unless such
an implementation is impossible, onerous or impractical. Again, the implementation of controls so recommended
in this document is entirely at your organisation's discretion.</para>
</definition>
</definitions>
</intro>
<controlchapter><title>Desktop Security Requirements</title>
<controlsection><title>Logical Access Controls</title>
</controlsection>
<controlsection><title>Security Management and Administration</title>
</controlsection>
<controlsection><title>Security Incident Reporting</title>
</controlsection>
<controlsection><title>Physical Access Controls</title>
</controlsection>
<controlsection><title>Protection from malicious software</title>
</controlsection>
</controlchapter>
<controlchapter><title>Portable and off site computing requirements</title>
<controlsection><title>Physical access controls</title>
</controlsection>
<controlsection><title>Security management and administration</title>
</controlsection>
<controlsection><title>General security points</title>
</controlsection>
<controlsection><title>Logical access controls</title>
</controlsection>
<controlsection><title>Protection from malicious software</title>
</controlsection>
</controlchapter>
<controlchapter><title>Network Security Requirements</title>
<controlsection><title>Data Back-up controls</title>
</controlsection>
<controlsection><title>Dialup Connection Security</title>
</controlsection>
<controlsection><title>Dialup Security Management Issues</title>
</controlsection>
<controlsection><title>Third Party Access - Customers</title>
</controlsection>
<controlsection><title>Access controls</title>
</controlsection>
<controlsection><title>Management Controls</title>
</controlsection>
<controlsection><title>Physical security controls</title>
</controlsection>
<controlsection><title>Network Devices</title>
</controlsection>
</controlchapter>
<controlchapter><title>Personnel Security</title>
<controlsection><title>Security in job descriptions</title>
</controlsection>
<controlsection><title>Reporting of security matters</title>
</controlsection>
<controlsection><title>Recruitment</title>
</controlsection>
<controlsection><title>Education and Awareness</title>
</controlsection>
</controlchapter>
<controlchapter><title>User Configuration</title>
<controlsection><title>User Administration</title>
<control level="baseline" techversion="4.0" title="Restrict access to login scripts and profiles" environment="Any" pleading="mandatory" id="NT4GEN-UC-1" versionMaj="1" disclosure-level="Any" availability-level="Any" versionMin="0" technology="NT" section="User Configuration:User Administration" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Login scripts and profiles must be accessible only by their user and administrators.</policy-statement>
<checklist-question>Is access to login scripts and profiles restricted only to their user and administrators?
</checklist-question>
<howto>
<step>Ensure the ACLs for login scripts and profiles grant access only to their user and administrators.</step>
</howto>
<risks-addressed>
<risk>Users will be able to run programs using the privileges of other users.</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
</controlsection>
<controlsection><title>Default Accounts</title>
<control level="baseline" techversion="4.0" title="Rename the administrator account" environment="Any" pleading="recommended" id="NT4GEN-DA-2" versionMaj="1" disclosure-level="Any" availability-level="Any" versionMin="0" technology="NT" section="User Configuration:Default Accounts" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Rename the administrator to an attributable account name and assign a new password.</policy-statement>
<checklist-question>Has the administrator account been renamed to an attributable account name and the password changed?</checklist-question>
<howto>
<step>Rename the administrator account to an individuals name</step>
<step>Assign a new password</step>
</howto>
<risks-addressed>
<risk>As the admin account is certain to exist on every system it is a priority for attack</risk>
<risk>Changing the password from the default helps prevent unauthorised access</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="4.0" title="Disable Guest Account" environment="Any" pleading="mandatory" id="NT4GEN-DA-1" versionMaj="1" disclosure-level="Any" availability-level="Any" versionMin="0" technology="NT" section="User Configuration:Default Accounts" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>The guest account must be disabled.</policy-statement>
<checklist-question>Has the guest account been disabled?
</checklist-question>
<howto>
<step>Select account disabled on the main account window.</step>
<step>Give the guest account a long random password that is not retained by anyone.</step>
<step>Set its login hours to none.</step>
<step>Set its expiration date to a date past.</step>
</howto>
<risks-addressed>
<risk>Unauthorised network access to the NT system may be possible.</risk>
<risk>Unauthorised access to NT objects may result</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
</controlsection>
<controlsection><title>Roles, Views, and Access Control</title>
</controlsection>
<controlsection><title>Privileges</title>
<control level="baseline" techversion="4.0" title="The advanced user right to load and unload device drivers must not be assigned to any users" environment="Any" pleading="mandatory" id="NT4GEN-PRIV-13" versionMaj="1" disclosure-level="Any" availability-level="Any" versionMin="0" technology="NT" section="User Configuration:Privileges" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>The advanced user right to load and unload device drivers must not be assigned to any users</policy-statement>
<checklist-question>Is the advanced user right to load and unload device drivers assigned to any users?</checklist-question>
<howto>
<step>Identify all users who hold this right and revoke it.</step>
<step>Identify all applications who hold this right and determine why they need it and revoke it for all those where this requirement is clearly spurious</step>
</howto>
<risks-addressed>
<risk>Replacing a device driver may be used to gain unauthorised access</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="4.0" title="The advanced user right to create a page file must not be assigned to any users" environment="Any" pleading="mandatory" id="NT4GEN-PRIV-7" versionMaj="1" disclosure-level="Any" availability-level="Any" versionMin="0" technology="NT" section="User Configuration:Privileges" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>The advanced user right to create a page file must not be assigned to any users</policy-statement>
<checklist-question>Is the advanced user right to create a page file assigned to any users?</checklist-question>
<howto>
<step>Identify all users who hold this right and revoke it.</step>
<step>Identify all applications who hold this right and determine why they need it and revoke it for all those where this requirement is clearly spurious</step>
</howto>
<risks-addressed>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="4.0" title="The advanced user right to bypass traverse checking must not be assigned to any users" environment="Any" pleading="mandatory" id="NT4GEN-PRIV-6" versionMaj="1" disclosure-level="Any" availability-level="Any" versionMin="0" technology="NT" section="User Configuration:Privileges" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>The advanced user right to bypass traverse checking must not be assigned to any users</policy-statement>
<checklist-question>Is the advanced user right to bypass traverse checking assigned to any users?</checklist-question>
<howto>
<step>Identify all users who hold this right and revoke it.</step>
<step>Identify all applications who hold this right and determine why they need it and revoke it for all those where this requirement is clearly spurious</step>
</howto>
<risks-addressed>
<risk>This right permits access control on an object path to be disregarded and may result in unintended access being obtained</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="4.0" title="The advanced user right to profile single process must be assigned only to administrators." environment="Any" pleading="mandatory" id="NT4GEN-PRIV-16" versionMaj="1" disclosure-level="Any" availability-level="Any" versionMin="0" technology="NT" section="User Configuration:Privileges" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>The advanced user right to profile single process must be assigned only to administrators</policy-statement>
<checklist-question>Is the advanced user right to profile single process assigned only to administrators?</checklist-question>
<howto>
<step>Identify all users who hold this right and revoke it.</step>
<step>Identify all applications who hold this right and determine why they need it and revoke it for all those where this requirement is clearly spurious</step>
</howto>
<risks-addressed>
<risk>The ability to profile single processes may result in unauthorised disclosure of security sensitive information</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="4.0" title="The advanced user right to repace a system level process token must be assigned to no user" environment="Any" pleading="mandatory" id="NT4GEN-PRIV-19" versionMaj="1" disclosure-level="Any" availability-level="Any" versionMin="0" technology="NT" section="User Configuration:Privileges" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>The advanced user right to repace a system level process token must be assigned to no user</policy-statement>
<checklist-question>Is the advanced user right to repace a system level process token assigned to any user?</checklist-question>
<howto>
<step>Identify all users who hold this right and revoke it.</step>
<step>Identify all applications who hold this right and determine why they need it and revoke it for all those where this requirement is clearly spurious</step>
</howto>
<risks-addressed>
<risk>Such access may be used to subvert the security controls on the system</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="4.0" title="The advanced user right to create permanent shared objects must not be assigned to any users" environment="Any" pleading="mandatory" id="NT4GEN-PRIV-9" versionMaj="1" disclosure-level="Any" availability-level="Any" versionMin="0" technology="NT" section="User Configuration:Privileges" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>The advanced user right to create permanent shared objects must not be assigned to any users</policy-statement>
<checklist-question>Is the advanced user right to create permanent shared objects assigned to any users?</checklist-question>
<howto>
<step>Identify all users who hold this right and revoke it.</step>
<step>Identify all applications who hold this right and determine why they need it and revoke it for all those where this requirement is clearly spurious</step>
</howto>
<risks-addressed>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="4.0" title="The advanced user right to generate security audits must not be assigned to any users other than administrators or security teams" environment="Any" pleading="mandatory" id="NT4GEN-PRIV-11" versionMaj="1" disclosure-level="Any" availability-level="Any" versionMin="0" technology="NT" section="User Configuration:Privileges" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>The advanced user right to generate security audits must not be assigned to any users other than administrators or security teams</policy-statement>
<checklist-question>Is the advanced user right to generate security audits assigned to any users other than the administrators or security users?</checklist-question>
<howto>
<step>Identify all users who hold this right and revoke it where appropriate</step>
<step>Identify all applications who hold this right and determine why they need it and revoke it for all those where this requirement is clearly spurious</step>
</howto>
<risks-addressed>
<risk>The security audit will contain disclosure sensitive information</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="4.0" title="The advanced user right to debug programs must be assigned only to adminisrators and developers" environment="Any" pleading="mandatory" id="NT4GEN-PRIV-10" versionMaj="1" disclosure-level="Any" availability-level="Any" versionMin="0" technology="NT" section="User Configuration:Privileges" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>The advanced user right to debug programs must be assigned only to adminisrators and developers</policy-statement>
<checklist-question>Is the advanced user right to debug programs assigned only to adminisrators and developers?</checklist-question>
<howto>
<step>Identify all users who hold this right and revoke it.</step>
<step>Identify all applications who hold this right and determine why they need it and revoke it for all those where this requirement is clearly spurious</step>
</howto>
<risks-addressed>
<risk>Security sensitive information may be obtained such as passwords</risk>
<risk>Unauthorised access may be obtained</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="4.0" title="The user right to shutdown the system should be assigned to local groups and not to individual users" environment="Any" pleading="recommended" id="NT4GEN-PRIV-4" versionMaj="1" disclosure-level="Any" availability-level="Any" versionMin="0" technology="NT" section="User Configuration:Privileges" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>The user right to shutdown the system should be assigned to local groups and not to individual users</policy-statement>
<checklist-question>Is the user right to shutdown the system assigned to local groups and not to individual users</checklist-question>
<howto>
<step>Assign the right to a local group</step>
<step>Assign users to the group</step>
</howto>
<risks-addressed>
<risk>Adnministration should be performed using roles supported through membership of groups</risk>
<risk>Complex individual admin often leads to unauthorised access</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="4.0" title="The advanced user right to profile system performance must be assigned only to administrators." environment="Any" pleading="mandatory" id="NT4GEN-PRIV-17" versionMaj="1" disclosure-level="Any" availability-level="Any" versionMin="0" technology="NT" section="User Configuration:Privileges" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>The advanced user right to profile system performance must be assigned only to administrators.</policy-statement>
<checklist-question>Is the advanced user right to profile system performance assigned only to administrators?</checklist-question>
<howto>
<step>Identify all users who hold this right and revoke it.</step>
<step>Identify all applications who hold this right and determine why they need it and revoke it for all those where this requirement is clearly spurious</step>
</howto>
<risks-addressed>
<risk>The ability to profile system performance may result in a denial of service</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="4.0" title="The advanced user right to receive unsolicited device input must be assigned to no users." environment="Any" pleading="mandatory" id="NT4GEN-PRIV-18" versionMaj="1" disclosure-level="Any" availability-level="Any" versionMin="0" technology="NT" section="User Configuration:Privileges" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>The advanced user right to receive unsolicited device inpurt must be assigned to no users.</policy-statement>
<checklist-question>Is the advanced user right to receive unsolicited device input assigned to no users?</checklist-question>
<howto>
<step>Identify all users who hold this right and revoke it.</step>
<step>Identify all applications who hold this right and determine why they need it and revoke it for all those where this requirement is clearly spurious</step>
</howto>
<risks-addressed>
<risk>This right can be used to obtain unauthorised access</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="4.0" title="The user right to force shutdown from a remote system should be assigned to local groups and not to individual users" environment="Any" pleading="recommended" id="NT4GEN-PRIV-2" versionMaj="1" disclosure-level="Any" availability-level="Any" versionMin="0" technology="NT" section="User Configuration:Privileges" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>The user right to force shutdown from a remote system should be assigned to local groups and not to individual users</policy-statement>
<checklist-question>Is the user right to force shutdown from a remote system assigned to local groups and not to individual users?</checklist-question>
<howto>
<step>Assign the right to a local group</step>
<step>Assign users to the group</step>
</howto>
<risks-addressed>
<risk>Security administration is simplified by the use of roles</risk>
<risk>This privilege may allow a denial of service to be executed</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="4.0" title="The advanced user right to increase scheduling priority must  be assigned only to administrators" environment="Any" pleading="mandatory" id="NT4GEN-PRIV-12" versionMaj="1" disclosure-level="Any" availability-level="baseline" versionMin="0" technology="NT" section="User Configuration:Privileges" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>The advanced user right to increase scheduling priority must  be assigned only to administrators</policy-statement>
<checklist-question>Is the advanced user right to increase scheduling priority assigned only to administrators?</checklist-question>
<howto>
<step>Identify all users who hold this right and revoke it.</step>
<step>Identify all applications who hold this right and determine why they need it and revoke it for all those where this requirement is clearly spurious</step>
</howto>
<risks-addressed>
<risk>The ability to increase scheduling priority can be used to hog system resource</risk>
<risk>This privilege may allow an enterprise wide denial of service</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="4.0" title="The advanced user right to modify firmware environment variables must only be assigned to administrators." environment="Any" pleading="mandatory" id="NT4GEN-PRIV-15" versionMaj="1" disclosure-level="Any" availability-level="Any" versionMin="0" technology="NT" section="User Configuration:Privileges" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>The advanced user right to modify firmware environment variables must be assigned only to administrators.</policy-statement>
<checklist-question>Is the advanced user right to modify firmware environment variables assigned only to administrators?</checklist-question>
<howto>
<step>Identify all users who hold this right and revoke it.</step>
<step>Identify all applications who hold this right and determine why they need it and revoke it for all those where this requirement is clearly spurious</step>
</howto>
<risks-addressed>
<risk>Modification of such variables may result in abnormal or unauthorised function</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="4.0" title="The advanced user right to act as part of the operating system must be assigned to no one." environment="Any" pleading="mandatory" id="NT4GEN-PRIV-5" versionMaj="1" disclosure-level="Any" availability-level="Any" versionMin="0" technology="NT" section="User Configuration:Privileges" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>The advanced user right to act as part of the operating system must be assigned to no one.</policy-statement>
<checklist-question>Is the advanced user right to act as part of the operating system assigned to any one?</checklist-question>
<howto>
<step>Identify all users who hold this right and revoke it.</step>
<step>Identify all applications who hold this right and determine why they need it and revoke it for all those where this requirement is clearly spurious</step>
</howto>
<risks-addressed>
<risk>Acting as part of the operating permits privileged action to be undertaken</risk>
<risk>Privileged action may be used to subvert operating system controls</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="4.0" title="The advanced user right to create a token object must not be assigned to any users" environment="Any" pleading="mandatory" id="NT4GEN-PRIV-8" versionMaj="1" disclosure-level="Any" availability-level="Any" versionMin="0" technology="NT" section="User Configuration:Privileges" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>The advanced user right to create a token object must not be assigned to any users</policy-statement>
<checklist-question>Is the advanced user right to create a token object assigned to any users?</checklist-question>
<howto>
<step>Identify all users who hold this right and revoke it.</step>
<step>Identify all applications who hold this right and determine why they need it and revoke it for all those where this requirement is clearly spurious</step>
</howto>
<risks-addressed>
<risk>The ability to create a token object may undermine the authentication system</risk>
<risk>Unauthorised access may be obtained</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="4.0" title="The user right to logon locally should be assigned to local groups and not to individual users" environment="Any" pleading="recommended" id="NT4GEN-PRIV-3" versionMaj="1" disclosure-level="Any" availability-level="Any" versionMin="0" technology="NT" section="User Configuration:Privileges" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>The user right to logon locally should be assigned to local groups and not to individual users.</policy-statement>
<checklist-question>Is the user right to logon locally assigned to local groups and not to individual users?</checklist-question>
<howto>
<step>Assign the right to a local group</step>
<step>Assign users to the group</step>
</howto>
<risks-addressed>
<risk>Managing access rights by role simplfiies administration</risk>
<risk>Complex administration often results in unauthorised access.</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="4.0" title="The user right to change the system time should be assigned to local groups and not to individual user" environment="Any" pleading="recommended" id="NT4GEN-PRIV-1" versionMaj="1" disclosure-level="Any" availability-level="Any" versionMin="0" technology="NT" section="User Configuration:Privileges" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>The user right to change the system time should be assigned to local groups and not to individual users.</policy-statement>
<checklist-question>Is the user right to change the system time assigned to local groups and not to individual users?</checklist-question>
<howto>
<step>Assign the right to a local group</step>
<step>Assign users to the group</step>
</howto>
<risks-addressed>
<risk>Reconstructing a set of events requires coinfidence in time sequencing</risk>
<risk>Certain elements of security infrastructure are sensitive to time</risk>
<risk>Changing the system time nay mask unauthorised activity</risk>
<risk>Changing the system time may result in unauthorised access</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="4.0" title="The advanced user right to logon as a service must be assigned only to administrators" environment="Any" pleading="mandatory" id="NT4GEN-PRIV-14" versionMaj="1" disclosure-level="Any" availability-level="Any" versionMin="0" technology="NT" section="User Configuration:Privileges" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>The advanced user right to logon as a service must be assigned only to administrators</policy-statement>
<checklist-question>Is the advanced user right to logon as a service assigned only to administrators?</checklist-question>
<howto>
<step>Identify all users who hold this right and revoke it.</step>
<step>Identify all applications who hold this right and determine why they need it and revoke it for all those where this requirement is clearly spurious</step>
</howto>
<risks-addressed>
<risk>The ability to create processes as a services can be used to subvert the security controls and gain unauthorised access</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
</controlsection>
<controlsection><title>Authentication/Password Configuration</title>
</controlsection>
</controlchapter>
<controlchapter><title>Security Compliance</title>
<controlsection><title>Security Compliance Checking</title>
</controlsection>
<controlsection><title>Security Management</title>
<control level="baseline" techversion="4.0" title="Antivirus software must be installed and maintained current on all machines" environment="Any" pleading="mandatory" id="NT4GEN-VIRUS-1" versionMaj="1" disclosure-level="Any" availability-level="Any" versionMin="0" technology="NT" section="Security Compliance:Security Management" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Ant-virus software must be installed and maintained on all mahines.</policy-statement>
<checklist-question>Is ant-virus software installed and maintained on all machines?</checklist-question>
<howto>
<step>Install anti-virus software on all machines.</step>
<step>Ensure that the virus engine and signature data files are maintained up to date</step>
</howto>
<risks-addressed>
<risk>Virus infections can often subvert system security controls</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="4.0" title="Ensure that a legal notice appropriate to your jurisdiction is displayed in the legal notice placeholded for display prior to logon" environment="Any" pleading="mandatory" id="NT4GEN-LEGAL-1" versionMaj="1" disclosure-level="Any" availability-level="Any" versionMin="0" technology="NT" section="Security Compliance:Security Management" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Ensure that a legal notice appropriate to your jurisdiction is displayed in the legal notice placeholded for display prior to logon</policy-statement>
<checklist-question>Ensure that a legal notice appropriate to your jurisdiction is displayed in the legal notice placeholded for display prior to logon</checklist-question>
<howto>
<step>Determine the most appropriate legal noice to implement for your jurisdiction</step>
<step>Populate the legal notice placeholder with this message for display prior to logon</step>
</howto>
<risks-addressed>
<risk>Legal action following a subjected breach may prove problematic</risk>
<risk>Monitoring of authorised use may prove problematic</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
</controlsection>
</controlchapter>
<controlchapter><title>Software Requirements</title>
<controlsection><title>Software legislation and compliance</title>
</controlsection>
<controlsection><title>Software acquisition and implementation</title>
</controlsection>
</controlchapter>
<controlchapter><title>Network Security Configuration</title>
<controlsection><title>Network Interface Considerations</title>
<control level="above baseline" techversion="4.0" title="FTP should not be installed or if part of the default image it should be disabled" environment="Any" pleading="recommended" id="NT4GEN-NETW-1" versionMaj="1" disclosure-level="Any" availability-level="Any" versionMin="0" technology="NT" section="Network Security Configuration:Network Interface Considerations" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>FTP should not be installed or if part of the default image it should be disabled</policy-statement>
<checklist-question>Is FTP installed or if part of the default image is it disabled?</checklist-question>
<howto>
<step>Build a server, w/s or domain controller image that does not include ftp by default</step>
<step>Alternatively, disable ftp on w/s, servers and controllers where not needed</step>
</howto>
<risks-addressed>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
</controlsection>
<controlsection><title>Internet Considerations</title>
</controlsection>
</controlchapter>
<controlchapter><title>Asset Security Requirements</title>
<controlsection><title>Ownership, Accountability and Inventories</title>
</controlsection>
<controlsection><title>Classification Labelling</title>
</controlsection>
</controlchapter>
<controlchapter><title>Compliance</title>
<controlsection><title>The Companies Act 1985</title>
</controlsection>
<controlsection><title>Data Protection Act 1998</title>
</controlsection>
<controlsection><title>Computer Misuse Act 1990</title>
</controlsection>
<controlsection><title>Information Security Policy</title>
</controlsection>
</controlchapter>
<controlchapter><title>Physical Security Requirements</title>
<controlsection><title>Outer perimeter - public access space</title>
</controlsection>
<controlsection><title>Inner perimeter - general space</title>
</controlsection>
</controlchapter>
<controlchapter><title>Internet/Email Security Requirements</title>
<controlsection><title>General Internet security requirements</title>
</controlsection>
</controlchapter>
<controlchapter><title>Configuration</title>
<controlsection><title>Files and File Permissions</title>
<control level="above baseline" techversion="4.0" title="Use encryption for sensitive data files" environment="Any" pleading="mandatory" id="NT4GEN-FILE-1" versionMaj="1" disclosure-level="above baseline" availability-level="Any" versionMin="0" technology="NT" section="Configuration:Files and File Permissions" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Sensitive data files must be encrypted.</policy-statement>
<checklist-question>Are sensitive data files encrypted?
</checklist-question>
<howto>
<step>Use an encryption tool or an encrypted file system to store sensitive data files. </step>
</howto>
<risks-addressed>
<risk>Sensitive data files will be accessible using non-standard tools when the NT operating system does not have control.</risk>
<risk>Sensitive data files which have been deleted may be accessible using non-standard tools when the NT operating system does not have control.</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
</controlsection>
<controlsection><title>Administration</title>
<control level="baseline" techversion="4.0" title="Clear Page File at Shutdown" environment="Any" pleading="mandatory" id="NT4GEN-ADM-1" versionMaj="1" disclosure-level="Any" availability-level="Any" versionMin="0" technology="NT" section="Configuration:Administration" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Enable clearing of the system page file at shutdown.</policy-statement>
<checklist-question>Has clearing of the system page file at shutdown been enabled?
</checklist-question>
<howto>
<step>Set the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SessionManager\Memory Management\ClearPageFileAtShutdown to 1.</step>
</howto>
<risks-addressed>
<risk>Sensitive information, including local and remote passwords and business information, may remain in the pagefile after shutdown. This may be recoverable by an attacker who has physical access to the machine.</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
</controlsection>
<controlsection><title>Backups</title>
</controlsection>
</controlchapter>
<controlchapter><title>System Development and Maintenance Requirements</title>
<controlsection><title>General Software Requirements</title>
</controlsection>
<controlsection><title>Change Control Procedures</title>
</controlsection>
<controlsection><title>Application system security</title>
</controlsection>
<controlsection><title>Security requirements for Analysis and Specification</title>
</controlsection>
<controlsection><title>Test Data Security</title>
</controlsection>
<controlsection><title>Control of operational software</title>
</controlsection>
<controlsection><title>Security of electronic office systems</title>
</controlsection>
</controlchapter>
<controlchapter><title>Installation</title>
<controlsection><title>Setup Choices</title>
<control level="baseline" techversion="4.0" title="Do not use dual-boot" environment="Any" pleading="mandatory" id="NT4GEN-SETUP-2" versionMaj="1" disclosure-level="Any" availability-level="Any" versionMin="0" technology="NT" section="Installation:Setup Choices" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>NT must be the only operating system installed. The system must not be set up to dual-boot other operating systems.</policy-statement>
<checklist-question>Is NT the only operating system installed?
</checklist-question>
<howto>
<step>Remove other operating systems by formatting partitions to NTFS prior to installation.</step>
<step>Ensure that boot.ini automatically boots NT, and that it lists no other operating systems.</step>
</howto>
<risks-addressed>
<risk>Filesystems will not be protected by NT ACLs.</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="above baseline" techversion="4.0" title="Restrict access to alternate boot mechanisms" environment="Any" pleading="mandatory" id="NT4GEN-SETUP-3" versionMaj="1" disclosure-level="Any" availability-level="Any" versionMin="0" technology="NT" section="Installation:Setup Choices" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Only authorised users must be able to boot the system from alternative media (CD, floppy disk).</policy-statement>
<checklist-question>Has access to alternative boot mechanisms been physically and/OR BIOS password restricted?
</checklist-question>
<howto>
<step>Ensure that the BIOS boot order boots from the hard disk before CD, floppy, or other bootable devices.</step>
<step>Assign a BIOS password to prevent changes to the boot order, and restrict access to the BIOS password to authorised personnel.</step>
</howto>
<risks-addressed>
<risk>NT ACLs may be bypassed by booting an alternative operating system.</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="4.0" title="Delete $WinNT$.inf files" environment="Any" pleading="mandatory" id="NT4GEN-SETUP-4" versionMaj="1" disclosure-level="Any" availability-level="Any" versionMin="0" technology="NT" section="Installation:Setup Choices" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>For unattended setups the $WinNT$.inf file should be deleted.</policy-statement>
<checklist-question>For unattended setups, has the $WinNT$.inf file been deleted after installation?
</checklist-question>
<howto>
<step>Ensure any $WinNT$.inf files are removed after an unattended installation.</step>
</howto>
<risks-addressed>
<risk>The username and password of the user used to add the machine to the domain may be exposed.</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="4.0" title="Installation disk image duplication" environment="Any" pleading="mandatory" id="NT4GEN-SETUP-5" versionMaj="1" disclosure-level="Any" availability-level="Any" versionMin="0" technology="NT" section="Installation:Setup Choices" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Do not install by duplicating a previous disk image, unless the disk image copy tool used is NT-aware and capable of assigning a unique machine SID after duplication.</policy-statement>
<checklist-question>For installations using disk image duplication, has the machine been assigned a unique SID?
</checklist-question>
<howto>
<step>Do not install using a disk image duplication.</step>
<step>Or, if using disk image duplication, ensure that the disk image duplication tool is NT-aware and able to assign unique machine SIDs after duplication.</step>
</howto>
<risks-addressed>
<risk>Machines and user accounts will have duplicate SIDs, undermining the security enforcement of NT.</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="4.0" title="Format all disk partitions with NTFS" environment="Any" pleading="mandatory" id="NT4GEN-SETUP-1" versionMaj="1" disclosure-level="Any" availability-level="Any" versionMin="0" technology="NT" section="Installation:Setup Choices" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>All filesystem partitions must be formatted prior to installation as NTFS.</policy-statement>
<checklist-question>Are all partitions formatted as NTFS?
</checklist-question>
<howto>
<step>Choose Format as NTFS from setup menus.</step>
<step>Do not use FAT partitions during installation, format as NTFS during installation.</step>
</howto>
<risks-addressed>
<risk>Filesystems will not be protected by NT ACLs.</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="4.0" title="Do not use HPFS or FAT file structures. Always use NTFS." environment="Any" pleading="mandatory" id="NT4GEN-SETUP-6" versionMaj="1" disclosure-level="Any" availability-level="Any" versionMin="0" technology="NT" section="Installation:Setup Choices" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Do not use HPFS or FAT file structures. Always use NTFS.</policy-statement>
<checklist-question>Are there any FAT or HPFS partitions on the system?</checklist-question>
<howto>
<step>Opt for using NTFS alone during system commissioning</step>
</howto>
<risks-addressed>
<risk>Other file structures do not consistently support windows NT access control</risk>
<risk>The use of other file structures may be used to subvert security controls</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
</controlsection>
</controlchapter>
<controlchapter><title>Auditing and Monitoring</title>
<controlsection><title>Events to be alerted in real-time</title>
</controlsection>
<controlsection><title>Audit log destination and format</title>
<control level="baseline" techversion="4.0" title="Security event logging must be enabled and not set to overwrite events" environment="Any" pleading="mandatory" id="NT4GEN-AUDIT-4" versionMaj="1" disclosure-level="Any" availability-level="Any" versionMin="0" technology="NT" section="Auditing and Monitoring:Audit log destination and format" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Security event logging must be enabled and not set to overwrite events</policy-statement>
<checklist-question>Is security event logging enabled and set so as not to overwrite events?</checklist-question>
<howto>
<step>Switch security event logging on</step>
<step>Configure event logging so as not to overwrite events</step>
</howto>
<risks-addressed>
<risk>Reconstruction of a sequence of a sequence of events requires events to be recorded</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
</controlsection>
<controlsection><title>Events to be audited</title>
<control level="baseline" techversion="4.0" title="Set up file auditing for group everyone" environment="Any" pleading="recommended" id="NT4GEN-AUDIT-3" versionMaj="1" disclosure-level="Any" availability-level="Any" versionMin="0" technology="NT" section="Auditing and Monitoring:Events to be audited" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>File auditing for group everyone should be set up to record failed attempts for read, write, execute and success and failure for delete, change permissions and take ownership.</policy-statement>
<checklist-question>Has file auditing been set up for group everyone?</checklist-question>
<howto>
<step>Set up file auditing for group everyone as follows;</step>
<step>Read - Audit failed attempts</step>
<step>Write - Audit failed  attempts</step>
<step>Execute - Audit failed attempts</step>
<step>Delete - Audit failure and success</step>
<step>Change Permissions - Audit failure and success</step>
<step>Take Ownership - Audit failure and success</step>
</howto>
<risks-addressed>
<risk>Reconstructing a sequence of events requires certain events to be recorded</risk>
<risk>Failing to record certain events may allow a breach or a failure to go undetected</risk>
<risk>Failing to record certain events may prevent successful recovery from a breach or a failure</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="4.0" title="Set up directory auditing for group everyone" environment="Any" pleading="mandatory" id="NT4GEN-AUDIT-2" versionMaj="1" disclosure-level="Any" availability-level="Any" versionMin="0" technology="NT" section="Auditing and Monitoring:Events to be audited" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Set up directory auditing for group everyone such that failed attempts are recorded for read, write, execute and failed and successful attempts are recorded for delete, change permissions and take ownership.</policy-statement>
<checklist-question>Has directory auditing for group everyone been set up in accordance with policy?</checklist-question>
<howto>
<step>Set up directory auditing for group everyone as follows;</step>
<step>Read - Audit failed attempts</step>
<step>Write - Audit failed attempts</step>
<step>Execute - Audit failed attempts</step>
<step>Delete - Audit failure and success</step>
<step>Change Permissions - Audit failure and success</step>
<step>Take Ownership - Audit failure and success</step>
</howto>
<risks-addressed>
<risk>Without an audit trail of activity reconstructing misuse cannot be achieved</risk>
<risk>A loss of accountability may occur</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="4.0" title="Network alerts must be enabled for excessive login failures" environment="Any" pleading="mandatory" id="NT4GEN-AUDIT-5" versionMaj="1" disclosure-level="Any" availability-level="Any" versionMin="0" technology="NT" section="Auditing and Monitoring:Events to be audited" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Network alerts must be enabled for excessive login failures</policy-statement>
<checklist-question>Are network alerts enabled for excessive login failures?</checklist-question>
<howto>
<step>Configure network alerts for excessive login failures</step>
</howto>
<risks-addressed>
<risk>Non-interactive/network login failures may be indicative of an attack</risk>
<risk>Non-interactive/network login failures may be indicative of a failed service</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="4.0" title="The audit policy must be set up to record failure and success for Logon and Logoff, User and Group Management, Security Policy Changes, Restart, Shutdown and System and failure for File and Object Access" environment="Any" pleading="mandatory" id="NT4GEN-AUDIT-1" versionMaj="1" disclosure-level="Any" availability-level="Any" versionMin="0" technology="NT" section="Auditing and Monitoring:Events to be audited" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>The audit policy must be set up to record failure and success for Logon and Logoff, User and Group Management, Security Policy Changes, Restart, Shutdown and System and failure for File and Object Access</policy-statement>
<checklist-question>Has the audit policy been set up to record the events defined in the audit policy?</checklist-question>
<howto>
<step>Set up audit policy as follows;</step>
<step>Logon and Logoff	Audit failure and success</step>
<step>File and Object Access	Audit failure</step>
<step>User and Group Management	Audit failure and success</step>
<step>Security Policy Changes	Audit failure and success</step>
<step>Restart, Shutdown and System	Audit failure and success</step>
</howto>
<risks-addressed>
<risk>Capturing events allows an audit trail of activity to be created</risk>
<risk>A failure to capture events prevents abnormal activity from being identified</risk>
<risk>This allows an attackers behviour to go unnoticed.</risk>
<risk>Failing to record security events may result in a loss of accountability</risk>
<risk>A loss of accountability makes it difficult to determine the nature of a breach</risk>
<risk>This may result in regulatory compliance breaches</risk>
<risk>This may make legal action problematic to pursue</risk>
<risk>This may make reconstructing the system securely difficult to achieve</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="4.0" title="Set up registry key auditing for group everyone" environment="Any" pleading="recommended" id="NTGEN-AUDIT-4" versionMaj="1" disclosure-level="Any" availability-level="Any" versionMin="0" technology="NT" section="Auditing and Monitoring:Events to be audited" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Registry key auditing should be set up to not audit query value, create subkey, read control, to audit successful attempts to set value, enumerate subkeys, notify, create link, delete and to audit successful and unsucessful attempts to write DAC</policy-statement>
<checklist-question>Has registry key auditing been set up in accordance with policy?</checklist-question>
<howto>
<step>Set up registry key auditing as follows;</step>
<step>Query Value - Not audited</step>
<step>Set Value - Audit successful attempts</step>
<step>Create Subkey - Not audited</step>
<step>Enumerate Subkeys - Audit successful attempts</step>
<step>Notify - Audit successful attempts</step>
<step>Create Link - Audit successful attempts</step>
<step>Delete - Audit successful attempts</step>
<step>Write DAC - Audit successful and unsuccessful attempts</step>
<step>Read Control - Not audited</step>
</howto>
<risks-addressed>
<risk>Reconstructing a sequence of evnts requires events to be recorded</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
</controlsection>
</controlchapter>
<controlchapter><title>Other</title>
</controlchapter>
</standard>

