On this page (6 sections)
The UK's National Cyber Security Centre (NCSC) has published a blog post about how industry, the NCSC and the Financial Conduct Authority (FCA) teamed up to clear away an obstacle to sharing cyber incident information. According to the NCSC, the obstacle was not reluctance. Publicly listed organisations were unsure whether sharing details mid-incident could clash with market-abuse rules.
This is policy and guidance news, not a vulnerability or an active attack. It matters most to listed companies and the suppliers who help them respond, but the lesson applies to any website owner or agency: decide before an incident who may share what, and with whom. All facts below come from the NCSC blog post, currently the only source we have for this story.
What the NCSC says happened
The NCSC points to high-profile incidents in the retail sector as evidence that quick information sharing is valuable, both inside a sector and across others. Many organisations rely on the same technologies, suppliers and digital supply chains, so a problem at one can signal similar exposure elsewhere.
For publicly listed organisations, the NCSC says, a cyber incident can also raise questions about market-sensitive (inside) information. Some were unclear on when they could pass details to the NCSC or to trusted information-sharing communities and still comply with the UK Market Abuse Regulation (MAR), which the FCA oversees. The NCSC frames the problem as uncertainty over how to share lawfully, rather than any unwillingness to share.
What the FCA guidance covers
The NCSC describes the result as FCA guidance on disclosing inside information relating to cyber incidents. It helps organisations work out their disclosure obligations while responding to an incident. It also covers when they may share information with government departments, law enforcement, regulators and trusted information-sharing communities.
The NCSC states that passing incident information to it, as part of its work to protect UK critical systems and online services and to support incident response, may be compatible with an organisation's regulatory obligations. The stated reason is that such sharing may fit with acting in the normal exercise of employment, profession or duties. The guidance also recognises NCSC-led communities where sharing can help others prevent or reduce the impact of threats.
Who is realistically affected
- Publicly listed organisations, which are the ones the NCSC says faced MAR-related hesitation.
- Security, legal and communications teams at those organisations, who decide what is disclosed and when.
- Agencies, hosting providers and other suppliers that respond to incidents for listed clients and may be asked to share indicators or timelines.
- Smaller site owners who are not listed. MAR is not their concern, but they can still gain from the wider sharing the NCSC wants to encourage.
The material we reviewed does not give the exact wording of the FCA guidance, say what specific information must be shared, or explain how any given incident should be handled, so we do not speculate on those points. Read the FCA guidance directly and take legal advice for your own situation.
What to do now
Whether or not your organisation is listed, the practical step is to settle the sharing question while things are calm.
- If you are a listed organisation, ask legal counsel to read the FCA guidance on disclosing inside information relating to cyber incidents and map it to your own disclosure process.
- Write down who can authorise sharing incident details with the NCSC, law enforcement, regulators or a trusted information-sharing community.
- Add an information-sharing step to your incident response plan, with a named owner and a backup.
- Agree with suppliers and agencies in advance what they may share about your incident and who must approve it.
- Keep a factual, timestamped incident log so that anything you share is accurate and consistent.
- Find out whether your sector has a trusted information-sharing community and how membership works.
- Review the plan after every incident or exercise and update it.
Detection and further reading
Sharing only helps if you notice the incident first. For website owners that means regular checks for unexpected file, script or configuration changes, and a clear path from detection to escalation. Our guide to checking whether a website is hacked is a good starting point, and the free malware scanner gives a quick outside-in look at a public site. More security news and analysis is on the Webforta blog.
What is still unclear
The NCSC post is a single primary source, and no other independent publisher has covered the story so far. The excerpt we reviewed describes the guidance at a high level. It does not give the FCA guidance's publication date or full text, or any figures on how often organisations were deterred from sharing. Because the NCSC calls the outcome a short-term solution, the discussion may continue. We will update this article if more details are published.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
