Peter Lowe

I made a thing: it's called the DNS Museum, and it's because I kept joking at the start of my talk, "Bizarre and Unusual Uses of DNS" that a lot of the things weren't alive anymore - so it was more like a museum of DNS and I was the curator. Anyway, I'm on holiday right now so I finally got around to doing something about that joke. Consider this a first draft, I have way more notes about other things to add at some point. It's also a little bland, but one thing I'm not is a designer. Let me know about any issues - AI was used to help create the site, but of course I'm responsible for any mistakes. It's on GitHub too, so PRs are welcome. https://dns.museum

@notecharlie@social.bigcavemaps.com Innnnnteresting. Thanks, I'll look into that! Edit: I actually heard of Hesiod but I confess I don't know much about it. Really appreciate the pointer.

On defining exactly what a "vulnerability" actually is: https://research.empiricalsecurity.com/research/the-vulnerability-identity-crisis Really interesting discussion and proposals on how to define a "vulnerability" by @jayjacobs@infosec.exchange

I've seen so many "discovery" mechanisms proposed for DNS lately. In general I think these methods are great -- AI agent discovery (_agent), AI agent capabilities and trust (_atn), designated DNS resolver discovery (_dns), "for sale" (_for-sale) -- but it's getting pretty crowded in the underscore namespace! I'm genuinely tempted to write up a new draft for discovery of discovery records.

Er, EXCUSE ME @BBCNews@flipboard.com but SPOILER!

The @firstdotorg@infosec.exchange #DNS Abuse SIG needs YOU! Even if you're not a member of FIRST. We have members from all over the DNS industry, from all over the world, and we're looking for members of the DNS security community with an operational background to grow the group. For one reason or another meetings are sometimes a little light on attendees, which is a shame because we're doing some really interesting work. And there's the potential for doing even more cool stuff. We have biweekly meetings every other Thursday at 21:00 JST (12:00 BST, 07:00 ET) which are friendly, informal, comfortably unstructured Zoom calls where we discuss ongoing work and general DNS topics. There's also a mailing list (which is very low-traffic) and a Slack channel (where most communication happens). Currently we're working on adjustments to the DNS Abuse Techniques Matrix - changes to the work we've already done - and welcome insight from stakeholders on the topic of DNS abuse, its classification, and how it can be detected, mitigated, and prevented. We also cover adjacent topics, like tooling, use of AI for the website and data, and how best to make it all work. You don't have to know everything - it's fine if you know one thing that everyone else doesn't. Or can ask a question that nobody else thought of. To explain the process: applications from people outside of FIRST don't need sponsorship or anything, but they are sent to the group first. If there are no objections after a short time, then your application will be accepted. If not, then we'll explain why. And if you're already in FIRST, then your application is just a formality and we invite you straight away. "My DMs are open" - message me if you'd like any more info! It's slow season right now so a perfect time to get on board. Apply to join, and find out more, from our homepage on the FIRST website: https://www.first.org/global/sigs/dns/

Weekly block list report: 3,539 entries; 3,517 valid / 22 invalid; 0 deleted #ads #adblocking #blocklist #trackers #pglblocklistreport List URL: https://pgl.yoyo.org/as/serverlist.php

Weekly block list report: 3,536 entries; 3,518 valid / 18 invalid; 1 deleted #ads #adblocking #blocklist #trackers #pglblocklistreport List URL: https://pgl.yoyo.org/as/serverlist.php

The FIRST DNS Abuse SIG will soon be working on some tools for detecting DNS abuse, and we'll need some datasets to verify them. Do you have a dataset which we could use? Query logs, netflow data, attack signatures, anything that we'd be able to point a tool at, and it verify an abuse type - would be super useful. Get in touch if you think you might be able to help!

Weekly block list report: 3,535 entries; 3,512 valid / 23 invalid; 2 deleted #ads #adblocking #blocklist #trackers #pglblocklistreport List URL: https://pgl.yoyo.org/as/serverlist.php

Weekly block list report: 3,542 entries; 3,517 valid / 25 invalid; 3 deleted #ads #adblocking #blocklist #trackers #pglblocklistreport List URL: https://pgl.yoyo.org/as/serverlist.php

@scottwilson@infosec.exchange Thanks Scott!

@bortzmeyer@mastodon.gougere.fr Of course you did, Stéphane. Of COURSE you did.