Configure Authentication Types

WS08_MCA_00044 (ObjectTemplate)

Windows Server 2008: This control activity guides the IT professional through configuration of two-factor authentication.

Element properties:

TypeSystem.Compliance.ManualControlActivityProjection

Source Code:

<ObjectTemplate ID="WS08_MCA_00044" TypeID="GRCControl!System.Compliance.ManualControlActivityProjection">
<Property Path="$Context/Property[Type='GRC!System.Compliance.ControlActivity']/ExternalName$">$MPElement[Name='GRC!System.Compliance.SourceNameEnum.MicrosoftCorporation']$</Property>
<Property Path="$Context/Property[Type='GRC!System.Compliance.ControlActivity']/ExternalId$">WS08_MCA_00044</Property>
<Property Path="$Context/Property[Type='GRC!System.Compliance.ControlActivity']/ExternalVersion$">1.0</Property>
<Property Path="$Context/Property[Type='GRC!System.Compliance.ControlActivity']/Type$">$MPElement[Name='GRCControl!System.Compliance.ControlActivity.TypeEnum.Preventive']$</Property>
<Property Path="$Context/Property[Type='GRC!System.Compliance.ControlActivity']/Title$">Configure Authentication Types</Property>
<Property Path="$Context/Property[Type='GRC!System.Compliance.ControlActivity']/DisplayName$">WS08_MCA_00044 Configure Authentication Types</Property>
<Property Path="$Context/Property[Type='GRC!System.Compliance.ControlActivity']/Description$">Windows Server 2008: This control activity guides the IT professional through configuration of two-factor authentication.</Property>
<Property Path="$Context/Property[Type='GRC!System.Compliance.ControlActivity']/ImplementationMethod$">The product can be configured to require two-factor smart card authentication through central configuration of Group Policy settings. Security baselines available from Microsoft do not configure this setting by default, as not all environments may desire to enforce smartcard authentication for all logon actions. Discuss the potential impact of enforcing smartcard logon with your IT department, and departments affected by this choice. If smartcard enforcement is required, it may be configured using the following Group Policy setting.

To apply the setting:
GPO Setting: Interactive Logon: Smart card removal behavior
GPO Setting Value: 1
GPO Setting Location: Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\</Property>
<Property Path="$Context/Property[Type='GRC!System.Compliance.ControlActivity']/AdditionalGuidance$">For more information, see:

"Security Compliance Manager" at http://technet.microsoft.com/en-us/library/cc677002.aspx
</Property>
<Property Path="$Context/Property[Type='GRC!System.Compliance.ControlActivity']/TestSummary$">Manual Assertion

Manually assert whether the procedure has been sufficiently and reasonably performed since the last assertion.

Manual assertions should be recorded at a frequency that is commensurate with audit sample sizes and frequencies, which can vary according to GRC authority document requirements and your organization's audit schedule. Determine what personnel will make the manual assertion by asking the GRC program manager. Typically, this assertion will be made by an analyst who observes an IT professional that enacts the process.

Record the compliance state as an assertion within the GRC program with one of the following states: compliant, noncompliant, error, or unknown.

Manual Assertion Steps:

1. Open the Service Manager Console.
2. Click the Compliance and Risk Items Workspace.
3. Expand the Control Management folder, then the Control Activities folders and select the All Control Activities View.
4. In the Control Activities View, select control activities for which you want to add a result and in the Task pane select Edit Control Activity. Service Manager Console launches the Control Activity form with the selected control activity.
5. In the Control Activity form, in the Task pane, select the Add Result Console task. Service Manager Console launches the Select Template dialog.
6. Select one of the templates for the results (Compliant, Non-Compliant, Unknown or Error). The Result form will open with the Result set to the control activity template name (for example, Compliant means Result = Compliant, and so on). The owner field is populated with the current user name.
7. Select one of the programs from the Program section before Results (OK button is enabled).
8. Save the results by clicking OK in the dialog. Service Manager Console creates a Number of Managed Entity Results per Configuration Item in Scope for the selected programs. Service Manager Console will close the Add Result dialog and create a relationship between the control activity and Managed Entitiy Result in the CMDB. The Control Activity form remains open and displays the updated control activity in the form.
</Property>
<Property Path="$Context/Property[Type='GRC!System.Compliance.ControlActivity']/TestId$"/>
<Property Path="$Context/Property[Type='GRC!System.Compliance.ControlActivity']/TestName$"/>
<Property Path="$Context/Property[Type='GRC!System.Compliance.ControlActivity']/SupportedControlObjectives$">GRC_MCO_00006</Property>
</ObjectTemplate>