Modül dersleri (3/3)
Progetto: audit DNS difensivo
Project: a defensive DNS audit
Use a fictional training domain and review its DNS from the perspective of the services that consume the records. Check delegation, authoritative availability, common records, mail policy, certificate policy, DNSSEC status, and exposure of resolver or transfer services. Do not scan or change real domains unless you have explicit authorization.
For each finding, record the exact observation, how to reproduce it, the affected asset, likely impact, confidence, and a practical correction. Separate evidence from assumptions. Give each issue a priority and a clear closure test so someone else can confirm that the fix worked.
A TXT or TLSA value is not a policy simply because it exists. Check its syntax, meaning, alignment, trust chain, and operational owner. Make recommendations that fit the service and can be verified after implementation.
Check your understanding
Choose the best answer. This quiz runs locally and sends no DNS queries to real domains.
What makes an audit finding verifiable?