Since I'm managing security tools and focusing on email security, Cloudflare mainly helps me take care of DNS records that are related to email security, such as SPF, DMARC, and DKIM. That's the main scope of my interest there. I'm monitoring those records, checking if somebody has altered them, and gathering evidence if needed to warn them not to do that anymore.
Cloudflare is a great product with many useful features. A colleague of mine is leveraging the API to get all the records periodically. We're gathering them to review if everything is set up properly without the need for manual review. I appreciate the additional details about the statistics since the DKIM enablement process requires visibility over whether the DKIM keys are being used and if there were any queries against them. The statistics part lets me briefly validate if the DKIM record is in use because over time, the records stop being used and aren't cleaned up because nobody requested that.
The reporting and auditing tools are important in the use cases I mentioned earlier. There are many features I do not configure but know exist, such as web access firewall to set up accesses to certain DNS records. We were also using the Workers part of Cloudflare to share data from Cloudflare to an external app called Salt, which helped us understand where our API endpoints are in our estate. Based on that, we got information about endpoint locations and unusual API queries.
It simplifies management because you can create domain groups and associate them to countries, allowing them to manage them independently. It helps me understand which country might be responsible for specific domains. It's a great product because it's scalable, has great coverage, and is mature with good defenses against DDoS attacks.