By NHI Mgmt Group Editorial TeamPublished 2025-10-22Domain: Best PracticesSource: JumpCloud

TL;DR: Cyber Security Awareness Month is often overwhelmed by vendor noise, but JumpCloud argues MSPs should use it to create one clear, client-facing security conversation, focusing on phishing, MFA, or password hygiene rather than broad awareness campaigns. The practical lesson is that trust-building beats feature-heavy messaging when clients need simple, actionable security guidance.


At a glance

What this is: This is a practitioner-focused argument for making Cyber Security Awareness Month useful by narrowing the message, starting conversations, and giving clients one concrete security action to take.

Why it matters: It matters because MSPs, IAM leads, and security teams often lose impact when awareness campaigns become broad, noisy, and disconnected from the controls clients can actually adopt.

👉 Read JumpCloud's guidance on making Cyber Security Awareness Month useful for MSPs


Context

Cyber security awareness month works best when it turns attention into a single, understandable security action. For MSPs and the teams they advise, the problem is not a lack of awareness content. The problem is that broad campaigns often overwhelm people before they change behaviour, which means the message rarely reaches control adoption.

That gap matters to IAM programmes because awareness is only useful when it leads to stronger identity controls, better authentication habits, or clearer client conversations. In practice, the most effective month-long campaign is usually the one that narrows scope instead of expanding it.


Key questions

Q: How should MSPs make cyber security awareness month more effective?

A: They should narrow the campaign to one practical control outcome, then reinforce it through short conversations, simple examples, and repeatable client-ready material. The goal is not to produce more content. It is to move one behaviour, such as MFA adoption or phishing resistance, into regular client practice.

Q: Why do broad awareness campaigns often fail to change security behaviour?

A: They fail because they ask busy people to absorb too many messages at once. If the audience cannot quickly see what action matters, the campaign becomes background noise. Security behaviour changes when the message is narrow, relevant, and tied to one control the client can actually adopt.

Q: When should teams use stories instead of statistics in security awareness?

A: Use stories when the goal is behaviour change, not benchmarking. A short example of a fake invoice, reused password, or missed MFA step is easier for non-specialists to remember and discuss. Stories make the risk feel concrete, which helps people translate awareness into action.

Q: Who is responsible for turning awareness into better security outcomes?

A: Responsibility sits with the security partner or MSP that understands the client’s environment and can translate risk into a specific action. Awareness only becomes useful when it supports a real control decision. The partner’s job is to make the advice simple enough that the client can use it immediately.


Technical breakdown

Why broad awareness campaigns lose operational impact

Large awareness campaigns often fail because they compete with work, not because the security advice is wrong. If the audience is busy, overloaded, or non-specialist, long guidance documents and generic threat lists rarely convert into action. Behaviour changes when the message is simple, repeated, and tied to one visible control or one easy habit. For MSPs, the operational question is not how much content can be delivered, but whether the client can absorb and act on it.

Practical implication: narrow the month to one control outcome so delivery effort maps to measurable behaviour change.

Why phishing, MFA, and password hygiene are still the highest-leverage themes

Phishing, MFA, and password management remain practical because they sit close to everyday identity risk. Phishing tests user judgment, MFA reduces the value of stolen credentials, and password managers lower the chance that people reuse weak secrets across systems. These are not abstract hygiene topics. They are the simplest identity controls that clients can understand, adopt, and reinforce without needing a major programme redesign.

Practical implication: choose the control theme that your clients can implement this month, not the one that sounds most comprehensive.

Why conversation beats broadcast messaging in client security work

Awareness improves when the audience can respond, ask questions, and hear examples that match their own environment. A short informal session does more than a polished campaign because it creates context and lowers resistance. For MSPs, the value is not in producing more materials. It is in translating security guidance into something that feels relevant to the client’s reality and decision-making pace.

Practical implication: replace one-way campaign blasts with short, interactive sessions that let clients connect guidance to their own risk.


NHI Mgmt Group analysis

Broad awareness campaigns fail when they try to do too much at once. Security awareness is most effective when it drives one specific behaviour change instead of trying to fix every user risk in a single month. That is a governance lesson as much as a communication lesson, because overloaded messaging reduces attention, action, and follow-through. The practitioner conclusion is to treat awareness as a control-enablement exercise, not a content calendar.

The strongest awareness programmes translate identity risk into one simple client action. Phishing, MFA, and password hygiene remain useful themes because they are close to identity behaviour and easy to explain without specialist language. That matters for MSPs and IAM teams alike, because simple messages are more likely to become actual policy, training, or authentication changes. The practitioner conclusion is to anchor awareness to the identity control the client can realistically adopt.

Client trust is built through relevance, not volume. The post’s central message is that a good security partner helps people make one useful decision, not ten disconnected ones. That principle aligns with identity governance across human and non-human programmes, where the most effective controls are the ones users can understand and sustain. The practitioner conclusion is to favour precision over spectacle.

Awareness works best when it supports the broader identity programme rather than sitting beside it. A one-month campaign should reinforce MFA adoption, password manager use, and phishing resilience in ways that can be measured after the campaign ends. That keeps the effort tied to operational outcomes instead of marketing activity. The practitioner conclusion is to make awareness part of the control lifecycle, not a seasonal event.

From our research:

  • 70% of organisations grant AI systems more access than they would give a human employee performing the exact same job, according to The 2026 Infrastructure Identity Survey.
  • Only 13% of organisations feel extremely prepared for the reality of agentic AI despite the majority racing toward autonomous adoption, which shows how quickly governance can lag behind adoption.
  • That same survey shows 69% of security leaders agree identity management must fundamentally shift to address agentic AI systems, a signal to revisit controls before autonomous use expands further.

What this signals

Identity programmes should expect seasonal awareness efforts to be judged by control adoption, not content output. If the campaign does not produce a clearer MFA, password, or phishing outcome, it will not hold attention for long. The strongest signal is whether the message changes behaviour after the month ends.

With 70% of organisations granting AI systems more access than human employees in the same role, per the 2026 Infrastructure Identity Survey, the governance challenge is no longer limited to people. Teams should plan awareness and identity messaging that covers human users, workload access, and emerging AI-driven access patterns together.

Client trust will increasingly depend on translation, not volume. MSPs and identity teams that can turn risk into one clear action will outperform teams that only add more guidance. The practical signal is that better communication is becoming part of identity governance discipline.


For practitioners

  • Focus the campaign on one control outcome Pick a single high-impact theme such as phishing, MFA adoption, or password managers, then build every message around that one change so clients know exactly what to do.
  • Run short client conversations instead of email blasts Offer a 15-minute informal session where clients can ask questions and hear examples tied to their own environment, which makes the guidance easier to absorb and act on.
  • Replace statistics with relatable scenarios Use a simple story about a fake invoice, a reused password, or a missed MFA step so the client can connect the risk to a real behaviour rather than a generic warning.
  • Use reusable client-ready material Share lightweight, customizable content that an MSP can brand and send directly, because ready-to-use material is more likely to become an actual conversation.

Key takeaways

  • Cyber Security Awareness Month is most useful when it narrows attention to one control outcome that clients can actually adopt.
  • Simple themes like phishing, MFA, and password hygiene still work because they are concrete enough to drive behaviour, not just awareness.
  • MSPs and identity teams strengthen trust when they replace broad vendor-style messaging with short, relevant, client-specific conversations.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST CSF 2.0, NIST SP 800-63 and NIST Zero Trust (SP 800-207) set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST CSF 2.0PR.AT-1Awareness training is the core control surface discussed in the article.
NIST SP 800-63MFA and password practices are central identity topics in the post.
NIST Zero Trust (SP 800-207)PR.AC-4The post’s focus on reducing exposure through MFA aligns with continuous access verification.

Tie awareness content to one measurable behaviour and verify the outcome after the campaign.


Key terms

  • Security awareness campaign: A planned effort to change user behaviour through repeated security messaging, examples, and reminders. In practice, the campaign only works when it drives a specific action such as MFA adoption, phishing resistance, or stronger password habits, rather than trying to teach every security topic at once.
  • Phishing awareness: Training that helps people recognise and respond to deceptive messages designed to steal credentials or trigger unsafe action. The goal is not perfect detection. It is reducing the chance that a user will click, reply, or approve something that should have been challenged.
  • Client-ready content: Security material that a practitioner can reuse, customise, and deliver without heavy rewriting. For MSPs and identity teams, this matters because usable content is more likely to start a conversation and influence behaviour than polished material that never leaves the inbox.

Deepen your knowledge

NHI governance, agentic AI identity, and machine identity security are core topics in our NHI Foundation Level course, the industry's only accredited NHI security programme. If you are responsible for identity strategy, access control, or security governance, it is worth exploring.

This post draws on content published by JumpCloud: an anti-blog post on making Cyber Security Awareness Month genuinely useful. Read the original.

NHIMG Editorial Note
Published by the NHIMG editorial team on 2025-10-22.
NHI Mgmt Group — the independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org