Article

The risks of following AI-generated security advice

AI security advice is sound in general and risky in particular: it cannot see your configuration, test the result or answer for a failed control. Learn from it; have changes checked by someone who sees your environment.

The short answer

In security, a plausible, slightly wrong answer does the most damage and is hardest to notice. An assistant can explain multi-factor or email authentication well, but cannot see your tenant, know which policies apply, test a change or warn you when a control stops working. Failures stay silent until an attacker finds them. Use AI to understand and draft; have live changes reviewed, tested and recorded by someone accountable.

Why security is different from other IT questions

A broken spreadsheet formula shows at once; security failures do not.

Failures are invisible

A misconfigured policy still shows a green tick until it matters.

Changes interact

A new rule can override, exclude or duplicate one the chat cannot see.

Attackers outpace training data

Advice sound when a model was trained may now be incomplete.

Attackers use AI too

Convincing phishing at scale, in fluent English and increasingly local languages and styles.

Mistakes cost more

Ransomware, email compromise, breaches: recovery costs, downtime, possible NDPC notice within 72 hours under the NDPA 2023.

Because attackers use AI, strong authentication, email filtering, patching and staff awareness matter more, not less. AI can explain each control; implementing and maintaining them consistently is the hard part.

The controls frameworks expect

Established frameworks such as NIST's Cybersecurity Framework put those controls at the core, alongside an incident response plan, backups, access control and securing outsourced IT services.

Six ways AI security advice goes wrong

Failure modeExampleWhat it can cost
Too-broad exclusions"Exclude this folder from antivirus" to speed up a scanA permanent blind spot for malware
Weakening to fix frictionDisabling a sign-in prompt, legacy protocol block or security default after complaintsRemoves a control attackers look for
Wrong scopeA one-mailbox script run on all, or a firewall rule opening "any"Wide exposure from one line
Outdated methodSteps for a retired admin centre, protocol or settingHalf-applied change, false confidence
Incomplete email authenticationSPF or DMARC missing a sending service, or jumping straight to rejectLost legitimate email, or spoofing still possible
No monitoring stepA control switched on, alerts uncheckedDetection without response

None needs the AI to be absurd: each is a reasonable answer missing context the assistant did not have.

The privacy trap

Pasting the real thing (a sign-in log, email header, firewall configuration, flagged users) gets the most precise answer, and puts sensitive data in a public tool that may store or process it. Most are hosted outside Nigeria, which can bring in the NDPA's rules on transfers abroad (NDPC); anonymised or de-identified information is the safer habit.

Before pasting, remove names, email addresses, phone numbers, IP addresses, account identifiers and, above all, passwords, keys and tokens. If you cannot redact it, do not paste it.

Rather talk it through? If you have already changed security settings based on AI advice, or are about to, we can review them against your environment and confirm nothing important was weakened. Talk to a Promatics specialist

How to check security advice before acting

  • I can explain in one sentence what this change does and why
  • The advice matches the vendor's current official documentation
  • I know which existing policies or rules this interacts with
  • Scoped to one user, group or address, not "all" or "any"
  • No new exclusions, disabled protections or logging turned off
  • Tested on a pilot user or group first
  • I know how to undo it and recorded the previous setting
  • Someone will review the related alerts or reports next week
  • No personal data or credentials pasted into the AI tool

Cannot tick most? Stop and get a second opinion.

When to bring in help

AI is a fine companion for awareness: understanding phishing, drafting a password policy, learning what a control is for. Bring in a professional when:

  • Identity, email, firewall, endpoint or backup changes
  • Alerts, suspicious sign-ins or incidents
  • Health, financial or sensitive personal data
  • Insurer, auditor, regulator or client wants evidence
  • Nobody would notice a silent failure

A cybersecurity partner brings what an assistant lacks: your configuration, risks, obligations under Nigerian data protection law and responsibility for the result. A security assessment is the usual first step.

AI tools carry their own risks (confidential data pasted into chatbots, assistants manipulated by hidden instructions): AI governance and security covers policies, discovery of unapproved AI use and security testing of AI applications.

Sources and further reading

Product capabilities and guidance change. These are the primary sources this article relies on, checked on the review date above.

  1. Cybersecurity Framework, National Institute of Standards and Technology
  2. Nigeria Data Protection Act 2023 and guidance on personal data, Nigeria Data Protection Commission
  3. Nigeria's computer emergency response team (ngCERT), Nigerian Communications Commission, ngCERT

This article is general information, not legal, accounting or security advice for your specific situation. Examples are hypothetical unless stated otherwise.

Talk to Promatics

Check your security changes before they become gaps

Security settings are easy to change and hard to verify alone. We review past or planned changes and tell you plainly where the risks are.

  • Review of your real controls, not a generic checklist
  • Changes tested and documented, with a rollback plan
  • Nigerian data protection context (the NDPA) built into the advice