SV-29238r1: The user is allowed to launch Windows Messenger (MSN Messenger, .NET Messenger). | Windows Vista Security Technical Implementation Guide

Loading benchmark…

Assessment Title

Rule Text

The user is allowed to launch Windows Messenger (MSN Messenger, .NET Messenger).

Description

Discussion Text

This setting prevents the Windows Messenger client from being run. Instant Messaging clients must be in compliance of with the Instant Messaging STIG. Windows Messenger should not be active on Windows unless the instant messaging system is a Managed Enterprise Service for unclassified data for which the DAA has approved.

How this relates to the STIG checklist: STIG vs SCAP benchmark.

IA Controls

NIST SP 800-53

Not mappedCCI-000381CCE-3316-7

Additional Details

Responsibility

Information Assurance Officer

References

DPMS Target Windows Vista DISA DPMS Target Windows Vista 1029

SCC Automation Reference

The reconstructed evaluation script behind this rule's OVAL check(s) — every module a compound check combines, with this rule's own concrete values and DISA's SCC tool's real per-module mechanism curated from static teardown of SCC releases.

# Windows PowerShell
# Reconstructed from oval:mil.disa.fso.windows:def:455
# The user is allowed to launch Windows Messenger (MSN Messenger, .NET Messenger).
# Per-module read mechanism curated from static teardown of DISA's SCC tool
# (SCAP Compliance Checker) -- see the SCC Automation Reference above.

# registry_object (registry_test)
function test_1 {
  return ($null -ne (Get-ItemProperty -Path 'Registry::HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Messenger\Client' -Name 'PreventRun'))
}
# registry_object (registry_test)
function test_2 {
  return ((@{String='reg_sz';ExpandString='reg_expand_sz';Binary='reg_binary';DWord='reg_dword';MultiString='reg_multi_sz';QWord='reg_qword';None='reg_none'}[(Get-Item -Path 'Registry::HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Messenger\Client').GetValueKind('PreventRun').ToString()]) -eq 'reg_dword')
}
# registry_object (registry_test)
function test_3 {
  return (-not ($null -ne (Get-ItemProperty -Path 'Registry::HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Messenger\Client' -Name 'PreventRun')))
}
# registry_object (registry_test)
function test_4 {
  return (((Get-ItemProperty -Path 'Registry::HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Messenger\Client' -Name 'PreventRun' -ErrorAction SilentlyContinue) | Select-Object -ExpandProperty 'PreventRun') -eq 1)
}
# registry_object (registry_test)
function test_5 {
  return (-not ($null -ne (Get-ItemProperty -Path 'Registry::HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Messenger\Client' -Name 'PreventRun')))
}

if ((test_1 -and (test_2 -or test_3) -and (test_4 -or test_5))) {
  Write-Output "PASS"
} else {
  Write-Output "FAIL"
}

Assessment Script Powered by AISyntax-verified

A standalone PowerShell script to assess this control automatically. Review before running it in your environment.

Syntax-checked as valid PowerShell. Not executed here — running it for real needs the actual windows_vista target this check assesses.

# oval:mil.disa.fso.windows:def:455
$registryPath = "HKLM:\Software\Policies\Microsoft\Messenger\Client"
if (-Not (Test-Path $registryPath)) { Write-Output "PASS"; exit 0 }
$preventRun = Get-ItemProperty -Path $registryPath -Name PreventRun -ErrorAction SilentlyContinue
if ($preventRun -eq $null) { Write-Output "PASS"; exit 0 }
if ($preventRun.PreventRun -eq 1) { Write-Output "PASS"; exit 0 }
Write-Output "FAIL"; exit 1

Remediation

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Windows Messenger “Do Not Allow Windows Messenger to be Run” to “Enabled”.