Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

Individually ordinary public documents can, once read together, describe an organisation’s technology in useful detail. In a first-person account published on DEV Community, an organisation traced convincing phishing messages to details it had published for recruitment, marketing, conference talks and sales. The author’s question was “what a stranger can learn about us without doing anything unlawful.” The account does not prove that any single document caused a compromise or breach. Its value is in showing how separate pieces of public material add up.

What the author found in public material

The author describes four kinds of routine publication. Each one was approved for an ordinary business purpose, and each disclosed a different piece of the estate.

Material What it disclosed, according to the author Why it was published
Job advert for an infrastructure engineer The firewall vendor, backup product, virtualisation platform and operating-system version the organisation was standardising on Recruitment
Supplier case study The organisation’s name, a quoted colleague, the number of depots, and what had been replaced and when Supplier marketing
Conference slide Real hostnames A conference talk
Tender response sent to prospective customers An architecture diagram marked confidential, which also appeared in another organisation’s procurement portal Sales and procurement

The author’s point is that this combined view described the estate more accurately than the department’s internal documentation did. No single item needed to be a mistake for that to happen.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

What the account does and does not establish

The distinction matters for how you use the story internally.

  • It establishes: convincing phishing messages appeared, colleagues reported them, and the author then matched specific details in those messages to the public materials above.
  • It does not establish: that any one document caused the phishing messages, or that a breach occurred.
  • It is one first-person account. The author’s description of the response, including the number of pages in the first review, is anecdotal and should not be read as a survey or benchmark.

A defensible framing is that public information can make phishing more convincing and can reveal operational context when it is assembled. That framing is supported by the official guidance below. A claim that a job advert alone caused a compromise is not.

Why scattered details matter together

Attackers rarely need one dramatic disclosure. A job advert that names a firewall vendor, a case study that dates a platform replacement, and a diagram that shows how systems connect each narrow the field. Together they help a message look like it came from inside the organisation, using the right product names and the right vocabulary.

What the NCSC asset-management guidance says

The National Cyber Security Centre (NCSC) states in its asset-management guidance: “Publicly available information about your organisation and staff can be used to make phishing messages more convincing.” The same guidance says organisations should understand how their identity and data are used online and help staff manage their digital footprints, particularly senior, board and privileged staff. See NCSC, “10 Steps to Cyber Security: Asset management”.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

What the NCSC small-organisations guidance suggests reviewing

The NCSC’s guidance for small organisations, reviewed on 21 July 2026 (first published 9 April 2026), recommends reviewing what your website and social accounts reveal. It asks you to consider what visitors genuinely need to know and to remove content that is unnecessary for the business but could help criminals. Its examples include:

  • staff profiles or biographies
  • personal information in blog posts
  • details about third parties the business uses
  • outdated social connections

See NCSC, “Small organisations guide to cyber security: Spotting cyber attacks”.

How the NCSC defines open-source intelligence

The NCSC’s Cyber Adversary Simulation Scheme standard defines open-source intelligence (OSINT) as collecting and analysing public information to map an organisation’s digital footprint and identify vulnerabilities or attack vectors. Its examples include information about employees, technology stacks and physical locations. This describes how adversaries can combine public sources. It does not independently confirm the specific incident in the author’s account. See NCSC, “Cyber Adversary Simulation Scheme standard”.

What the organisation changed afterwards

According to the author, the organisation responded in five ways:

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
  • Adverts describe the work and skills but no longer name product versions.
  • Case studies require approval, and two suppliers agreed to remove theirs.
  • Conference talks receive review before delivery.
  • Tender responses no longer include diagrams.
  • The organisation began an annual review of what a stranger could lawfully learn from public sources. The author says the first review ran to nine pages. That is one organisation’s experience, not a general figure, and the annual cadence is the author’s practice rather than an NCSC requirement.

The author also frames the disclosures as ordinary work done in good faith. That framing is useful. The fix is a better review process, not a blame exercise aimed at the people who wrote the advert or gave the talk.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

How to run a public-content review

The steps below turn the author’s responses and the NCSC guidance into a repeatable process. Adjust the scope to your organisation’s size and publication volume.

  1. Inventory every public-facing item. Include job adverts, case studies, conference material, tender responses, website pages, social accounts and any supplier marketing that names you.
  2. Assign a named review owner for each category. Recruitment, marketing, sales and procurement often publish independently, so one owner per category prevents gaps.
  3. Ask what readers genuinely need. A candidate needs the role and skills, not the exact firmware version. A customer needs to understand your approach, not the hostnames in your network.
  4. Remove operational detail that serves no purpose. Check for product versions, hostnames, internal diagrams, named suppliers without approval, and dated replacement timelines.
  5. Require approval for supplier-produced material. Case studies and testimonials often bypass internal review. Make approval a condition of publication, and decide in advance what you will do if a supplier refuses to remove detail.
  6. Keep approvals workable. If review takes weeks, recruiters and sales teams will route around it. Agree turnaround times and a simple checklist.
  7. Review across documents, not just one at a time. Compare the advert, the case study, the talk and the tender against each other, because the risk sits in the combination.
  8. Set a review cadence and record the outcome. The annual cycle the author describes is a reasonable starting point. Choose a frequency that matches how often your published material changes.

Where external attack surface management fits

External attack surface management (EASM) is a related technical category, but it does not replace content review. The NCSC describes EASM as identifying, monitoring and reducing vulnerabilities in internet-accessible assets. Its buyer’s guide covers external discovery and analysis, and suggests considering discovery quality, integrations, access and reporting needs, and fit with your existing vulnerability-management practice. See NCSC, “External attack surface management (EASM) buyer’s guide”.

EASM can help you understand the internet-facing assets you run. It will not review whether a job advert names a firewall vendor, whether a conference slide shows real hostnames, or whether a tender diagram should be shared at all. Those are human review decisions, and they belong in the process above.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.