Microsoft Outlook 2013 Security Technical Implementation Guide

The Microsoft Outlook 2013 Security Technical Implementation Guide (V1 R14) has 82 STIG checks. New to STIG checklists? Read What is a STIG checklist?, CKL vs CKLB, and STIG vs SCAP benchmark.

Find STIG checks

82STIG checks

Search filters this STIG's checks locally. Separate terms must all match (use quotes for an exact phrase). A search you ran on the Search page carries over here.

Severity

Version

V1 · R14

CurrentPublished Thu Jan 30 2025

Outlook minimum encryption key length settings must be set.

Microsoft Outlook 2013 Security Technical Implementation Guide

Assessment Title

Rule Text

Outlook minimum encryption key length settings must be set.

Description

Discussion Text

This setting allows the minimum key length for an encrypted email message to be configured.

Satisfies: SRG-APP-000514, SRG-APP-000555, SRG-APP-000625, SRG-APP-000630, SRG-APP-000635, SRG-APP-000416

New to STIG checklists? Read What is a STIG checklist? and CKL vs CKLB.

Objective

V-242739

Rule

SV-242739r961857_rule

Severity

medium

Rule Version

DTOO316

Documentable

false

IA Controls

NIST SP 800-53

Rev 5

Assessment Procedure

Check Text

Verify the policy value for User Configuration -> Administrative Templates -> Microsoft Outlook 2013 -> Security -> Cryptography "Minimum encryption settings" is set to "Enabled: 168 bits".

Procedure: Use the Windows Registry Editor to navigate to the following key: 

HKCU\Software\Policies\Microsoft\Office\15.0\outlook\security

Criteria: If the value MinEncKey is REG_DWORD = 168, this is not a finding.

Implementation Procedure

Fix Text

Set the policy value for User Configuration -> Administrative Templates -> Microsoft Outlook 2013 -> Security -> Cryptography "Minimum encryption settings" to "Enabled: 168 bits".

STIG check 76 of 82 in the Microsoft Outlook 2013 STIG checklist

← Previous · V-242738Outlook must be configured not to prompt users to choose security settings if default settings fail.Next · V-242740 →Replies or forwards to signed/encrypted messages must be signed/encrypted.