Elektrine lite

← Feed

disclose.io :verified:

disclose@infosec.exchange

<p>Free open-source tools to standardize, normalize, and promote the adoption of vulnerability reporting and disclosure. <a href="https://infosec.exchange/tags/internetimmunesystem" class="mention hashtag" rel="tag">#<span>internetimmunesystem</span></a> <a href="https://infosec.exchange/tags/hacktheplanet" class="mention hashtag" rel="tag">#<span>hacktheplanet</span></a></p>

Posts

  • View post

    Domain, URL, IP, ASN, package, repo, etc goes in &amp;gt;&amp;gt;&amp;gt; Likely owner and the best available reporting route out with the guesses labelled as guesses and a CERT/CNA fallback when nobody has published anything. Web-driven, and designed to be API/AI-first to support modern toolchains. Free, no login, nothing gets scanned.

  • View post

    On August 12 the White House published a memorandum directing a federal program that will authorize vetted private US companies to conduct cyber surveillance and cyber effects operations against foreign cybercrime organizations, under DOJ and DHS oversight. Our factual analysis of what the memo says, what it doesn&amp;#39;t, and why authorization is the load-bearing concept: https://blog.disclose.io/white-house-private-sector-cyber-operations-memo/ #cybersecurity #policy

  • View post

    NIST is asking how to modernize the NVD in the age of AI, months after saying most new CVEs are now lowest priority for enrichment. Comments close October 13 (docket NIST-2026-0100). Our analysis covers what NIST is asking, the AI enrichment failure modes worth putting on the record, and what a useful comment looks like: https://blog.disclose.io/nvd-modernization-rfi-2026/ #NVD #CVE #infosec #cybersecurity

  • View post

    Policy Pulse #29: the White House authorized vetted private firms to run offensive cyber operations against foreign cybercriminals, and never touched the CFAA. Crowell &amp;amp; Moring&amp;#39;s read: no civil safe harbor exists yet. This week also covers NIST&amp;#39;s NVD modernization RFI and OpenAI&amp;#39;s new offensive-security model. https://blog.disclose.io/policy-pulse-issue-29-week-of-august-16-2026/

  • View post

    Policy Pulse #30: Mandiant published the architecture behind its Agentic Vulnerability Discovery Harness. One engagement produced more than 100 true-positive critical vulnerabilities in two days; ten months of use produced 12 assigned CVEs. Human consultants still reproduce, deduplicate, and prepare every disclosure. Also: CISA added nine KEV entries in five days, and the DMCA Section 1201 renewal deadline is tomorrow. https://blog.disclose.io/policy-pulse-issue-30-week-of-august-23-2026/

  • View post

    Policy Pulse #32: Trail of Bits told GPT-5.6-Cyber to escape a stock QEMU/KVM VM. It escaped three times, the third on three zero-days plus a KVM fix nobody had flagged as a security issue. Disclosure status of the new bugs: &amp;quot;bug has been reported.&amp;quot; Also: Project Watershed 250, PaperCut zero-days in KEV, a judge voiding the Pentagon&amp;#39;s label on Anthropic, and IST&amp;#39;s Fragile Foundations Sprint. https://blog.disclose.io/policy-pulse-issue-32-week-of-september-1-20...

  • View post

    lookup.disclose.io runs inside the tools you already use, thin clients over one API: dio-lookup CLI (npm), Caido plugin, Burp and ZAP extensions, Chrome extension, Nmap NSE, Nuclei templates, a hosted MCP server in the MCP registry, and a JSON API with OpenAPI 3.1 and llms.txt. Since August 13 the Burp, ZAP, Caido, and Chrome plugins are route-aware: contacts grouped the way the site groups them, owner route first. https://github.com/disclose #VulnerabilityDisclosure #AppSec

  • View post

    Good disclosure policies often hide from automation: behind bot protection, or deep in a help-center sitemap. lookup.disclose.io follows the legal and help branches of a site&amp;#39;s sitemap, follows an owner-endorsed security portal on the same domain, and uses human-reviewed evidence when an official page blocks bots. Bunnings, TCL, and Motorola Solutions publish a policy. lookup reaches it. A current security.txt still ranks first. https://lookup.disclose.io #VulnerabilityDisclosure

  • View post

    &amp;quot;Complete&amp;quot; in lookup.disclose.io means one thing: a reporting route qualified to the actual owner of the asset. Publisher, repo host, parent company, disclosure platform: useful leads, none of them ownership. September correction: corporate context no longer implies disclosure scope. Outlook shows under Microsoft, but Microsoft&amp;#39;s route is first-party only where its current policy names the asset. https://lookup.disclose.io #AppSec

  • View post

    lookup.disclose.io runs inside Nmap. lookup-disclose.nse enriches each public scan target with its likely owner and responsible disclosure routes, straight from the lookup API: nmap -Pn -sn --script ./lookup-disclose.nse example.com It only talks to the lookup API, refuses private targets, caps requests across a scan, keeps output to bounded single lines, and keeps an optional API key out of the output. https://github.com/disclose/nmap-lookup #nmap #VulnerabilityDisclosure

  • View post

    lookup.disclose.io has a proper usage guide at /guide. Domains, URLs, IPv4/IPv6 addresses, CIDRs, emails, and ASNs are detected automatically. When a bare name could mean several things, a prefix removes the ambiguity: npm:, pypi:, crates:, gh:org/repo, app:, hw:, ext:, desktop:. Ideas and feature requests now have their own home at /feedback, kept separate from the per-result thumbs. https://lookup.disclose.io/guide #VulnerabilityDisclosure

  • View post

    security.txt results in lookup.disclose.io reflect what a site actually publishes. A TLS hostname edge case made valid files look missing on some major sites. lookup now reaches /.well-known/security.txt before the root fallback, tells an inaccessible probe apart from a real absence, and keeps expired files visible, labeled. Also: the CNA roster and Cloudflare origin ranges refresh weekly via a reviewed pull request. https://lookup.disclose.io #securitytxt

  • View post

    dnssecuritytxt census, Sep 7: 216 domains now publish a security contact in DNS, net +20 for the week. New since our last update: one.com and 19 more group.one brands (including WP Rocket, Imagify and Hostnet), @defcon&amp;#39;s own instance defcon.social, Concordia University of Edmonton, Skatteverket (the Swedish Tax Agency) and Steno (court reporting tech). One TXT record tells researchers where to report a vuln on your domain. Five minutes: https://dnssecuritytxt.org

  • View post

    When a site&amp;#39;s current, unexpired security.txt names its disclosure platform, that is the answer. lookup.disclose.io removes conflicting program links from older third-party catalogs while keeping every platform the site explicitly publishes. The suppression is deliberately narrow. A missing, expired, or custom-portal-only policy does not trigger it, so nothing disappears on a guess. https://lookup.disclose.io #BugBounty #VulnerabilityDisclosure

  • View post

    The reporting contact is the first thing you see in a lookup.disclose.io result. Attribution and the evidence chain sit one section down, one scroll away for anyone who wants to check the work. New this week: Historical Breadcrumbs. What the Common Crawl archive recorded for a domain, re-checked live, shown as a labeled &amp;quot;historical&amp;quot; lead that ranks below every current owner or operator route and above the coordinator backstop. https://lookup.disclose.io #VulnerabilityDisclo...

  • View post

    Who is lookup.disclose.io for? Anyone who has found something on an asset they don&amp;#39;t own and needs to reach whoever does. Researchers first, but &amp;quot;whose thing is this, and who do I tell?&amp;quot; is a question the whole defensive world asks. IR and threat intel. SOC, MDR and abuse desks. CERTs and coordinators. Product security. CNAs and bounty triage. Third-party risk. Anyone building agentic tooling: no language model inside, so it cannot invent a contact. https://lookup.di...

  • View post

    IP lookups in lookup.disclose.io got sharper. For a single address, the primary answer is the service operator actually using it: verified leaf-certificate subject, live redirects, and an IP-hosted security.txt come first. The registered network holder and the BGP origin ASN are fallbacks. RPKI is shown as routing context, never ownership. Route objects can no longer hijack attribution, and &amp;quot;production network&amp;quot; is no longer an organization. https://lookup.disclose.io #RDAP...

  • View post

    When a site publishes no security contact, lookup.disclose.io says so plainly: &amp;quot;No first-party reporting route found.&amp;quot; Constructed security@ ranks before abuse@, both labeled unverified, and the CERT route stays a real coordination path. Since September, fewer results end there: reviewed first-party policies and exact current scope turn coordinator-only results into owner routes where the evidence supports it. https://lookup.disclose.io #VulnerabilityDisclosure #CVD

  • View post

    Closes TODAY (Oct 9): DOE&amp;#39;s RFI on securing the US bulk-power system (EO 14421). Question B-7 asks how vulnerabilities reported by researchers are received, validated, remediated and communicated. Docket DOE-HQ-2026-1123. https://www.govinfo.gov/content/pkg/FR-2026-09-09/pdf/2026-18370.pdf RSAC 2027 Call for Submissions closes Oct 15, 11:59 PM PT: rsaconference.com #infosec #VulnerabilityDisclosure #CriticalInfrastructure #CyberPolicy #ICS #RSAC2027

  • View post

    lookup.disclose.io passed 45,000 lookups. Our dashboard says 143,690 requests. Most of it is MCP registry crawlers saying hello, so we are not calling that lookups. After basic bot filtering (user-agent based, and yes, bypassable) the number is 45,494. Across 2,393 real assets people looked up, we found a disclosure route 41% of the time. The rest fell back to abuse@ or a national CERT: most of the internet still has nowhere to send a vuln report. Go argue with the 59%. lookup.disclose.io

  • View post

    DOE wants to know how vulnerability reports for power systems are received, triaged and remediated. Comments close October 9. Policy Pulse #34 also covers the CRA reporting platform launch, AI evaluation incidents and the UK&#39;s withdrawn CMA review amendment. https://blog.disclose.io/policy-pulse-issue-34-week-of-september-14-2026/ #VulnerabilityDisclosure #Cybersecurity

  • View post

    Thanks everyone for your lookup.disclose.io feedback at #hackersummercamp this year, we got a TONNE of it and have made some pretty tasty updates over the weekend... 👀 • Owner-first routing: results lead with the owner&#39;s own reporting route • New evidence panel: see why we attributed an asset • Provenance + confidence on every contact • One clear recommended next step • Live progress instead of a spinner Free, no login: https://lookup.disclose.io

  • View post

    Ahead of Hacker Summer Camp we&#39;ve collected everything disclose.io makes on one page: the program directory, the security-contact lookup engine, safe-harbor terms, and the policy generators. All open source and free. We&#39;ll feature them one at a time from now to DEF CON. https://go.disclose.io/

  • View post

    Five governments (CISA, NSA, UK, NL, Japan) just published joint guidance on how to run a vulnerability disclosure program: safe harbor, security.txt, a CVE for every finding, no gag NDAs. Soft law, not statute, but now a citable five-government benchmark. This week&#39;s Policy Pulse: https://blog.disclose.io/policy-pulse-issue-25-week-of-july-18-2026/ #VulnerabilityDisclosure #CyberPolicy