Adding Email Headers and Transit Protection
An engineer needs to add protection for data in transit and have headers in the email message. Which configuration is needed to accomplish this goal?
Community Insight
The exam tests the distinction between dedicated legacy hardware and the modern unified appliance, where provisioning the Email Security Appliance (ESA) enables both TLS encryption and header manipulation via content filters.
This question addresses configuring email security features to protect data in transit and insert specific headers into messages using the Cisco Security Email Threat Defense platform.
Many learners select 'Deploy an encryption appliance' due to outdated study materials referencing the obsolete Cisco IronPort Encryption Appliance, which was discontinued years ago.
Community Discussion (22 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Provisioning the Email Security Appliance (ESA) is the correct configuration because it serves as a unified platform for securing email traffic. The ESA handles protection for data in transit by enforcing TLS encryption and allows administrators to add or modify message headers using Content Filters or Message Filters. This capability is a standard feature of the modern Cisco Secure Email Threat Defense solution.Why the Other Options Are Wrong
Deploying an encryption appliance (Option A) refers to a legacy, out-of-support product (Cisco IronPort Encryption Appliance) that has been End-of-Support since 2015. Mapping sender IP addresses (Option C) is a basic network configuration unrelated to email-specific header insertion or application-layer encryption. Enabling flagged message handling (Option D) typically relates to spam classification or user notifications, not the cryptographic protection or structural modification of email headers.Community Comment Notes
Community consensus heavily favors Option B, with users noting that while older guides might mention encryption appliances, the current ecosystem relies on the ESA. As NikoNiko noted, "WSA: AsyncOS enables you to add encryption settings... by inserting an SMTP HEADER," confirming the functionality resides within the main appliance software. Another user, FortiSherlock, highlighted that the dedicated encryption appliance is "past End-of-Life," reinforcing why Option A is incorrect in a modern context.Exam Strategy
Focus on the current Cisco product portfolio rather than legacy equipment. When questions involve email security, assume the answer involves the primary Email Security Appliance (ESA) unless specifically asking about a deprecated component.
Frequently Asked Questions
Why is deploying an encryption appliance incorrect?
The dedicated Cisco IronPort Encryption Appliance has been End-of-Support since 2015. Modern email security is handled by the unified Email Security Appliance (ESA).
How does the ESA add headers to messages?
Administrators can use Content Filters or Message Filters within the ESA to insert, modify, or remove SMTP headers based on defined policies.