What is the difference between SPF, DKIM, and DMARC?
SPF names the servers allowed to send for a domain, DKIM signs the message, and DMARC decides what happens when they fail and sends reports.

Exam objectiveGiven a scenario, modify enterprise capabilities to enhance security
Objective 4.5 covers how to modify existing enterprise capabilities to strengthen security, across network, host, data, messaging, and identity controls.
Network controls. A firewall allows or blocks traffic using rules, access lists, ports and protocols, and screened subnets. An IDS watches passively and alerts, while an IPS sits inline and can block. Signature detection compares traffic with known attack patterns, and trend or anomaly detection compares it with a learned baseline, which can catch new attacks at the cost of more false positives. Web filters can see the full URL through an agent, or through a centralized proxy that decrypts HTTPS, and use URL scanning, content categorization, block rules, and reputation; DNS filters see only the domain name but cover any device that uses the resolver.
Platforms, protocols, and email. Group Policy centrally distributes Windows configuration, and SELinux enforces mandatory access control on Linux through security labels and policy. Secure protocol implementation means choosing the right protocol, port, and transport method. SPF names the servers allowed to send for a domain, DKIM signs the message, and DMARC sets the policy and reporting when those checks fail, while an email gateway filters spam, phishing, and malware.
Data, devices, and behavior. File integrity monitoring (FIM) detects unauthorized change, DLP stops sensitive data from leaving, and network access control (NAC) decides whether a device may connect at all. EDR records and responds to behavior on endpoints, XDR correlates across domains, and user behavior analytics flags an account that departs from its own baseline.
Exam scenarios describe a problem and ask which capability to change, so note which layer each control sees: network, host, data, or identity.
This page is the map. Knotch is where you drill it until it sticks.
SPF checks whether the connecting server is on the domain's published list of allowed senders. DKIM checks a cryptographic signature on the message itself.
Signature detection matches predefined attack patterns, so it is precise for known threats but can miss new attacks or variants that match no signature. Anomaly detection compares traffic with a learned baseline, so it can catch new attacks but produces more false positives.
A web filter can see the full URL, including the path, for devices with an agent or for HTTPS traffic the proxy decrypts. A DNS filter sees only the domain name, but covers any device that uses the resolver.
EDR is centered on endpoints, recording and responding to behavior on the device. XDR correlates detection across multiple domains beyond the endpoint.
The full set of look-alike pairs for this objective is inside Knotch.
An IDS catches thousands of known exploits, but a brand-new exploit passes through without any alert.
Which limitation BEST explains this?
A signature describes a known attack pattern, so an exploit that matches no existing signature goes undetected.
Signatures match predefined attack patterns, so they are precise for known threats but can miss new attacks or variants that match no existing signature, and they must be kept up to date. Anomaly detection can catch new attacks at the cost of more false positives.
Why not B: An IDS is passive by design and still raises alerts when something matches.
Why not C: Learning a baseline describes anomaly detection, not signatures.
Why not D: Placement affects what is seen, and too much traffic would not hide only the new exploit.
SPF names the servers allowed to send for a domain, DKIM signs the message, and DMARC decides what happens when they fail and sends reports.
No. A look-alike domain the attacker really owns passes all three for that domain, so gateways should flag newly registered and look-alike domains, backed by user awareness.
Implicit TLS is encrypted from the start of the connection. STARTTLS upgrades a connection to encryption after a cleartext start.
