Operational change brief
New phishing assets, exposed infrastructure, active kits, takedown movement, KEV/CVE pressure and priority actions for fraud, SOC and brand-protection teams.
View weekly sampleWhat customers get
A managed reporting rail, not a one-off PDF.
Every report answers the questions regulated teams are actually asked: what changed, who is affected, how do we know, what action is open, and what can we show a board, auditor, insurer or regulator.
Liability-relevant record
Documented threat-landscape monitoring in place.
That sentence matters. The report pack gives leadership a repeatable record that monitoring existed before an incident, not after someone asked for proof.
Reporting cadence
The right level of detail for each room.
Security teams need fresh actions. Risk committees need trend and ownership. Boards need exposure, euros-at-risk framing and confidence that the organisation can prove its work.
Management review
Attack-surface movement, customer-harm trends, supplier exposure, campaign shifts, unresolved actions and evidence-backed progress against the previous month.
View monthly sampleBoard and NIS2 synthesis
Sector pressure, peer benchmark versus comparable Belgian institutions, trend arrows, board risk letter and regulator-safe evidence appendix.
View quarterly sampleProgramme evidence file
Year-over-year exposure, recurring actor and kit patterns, control maturity, reporting readiness, open risk and the management record for audits and renewals.
View annual sampleNIS2 responsibilities
Built around the file a regulated customer needs to maintain.
PhishNet helps customers document threat-landscape monitoring, incident context, risk-management evidence, supplier and attack-surface exposure, board communication and follow-up actions.
Threat landscapeSector pressure, relevant campaigns, ransomware claims, phishing waves and public-channel exposure.
Attack surfaceDomains, CT logs, TLS, ASNs, nameservers, apps, support journeys, suppliers, CVEs and takedown resurrection.
Evidence positionSource trail, confidence, timestamps, review state, evidence links and customer-safe excerpts.
Management actionRecommended actions, open owners, escalation paths, regulator language and board-ready risk sentences.
Towns, fleets and local-service exposure
NIS2 reporting for organisations with public-facing services everywhere.
Not every regulated customer looks like a bank. Towns, utilities, healthcare networks, transport operators and field-service groups need clear evidence for citizen-facing services, suppliers, portals, apps, payments and local infrastructure.
What this helps sell
A repeatable managed reporting service for groups of customers.
Use PhishNet to approach municipalities, intermunicipal organisations, sector associations, MSSPs and regulated service providers with a concrete file: what is exposed, what changed this week, how it was proven, what action is next and what management can safely circulate.
NIS2 readinessThreat-landscape monitoring, evidence trail, incident context, reporting milestones and board language.
Attack-surface managementDomains, suppliers, certificates, exposed services, impersonation journeys, ransomware and public-channel pressure.
Sector fleetsMunicipalities, hospitals, energy, water, transport, postal, digital infrastructure, finance and B2B research/industrial examples can now be generated as passive watch fleets.
Commercial wedgeOne customer-specific brief opens the conversation; recurring packs create the managed service.
Healthcare report example
Hospital and patient-service exposure brief
Use for hospital networks, patient portals, eHealth journeys and NIS2 evidence conversations.
Open PDF Municipal report example Brief for towns, cities and citizen servicesUse as the first-call proof piece for municipalities and public-sector service owners.
Open PDF Fleet report example Exposure sheet for distributed operationsUse for mobility, logistics, utilities, field teams, payment journeys and partner infrastructure.
Open PDFSample library
Open the samples after the context is clear.
The PDFs are formatted for decision makers. The HTML previews are useful for review, accessibility checks and faster circulation before generating customer-specific packs.
Flagship exposure brief
Open PDF
External Threat Exposure Brief
A customer-facing brief for a named brand: exposure, peer comparison, operator pattern, evidence chain and recommended action.
HTML preview
Preview
Flagship brief web proof
The same flagship structure as a web-readable sample for review and iteration before customer delivery.
Weekly
Open PDF
Operational change brief
Short, action-oriented reporting for teams that need to move quickly without waiting for the quarterly cycle.
Monthly
Open PDF
Management review
A management layer for trend, owner, unresolved action and attack-surface evolution.
Quarterly
Open PDF
Board and regulator synthesis
The board-readable synthesis with peer benchmark, trend arrow, evidence readiness and NIS2/DORA reuse.
Annual
Open PDF
Programme evidence file
The annual record for audit, renewal, risk committee review and continuous-improvement planning.
Healthcare
Open PDF
Hospital and patient-service brief
A NIS2-oriented exposure brief for hospitals, patient portals, eHealth identity journeys and healthcare networks.
HTML preview
Preview
Healthcare brief web proof
The hospital sample as a web-readable preview for review, outreach and customer-specific pack iteration.
Municipal
Open PDF
Town and citizen-service brief
A NIS2-oriented exposure brief for towns, local governments, citizen portals and public-service suppliers.
Fleet
Open PDF
Distributed operations exposure sheet
A concise management sheet for fleet, logistics, mobility, utility and field-service attack-surface risk.
How it is delivered
Customer-specific, evidence-backed, safe to circulate.
A report pack is generated for a customer, brand, sector or cohort. Raw sensitive material stays restricted; the customer view exposes defanged indicators, hashes, excerpts, provenance, confidence, timestamps, evidence links and recommended actions.