Image without description
  • Jacco Meijer
  • |
  • Oct 22, 2025

What cyber security mistakes do organizations still make?

A brief check on how the AI response for this question compares to real life experience.

Cyber security mistakes

Executives are often very aware that cyber security matters, but in practice many still make recurring mistakes that significantly increase the risk of the organization.

The next AI prompt generates a breakdown of key mistakes executives tend to make. It gives the answer to why the mistakes are important and what actions can help remedy them.

Prompt

What cyber security mistakes do executives still make?

Try the prompt and see how the generated response differs. This post analyzes the october 2025 response below by comparing it to the authors real life experience.

Response

This is the index of the generated response. The details of the original response are left out.

  1. Treating cyber security as 'just IT' or a compliance exercise
  2. Under‑investing in resiliency and assuming prevention is enough
  3. Overlooking the human element and poor organizational culture
  4. Neglecting third‑party / supply chain and data visibility risks
  5. Failing to take accountability and failing to act promptly after an incident
  6. Thinking 'we’re too small / we’ll never be targeted'

– Malcolm Marshall, Global Head of Cyber Security at KPMG

"Collectively we sleepwalked into a position of vulnerability and failed to learn lessons of embedding security into products right out of the gate."


Treating cyber security as 'just IT' or a compliance exercise

In reality, this one is very true. Phrases like “it’s just data” or “it’s just IT” are still commonly heard. Another frequent remark is “just make sure we pass the audit”. These expressions reveal a mindset where cyber security is either reduced to a technical concern or treated as a compliance checkbox.

As a result, the practical measures that truly reduce risk and enhance operational resilience are often underfunded. Because, after all, “it’s just data” and “it’s just IT”. Meanwhile compliancy, often focused only on passing audits, tend to receive much more attention and resources.


Under‑investing in resiliency and assuming prevention is enough

In reality, this one is also very visible. Many organizations still focus on preventive controls like firewalls, access management and other defenses but completely overlook resilience. Key capabilities like threat detection, incident response and recovery planning often get very little attention.

Prevention these days is not enough anymore. Without a tested response and recovery strategy, evolving cyber threats and human error can lead to severe breach impacts.


Overlooking the human element and poor organizational culture

Reality shows that in recent years, larger organizations have shown some improvement, but many still operate under the false belief that employees inherently understand secure behavior or that small companies aren't targets. This leads to outdated or minimal training.

A common approach for a single year is a mandatory slide deck with four follow up questions and two phishing simulations.

Human error remains a top cause of breaches, from clicking malicious links to badly configured systems. Without a strong security culture and continuous awareness efforts, even the best technical defenses can be easily compromised.


Neglecting third‑party / supply chain and data visibility risks

In reality, managing third-party and supply chain risks is still often neglected. Organizations focus on securing internal systems, while external dependencies such as vendors, external libraries and cloud services receive less attention.

One weak link can break the chain

The aspects of supply chain data get some attention today, but this is also a major concern. There's a general lack of awareness on what data exists, where it is and who can access it.

You can’t secure what you can’t see


Failing to take accountability and failing to act promptly after an incident

In reality, these incidents are rarely visible to the public due to confidentiality. What does become apparent however, is how the incident is communicated. Often downplayed to avoid accountability.


Thinking - we’re too small / we’ll never be targeted

Size doesn’t equal safety.

In reality, smaller organizations are often more aware of their risks but lack the resources to properly defend against them. Larger organizations tend to invest more in cyber security, but this can create a false sense of security.

Cyber threats don’t discriminate by size.

Attackers often target smaller businesses because they’re seen as easier to compromise. They generally have a weaker defense but more valuable data.

Conclusion

The AI generated response highlights several major cyber security concerns that align closely with the authors real world experience.

While the original AI response captures the general issues accurately, the details provided in this post are more specific which offers a clearer picture of the current landscape.

Ironically, AI fails to mention itself as a potential risk. While AI is arguably one of the most significant cyber security threats facing organizations today.


Other posts

Image without description
  • Jacco Meijer
  • |
  • Oct 19, 2025

Risk analysis for software development

By systematically identifying and assessing potential risks, teams can reduce uncertainty and prevent costly issues.

Image without description
  • Jacco Meijer
  • |
  • Oct 18, 2025

Security controls for software development

Exploring how security controls protect and improve every stage of the DevSecOps workflow.

Image without description
  • Jacco Meijer
  • |
  • Oct 17, 2025

Software development security

On risk assessments, security controls and the complexity of securing the Software Development Lifecycle (SDLC)

Image without description
  • Jacco Meijer
  • |
  • Oct 14, 2025

Canonical controls with Enterprise Risk and Security Management

How to use the SCF canonical control objectives with ERSM in Archimate

Image without description
  • Jacco Meijer
  • |
  • Oct 7, 2025

ISO 27000, ISA 62443, NIS2, BIO, NIST CSF and NIST SP 800-53

How to align the steadily increasing number of cyber security frameworks, standards and regulations?

Image without description
  • Jacco Meijer
  • |
  • Aug 15, 2025

Asset security

Information asset identification and classification from a security perspective

Image without description
  • Jacco Meijer
  • |
  • Aug 8, 2025

Data security

Data identification, data roles and data classification from a security perspective

Image without description
  • Jacco Meijer
  • |
  • Jul 25, 2025

Threat modeling, security frameworks and Enterprise Architecture

Combining ISO 27001, NIST CSF and threat modeling with Enterprise Architecture strengthens all elements

Image without description
  • Jacco Meijer
  • |
  • Jul 18, 2025

Threat modeling as part of a risk framework

Threat modeling in the context of ISO 27001 and NIST CSF

Image without description
  • Jacco Meijer
  • |
  • Jul 11, 2025

Cyber security risk frameworks

Managing cyber security risk with ISO 27001 and NIST CSF

Image without description
  • Jacco Meijer
  • |
  • Jun 27, 2025

NIST CSF Tiers for cyber security risk governance and management

NIST CSF 2.0 contains useful tiers for Capability Maturity Modeling in Enterprise Architecture

Image without description
  • Jacco Meijer
  • |
  • Jun 20, 2025

Archimate risk assessment elements

A few simple specializations for working with risk assessments in Archimate

Image without description
  • Jacco Meijer
  • |
  • Jun 13, 2025

Security principles in Enterprise Architecture

Adding security principles to Enterprise Architecture for NIST CSF and ISO 27001

Image without description
  • Jacco Meijer
  • |
  • Jun 6, 2025

Combining ISO 27001 and NIST CSF

How to use ISO 27001 and NIST Cyber Security Framework together

Image without description
  • Jacco Meijer
  • |
  • May 1, 2025

CISSP certification and Enterprise Architecture

How do the CISSP certification domains relate to Enterprise Architecture and the ArchiMate layers?

Image without description
  • Jacco Meijer
  • |
  • Apr 23, 2025

Architect roles in the ArchiMate context

An ArchiMate model that maps architect roles to the ArchiMate framework layers.

Image without description
  • Jacco Meijer
  • |
  • Mar 18, 2025

Visualizing IT Architecture in three languages, UML, C4 and ArchiMate

What are the differences and what are these languages most used for?

Image without description
  • Jacco Meijer
  • |
  • Feb 18, 2025

OAuth 2.0 and OpenID Connect Sequence Diagrams

Technical specs can be hard to read. While still highly technical, the UML Sequence Diagrams provided in this blog are a lot easier to understand.

Image without description
  • Jacco Meijer
  • |
  • Jan 9, 2025

OWASP and CISSP

OWASP recommendations from the independent information security certification CISSP.

Image without description
  • Jacco Meijer
  • |
  • Mar 21, 2024

UI Library with MDX documentation

Using the simple Render JSX plugin for Esbuild this post shows how to setup a simple UI library.

Image without description
  • Jacco Meijer
  • |
  • Mar 20, 2024

Render JSX plugin for Esbuild

Transform Esbuild generated JSX bundles to HTML pages.

Image without description
  • Jacco Meijer
  • |
  • Mar 19, 2024

Esbuild as a static site generator for MDX

Static site generators gain popularity. This blog is about using Esbuild as a static site generator for MDX.

Image without description
  • Jacco Meijer
  • |
  • Mar 18, 2024

11ty and Github pages

Simplifying the Contentful-Gatsby-Netlfy trio.

Image without description
  • Jacco Meijer
  • |
  • Jun 30, 2022

NPM7 and @npmcli/arborist

@npmcli/arborist is a powerful library that handles the new NPM 7 workspaces. This blog is about a simple make tool that uses the library.

Image without description
  • Jacco Meijer
  • |
  • May 12, 2022

Comparing React app, Nextjs and Gatsby

A new React project starts with a React toolchain. Main tools in the chains are SSR, React server components and GraphQL.

Image without description
  • Jacco Meijer
  • |
  • May 10, 2022

Versioning strategy for NPM modules

It is important to be able to bump the version of a NPM package without side effects.

Image without description
  • Jacco Meijer
  • |
  • Apr 12, 2022

React component themes and CSS variables

Creating React components with flexible themes by using CSS variables.

Image without description
  • Jacco Meijer
  • |
  • Mar 21, 2022

Content modeling with variants

The efficiency of a variant field in a content model.

Image without description
  • Jacco Meijer
  • |
  • Mar 12, 2022

Documentation

Documenting a software project is challenging. Here's a few simple guidelines that help a team writing clear documentation.

Image without description
  • Jacco Meijer
  • |
  • Mar 11, 2022

Javascript history

In 1986 David Ungar and Randall B. Smith developed Self at Xerox PARC. Inspired by Java, Scheme and Self Brendan Eich created Javascript in 1995.

Image without description
  • Jacco Meijer
  • |
  • Mar 10, 2022

On Javascript transpilers, bundlers and modules

There's Javascript transpilers, modules, bundles and bundlers. This is a brief overview of all of these.

Image without description
  • Jacco Meijer
  • |
  • Feb 11, 2022

Agile Scrum

The Agile Scrum framework is flexible enough to be used in many different ways. Here's one way of working.

Image without description
  • Jacco Meijer
  • |
  • Jan 20, 2022

What happened to Wheelroom?

Founded in 2018. Started to fly in 2020 and abandoned in 2021. What happened?

Image without description
  • Jacco Meijer
  • |
  • Jan 19, 2022

Contentful, Netlify and Gatsby four years later

What did we learn from using Contentful for four years?

Image without description
  • Jacco Meijer
  • |
  • Jan 18, 2022

Typescript interface for React UI components

How to define an interface for React UI components that prevents breaking changes.

Image without description
  • Jacco Meijer
  • |
  • Jan 17, 2022

Naming React components

What's in a name? A clear naming strategy helps developers communicate. Most devs rather spend time writing component code than wasting time on a good component name.