Joe Decker writes about cybersecurity, with a focus on exposure management, proactive security, and using context to prioritize risk. His posts discuss asset visibility, vulnerabilities, threat intelligence, and the role and limits of AI in security decisions.
More findings are not the same as more understanding · The risk that costs you is often the one nobody owns · Use AI at scale, but keep a person at the final decision
Joe Decker writes about cybersecurity, especially exposure management: how security teams can make sense of assets, vulnerabilities, and other signals to decide what needs attention.
In these posts, they explain security through familiar references, from the end of AOL dial-up to sailing history and a Southern Gothic novel.
Their posts focus on proactive preparation, overlooked risks, and the limits of treating an AI-generated account or risk score as a final answer.
Decker’s distinctive approach connects technical security problems to concrete ideas, then brings the explanation back to a practical decision.
In one post, a film-editing analogy shows why a large volume of findings is not the same as understanding: teams need context to judge which exposures could lead to meaningful consequences.
In another, the overlooked danger in a horror novel becomes a way to discuss forgotten assets, unclear ownership, and risks people have learned to ignore.
Historical and technology references make proactive security and outdated visibility easier to grasp.
Across these examples, they argue that organizations should prepare and prioritize, treating evidence and AI-assisted analysis as inputs to human judgment—not substitutes for it.
Joe Decker’s posts circle one argument: security teams are not short of findings; they’re short of context.
Read more
Exposure management, in this telling, means deciding which exposures form a plausible path to something important, who owns them, and what to fix first.
Three further priorities follow: anticipate incidents rather than react to them, retire legacy systems and habits before they cause exposure, and treat AI as an assistant to correlation and prioritization, not a final verdict.
Decker makes these points through extended comparisons to history, novels, film, and technology nostalgia.
More findings are not the same as more understanding
Joe Decker argues that scanners, identity platforms, and cloud, application, and infrastructure tools produce more data than a security team can reasonably process.
Read more
Exposure management is not about making a longer list; it’s about adding context: which exposures form a plausible path to something important, what identities, data, and business processes are involved, which controls stand between an exposure and a real consequence, and what to fix first.
The comparison is filmmaking.
A camera can capture thousands of details, but editing, framing, and context turn them into a story.
Joe Decker applies the same logic to security tooling: polished output is not the same as truth, and a risk score is an interpretation, not a verdict.
The risk that costs you is often the one nobody owns
In Joe Decker’s framing, visibility comes first, and the dangerous exposures are often the quiet ones, not the loudest vulnerability or newest CVE.
Read more
They persist because visibility is partial, ownership is unclear, and people have grown comfortable with the way things are. Good exposure management means understanding what is actually in the environment, what can be exploited, and what matters to the organization.
Joe Decker offers a deliberately mundane image — a "Windows 98 box in a parking lot" — alongside other overlooked items: the inherited exception justified by "we've always done it this way," the misconfiguration everyone assumes someone else owns, and the third-party exposure that has been sitting quietly. The illustration comes from Michael McDowell’s Southern Gothic horror novel, "The Elementals," where the scariest element is not the obvious threat but the thing everyone has learned to live with.
Use AI at scale, but keep a person at the final decision
This is Joe Decker’s clearest position on AI, and it carries a tension: AI can correlate signals, uncover patterns, and challenge assumptions at a scale humans cannot, but it can also construct a convincing narrative from incomplete or poorly framed evidence.
Read more
The argument is not to avoid AI but to treat its output as an input to judgment. Their stated sequence puts evidence before opinion, context before score, and human accountability at the final cut.
The specific caution: a risk score is an interpretation, not a verdict. Joe Decker closes the post by making the priority explicit: the job is not to eliminate every ambiguity but to make better decisions in the presence of ambiguity.
Prepare before the incident, because reacting is already too late
Joe Decker treats proactive security as a leadership issue as much as a tooling one.
Read more
The components named are threat intelligence, continuous monitoring, readiness to act, asset discovery, and vulnerability management, all framed as preparation in advance rather than a response once conditions worsen. Leaders who prepare their teams and infrastructure are described as the ones who endure.
Two historical figures carry the argument.
Ernest Shackleton did not wait until the ice closed in to think about survival but stocked, planned, and led with foresight; Horatio Nelson's victories came from relentless drilling, anticipation, and positioning before a shot was fired.
A separate post maps an Age of Sail metaphor onto modern practice: charting unknown territory becomes asset discovery, inspecting a ship's hull becomes vulnerability management, and reading the winds becomes threat intelligence.
Retire outdated systems before they retire themselves
A recurring priority is that legacy technology and inherited habits are themselves a form of exposure.
Read more
Joe Decker’s point is that organizations often know a faster, safer approach exists yet keep the old one running, leaving visibility and response capabilities behind. The recommendation is to upgrade visibility, processes, and response rather than tolerate what is merely familiar.
The hook is AOL's dial-up service ending after 40 years.
Joe Decker says cybersecurity can feel like dial-up sometimes, with old systems hanging on while risks sneak in.
They close by saying that in cybersecurity, "You've Got Mail" should not be the warning sign.
This is the clearest statement of how Joe Decker defines exposure management and where they place AI in the decision process.
Read more
Start here to understand the difference they draw between finding more issues and understanding the ones that matter.
Joe Decker compares filmmaking to security work.
A camera can capture thousands of details, but editing, framing, and context turn them into a story.
A scanner can find thousands of vulnerabilities, an identity platform can surface thousands of relationships, and cloud, application, and infrastructure tools can generate more data than a team can process.
More findings do not automatically mean more understanding.
Exposure management creates context: deciding which exposures form a plausible path to something important, which identities and processes are involved, which controls stand between an exposure and a consequence, and what to fix first.
Decker also warns that AI can correlate signals and challenge assumptions, but can build a convincing narrative from incomplete evidence.
A risk score is an interpretation, not a verdict.
For brands planning a campaign
A cybersecurity vendor could build a co-authored article or webinar around the line “Evidence before opinion.
Context before score.
Human accountability at the final cut.”
It supports demand-generation messaging that positions AI as an assistant to prioritization, not the final risk verdict.
This post explains what Joe Decker means by overlooked risk and how they make the idea memorable for a general reader.
Read more
It shows how they connect culture with everyday security practice.
Joe Decker uses Michael McDowell’s Southern Gothic novel “The Elementals” to explain a common security problem.
The scariest risk is not always the loudest vulnerability or the newest CVE.
It can be the forgotten asset, described with the example of a “Windows 98 box in a parking lot,” the inherited exception, the misconfiguration everyone assumes someone else owns, or the third-party exposure that has been sitting quietly.
The danger builds when visibility is partial, ownership is unclear, and people get comfortable with “that’s just how it is.”
Decker argues that good exposure management is not just finding more issues.
It is understanding what is actually in the environment, what can be exploited, what matters to the organization, and what needs action before the problem spreads.
For brands planning a campaign
A book-club or social content series could invite security leaders to name the book, film, or show that made them think about cybersecurity. For a vendor, this softer demand-generation format still delivers the exposure management message around forgotten assets and unclear ownership.
This is a strong introduction to how Joe Decker explains proactive security to people outside security operations.
Read more
It shows their teaching method: a familiar historical frame mapped step by step onto modern practice.
Joe Decker builds an extended Age of Sail metaphor for proactive security.
Mapping the unknown becomes asset discovery.
Inspecting the hull becomes vulnerability management.
Reading the winds becomes threat intelligence.
Securing the cargo becomes data protection.
Exposure management is the sextant and compass that help a team understand its attack surface, prioritize risks, and fortify defenses.
The post connects the metaphor to a direct argument: cybersecurity preparation is not about whether a storm will strike, but how well prepared the organization is when it does.
For brands planning a campaign
A webinar or co-authored article could use the same structure to walk enterprise security buyers through asset discovery, vulnerability management, threat intelligence, and data protection. The metaphor gives a vendor a readable frame for a demand-generation campaign without leading with product categories.
This post explains why Joe Decker treats proactive security as a leadership issue, not just a tooling issue.
Read more
It is a compact example of their historical framing and focus on readiness before an incident.
Joe Decker argues that in cybersecurity, waiting to react is already too late.
They point to Shackleton, who planned for survival before the ice closed in, stocking supplies and leading with foresight.
They also point to Nelson, whose victories came from relentless drilling, anticipation, and positioning before a shot was fired.
The same logic applies to security: threat intelligence, continuous monitoring, and readiness separate resilience from disaster.
Leaders who prepare their teams and infrastructure in advance are the ones who endure.
For brands planning a campaign
A vendor could use the Shackleton and Nelson framing for a campaign on resilience and preparation. It suits a webinar series or executive briefing that asks buyers to fund readiness before an incident forces the conversation.
This post shows how Joe Decker uses technology nostalgia to make modernization and legacy exposure concrete.
Read more
They turn a widely understood cultural reference into a security argument.
Joe Decker uses the end of AOL dial-up after 40 years to talk about legacy risk in cybersecurity.
The familiar beep-boop-screeeeech is a relic, but they say cybersecurity can feel like dial-up: people know there is a better, faster, more secure way to connect, yet old systems and habits persist.
Relying on yesterday’s approach to visibility can leave the door open for risks to sneak in.
The lesson: retire outdated systems before they retire themselves, and upgrade visibility, processes, and response capabilities.
The post closes with the line, “You’ve Got Mail” shouldn’t be the warning sign in cybersecurity.
For brands planning a campaign
A modernization campaign for exposure management could use the AOL reference as a social or video hook. It gives a vendor a familiar way to discuss outdated visibility, stale processes, and response gaps without starting with technical jargon.
Teaching through analogies from history, books, and film4
Proactive security and preparation before the incident3
Asset discovery and visibility as the starting map3
Commercial and platform signals around exposure management3
Exposure management as context, not a longer vulnerability list2
Threat intelligence and continuous monitoring2
Recurring Friday thought-leadership format2
Audience engagement through direct questions2
AI's role and limits in security decisions1
Exposure management as context, not a longer vulnerability list
Across several posts, Joe Decker argues that security teams already face too many findings.
Read more
Exposure management means deciding which exposures form a plausible path to something important, which identities, data, and business processes are involved, and what to fix first. More findings do not automatically mean more understanding.
For brands planning a campaign
A vendor can build co-authored content around a practical prioritization process: how a security team moves from scanner output to business context, with worked examples of what to fix first.
Proactive security and preparation before the incident
Joe Decker uses historical and everyday analogies to make a consistent case: waiting to react is already too late.
Read more
Preparation includes asset discovery, vulnerability management, threat intelligence, continuous monitoring, and readiness to act. The argument favors anticipation over defense alone.
For brands planning a campaign
A webinar series could focus on operational readiness: how security leaders frame, plan, and drill proactive exposure management before a breach, using the preparation framing Joe Decker returns to.
Asset discovery and visibility as the starting map
The posts treat visibility as the foundation of exposure management.
Read more
They point to forgotten assets, inherited exceptions, misconfigurations, and third-party exposures that persist when ownership is unclear. Outdated systems and habits are risks to retire, not tolerate.
For brands planning a campaign
Campaign assets can center on attack surface discovery and ownership assignment. Practical audit questions, ownership maps, and before-and-after examples would fit Joe Decker's focus on what is actually in the environment.
Threat intelligence and continuous monitoring help teams anticipate and adapt to emerging threats.
Read more
The posture is active: leaders who prepare teams and infrastructure in advance are the ones who endure. Monitoring is part of readiness, not a standalone feed.
For brands planning a campaign
A co-authored article or webinar segment could show how threat intelligence informs exposure prioritization and response readiness, using a story of changing conditions rather than a static risk score.
Joe Decker says AI can correlate signals, uncover patterns, challenge assumptions, and work at a scale humans cannot.
But AI can also create a convincing narrative from incomplete or poorly framed evidence.
Polished output is not truth, and a risk score is an interpretation, not a verdict.
For brands planning a campaign
A differentiated campaign angle is AI-assisted exposure management with human accountability. A debate-style webinar or co-authored piece could pair AI-assisted correlation with guardrails: evidence before opinion, context before score, and a named human making the final decision.
Teaching through analogies from history, books, and film
Joe Decker makes security arguments memorable by connecting them to other subjects: Age of Sail navigation, Shackleton and Nelson, a Southern Gothic horror novel, and AOL dial-up.
Read more
The analogies carry the main point and often extend across a full post.
Extended metaphor and cultural reference are the primary teaching devices in these posts.
For brands planning a campaign
Co-created formats can use narrative hooks, but the vendor should supply accurate technical substance so the metaphor supports, rather than replaces, the evidence. The strongest fit lets Joe Decker frame the problem and a practitioner supply the operational detail.
Two posts are explicitly framed as Friday reflections.
Read more
One pairs a book recommendation with an exposure management lesson and a question for the audience.
The other opens with a Friday greeting and builds a ship analogy around proactive security.
Together, they suggest a repeatable weekly format rather than one-off commentary.
For brands planning a campaign
A recurring Friday series could support sustained demand generation for a vendor. The sponsor can contribute data, guest practitioners, or a monthly technical deep dive to complement the reflective format.
One asks what book, movie, or show has unexpectedly made readers think about cybersecurity.
Another asks readers to share their thoughts on drawing insights from history to tackle modern security challenges.
The questions invite participation without requiring a technical answer.
For brands planning a campaign
Campaign planning can include lightweight engagement prompts that feed a broader content series. A vendor could ask security leaders to share a real exposure management lesson or a decision they would make differently.
Commercial and platform signals around exposure management
The posts repeatedly use exposure management, proactive security, and cybersecurity hashtags; two include a Tenable hashtag.
Read more
They place Joe Decker in the exposure management conversation but do not document sponsorship terms, payment, or a formal partnership.
Joe Decker's posts do not establish sponsorship or payment from a partner hashtag.
For brands planning a campaign
Treat the hashtags as topical signals, not proof of a commercial relationship. Before proposing a partnership, ask about scope, disclosure, and any prior relationship.
Joe Decker's posts do not disclose a sponsorship, affiliate arrangement, employment, client engagement, owned business or investment.
Read more
Tenable appears as a repeated hashtag on two cybersecurity posts, showing the topics they associate with the writing.
Other company names appear only as passing examples.
Ask them to clarify any commercial relationships relevant to a campaign.
Tenable
Mention
Two posts end with the hashtags #Tenable, #ExposureManagement and #ProactiveSecurity.
Read more
One discusses drawing exposure management lessons from a horror novel; the other frames proactive security through the Shackleton and Nelson examples. The posts do not disclose whether Joe Decker has a commercial relationship with Tenable; ask them to clarify before a campaign.
Joe Decker's Friday essays use a film, novel, historical episode, or piece of technology nostalgia to make one point about security: exposure management is not a longer list of findings, but the context that turns findings into decisions.
Read more
Start with the exposure management posts for the core argument, then read the AI post for the clearest statement of its limits and the proactive security posts for preparation and readiness. The analogies are the teaching method, so the posts work best in sequence rather than skimmed for definitions.
Both write for security leaders about turning a high volume of findings into practical priorities.
Read more
They use recent technical developments to make the case for stronger governance and monitoring, not just more tooling.
David Daily's posts focus on open-source and software supply-chain risk, including malicious packages and AI as both defender and adversary, and call for dependency analysis and governance. Joe Decker's posts focus on exposure management across an organization's own attack surface, prioritizing context and human judgment over tool output.
Both frame cyber risk as a leadership and governance problem: technical teams cannot own it alone, and executives need to understand the exposure.
Read more
Christina Trocino's posts center on digital assets, custody, smart-contract, regulatory, and insurance risk in financial institutions, often addressing CFOs, general counsel, or boards. Joe Decker stays focused on enterprise security operations, writing about exposure management, asset visibility, and prioritization.
Both connect security controls to trust and human judgment.
Read more
On AI-era risk, they argue that safeguards must be built deliberately, not assumed.
Kenia Acosta writes about identity and access management, especially nonhuman identities such as APIs, service accounts, bots, and agents, with a motivational focus on courage. Joe Decker writes about exposure management across the attack surface, using historical, literary, and film analogies to make the case.
Joe Decker's content targets cybersecurity practitioners and security-tool buyers, covering exposure management, proactive security, asset visibility, and the limits of AI-assisted risk scoring.
Read more
The vocabulary, Tenable and CISO hashtags, and recurring question of “what should we fix first” make the topic a strong fit for a vendor campaign about exposure management.
The only measured audience figure available is a LinkedIn follower count of 884, observed 10 October 2026.
That figure describes reach on one channel at one moment, not followers’ job titles, employer sizes, or buying authority.
For a co-authored article or webinar aimed at security buyers, Decker is a credible voice on the topic with a modest measured following.
Ask for recent LinkedIn audience demographics or any subscriber or reader survey results showing role, seniority, and company size.
At roughly 884 followers, a single post is unlikely to deliver enterprise-scale distribution on its own; plan to amplify through the vendor's own channels, a webinar list, or a co-marketing arrangement rather than rely on organic reach.
The five posts were published between 11 August 2025 and 1 September 2026, showing sustained output on these themes rather than a single burst.
LinkedIn followers
884
LinkedIn profile at linkedin.com/in/thejoedecker · 2026-10-10
Joe Decker's five posts read as original commentary on cybersecurity topics — exposure management, proactive security, asset visibility, and the limits of AI in risk scoring — rather than labeled sponsored placements.
Read more
Two carry a #Tenable hashtag, showing a brand association in the writing but not establishing a paid or formal partnership.
The posts publish no inquiry route, media kit, rate card, or partner page; ask directly about partnership formats, sponsor policies, rates, and availability.
They also demonstrate material for a co-authored or webinar-style campaign: Joe explains risk prioritization, attack surface, and evidence-before-opinion thinking through sustained analogies (age-of-sail navigation, film editing, a Southern Gothic novel), returning to the argument that finding more issues is not the same as understanding them.
The cybersecurity vendor’s campaign for enterprise security buyers is a strong topical match.
Read more
Joe Decker writes directly about exposure management, proactive security, asset visibility, and the limits of AI-assisted risk scoring—the exact subjects the vendor wants to reach enterprise security buyers with.
Several posts offer usable campaign material.
One defines exposure management as creating context around findings: deciding which exposures form a plausible path to something important, what identities, data, and business processes are involved, which controls stand between an exposure and a consequence, and what to fix first.
It also warns that AI can build a convincing narrative from incomplete information, that a risk score is an interpretation rather than a verdict, and that human accountability belongs at the final decision.
That practical framing could anchor co-authored content.
The Age of Sail post maps asset discovery, vulnerability management, threat intelligence, and data protection onto a preparation story, giving a webinar series a readable structure without leading with product categories.
The “Elementals” post makes overlooked risk concrete through forgotten assets, inherited exceptions, misconfigurations with unclear ownership, and third-party exposures.
The Shackleton and Nelson post argues that waiting to react is already too late, and that threat intelligence, continuous monitoring, and readiness separate resilience from disaster.
The AOL dial-up post adds a modernization hook about outdated visibility and stale processes.
Distribution and commercial format are weaker points.
The only measured audience figure stated is 884 LinkedIn followers; the posts provide no demographic data, subscriber survey, or buyer-composition information.
They also publish no media kit, rate card, sponsor policy, disclosed partnership example, or verified inquiry route.
Two posts carry a Tenable hashtag, but do not say whether payment, sponsorship terms, or a formal relationship were involved.
Treat Decker as a credible co-author or co-presenter for exposure management thought leadership, not as a guaranteed enterprise-scale distribution channel.
Plan to amplify through the vendor’s own channels, webinar list, sales team, and paid promotion.
The vendor should supply accurate technical substance, product workflow detail, and customer proof; Decker should supply the argument, teaching frame, and practical prioritization questions.
Ask directly about availability, disclosure, and terms before committing.
When to choose a specialist
A consumer meal-kit company wants a high-volume short-form video creator to drive direct-response sign-ups from a general consumer audience.
Read more
That campaign is a poor match for Joe Decker’s posts.
Their five posts offer cybersecurity commentary for a professional audience, not food, cooking, household, or general lifestyle content.
The recurring subjects are exposure management, proactive security, asset visibility, threat intelligence, AI’s role in risk decisions, and legacy system modernization.
The teaching method relies on extended analogy, using Age of Sail navigation, Shackleton and Nelson, a Southern Gothic novel, film editing, and AOL dial-up.
None translates into meal planning, recipe video, or consumer purchase intent.
The audience information also does not support a consumer sign-up campaign.
The only measured figure is 884 LinkedIn followers; the posts provide no consumer demographics, engagement data, or platform audience composition.
They include no transcript, video example, or short-form format to demonstrate the high-volume consumer video the campaign requires.
The partnerships section lists no sponsorship formats, rates, or published partnership inquiry route.
A brand could approach Decker for a cybersecurity-adjacent consumer analogy, but that would be a different campaign.
For a direct-response meal-kit campaign, choose a creator whose work already matches the audience, lifestyle format, and conversion-oriented video requirements.
If considering Decker for another brief, ask for audience data and short-form video samples.
A worked campaign example
Worked campaign angle for the cybersecurity vendor’s campaign aimed at enterprise security buyers: a co-authored article plus a three-part webinar series titled “From finding more to fixing first: putting context into exposure management.” Aim the series at enterprise security buyers and practitioners responsible for prioritization, ownership, and risk communication.
Part one: “The asset everyone forgot.”
Use Decker’s overlooked-risk argument to open with forgotten assets, inherited exceptions, misconfigurations with unclear ownership, and third-party exposures.
The vendor supplies an anonymized customer example or a discovery workflow from its own product.
Decker frames the practical questions: what is actually in the environment, who owns it, what can be exploited, and what matters to the organization.
The deliverable is a checklist buyers can use to find exposures that are not showing up in the loudest scanner findings.
Part two: “Evidence before opinion, context before score.”
Build this around the AI post.
Decker explains why more findings do not create more understanding, why a risk score is an interpretation rather than a verdict, and where human accountability belongs.
The vendor demonstrates how AI-assisted correlation can support prioritization while keeping a named human at the final decision.
The deliverable is a worked prioritization example that starts with raw findings, adds business context and control information, and ends with a fix-first list.
Part three: “Prepared before the storm.”
Use the Shackleton and Nelson framing to make proactive security a leadership issue.
Decker argues that threat intelligence, continuous monitoring, and readiness drills separate resilience from disaster.
The vendor contributes a threat scenario, a response workflow, or a tabletop exercise.
The deliverable is an executive briefing template that asks buyers to fund readiness work before an incident forces the conversation.
Use the recurring Friday format for lightweight social amplification.
Decker can ask security leaders what book, film, or show made them think differently about risk, then connect the responses to the webinar themes.
The vendor should supply data, technical accuracy, product demonstration, and customer proof.
Decker should own the narrative frame, practical prioritization questions, and demand-generation angle tying the series to the campaign for enterprise security buyers.
Measure article reads, webinar registrations and attendance, on-demand views, resource downloads, and qualified conversations.
Do not promise enterprise-scale reach from the creator’s organic channel alone; plan for the vendor’s list, sales follow-up, and paid distribution from the start.
Ask directly about scope, disclosure, and terms, since the posts do not describe a partnership format or inquiry route.
When the vendor's offer centers on software supply chain or open-source component risk and the campaign wants a named threat plus a short action list.
Read more
Both posts lead with a reported 188% year-over-year rise in malicious open-source packages, then move to concrete buyer steps: rigorous dependency analysis, stronger governance policies, and continuous monitoring. For a supply-chain security product, that gives a demand-generation campaign a sharper opening statistic and clearer calls to action than the exposure-management framing, which focuses on prioritization questions rather than a specific threat category.
The tradeoff is range and repetition.
Both posts build on the same 188% figure and three recommendations, so a multi-part co-authored series could repeat one message.
They offer less close analysis of how risk gets overlooked in a live environment, less on ownership and business context, and little guidance on deciding what to fix first.
There is also no extended teaching analogy to carry a series structure.
The format is narrow: report commentary and a question prompt, rather than the essay-style argument a longer campaign asset needs.
When the campaign targets financial services, insurance, or digital-asset buyers and speaks to the board rather than the security operations team.
Read more
The posts frame digital asset risk around custodian hacks, smart contracts executing incorrectly, mid-transaction regulatory change, and cascading counterparty requirements.
They argue that cyber risk is now a balance sheet conversation, with the CFO, GC, and CEO at the table.
One post reports a fintech-leader discussion on how AI is reshaping cyber, governance, and risk, including the line that attackers no longer break in but log in.
For a vendor selling risk quantification, cyber insurance-adjacent coverage, or digital asset protection, that puts the campaign at executive level earlier than the posts by the creator featured on this page.
The tradeoff is subject fit for an exposure-management campaign.
The posts concentrate on crypto and digital-asset risk, plus a conference recap, with little on asset discovery, vulnerability management, continuous monitoring, or deciding which exposure to fix first.
For a vendor selling exposure management to enterprise security buyers, the campaign would need reframing around financial-services risk, and the vendor would need to supply practitioner-level teaching material.
One of the two posts is an event summary rather than original analysis; ask for more original analysis before building the campaign around this comparison.
When the campaign concerns identity, especially nonhuman identities such as APIs, service accounts, bots, and agents, or wants a personal narrative about why safeguards earn confidence.
Read more
The identity post names the problem directly: this workforce never retires on its own and, unmanaged, creates silent risk.
It offers three actions for identity programs: gain visibility into every human and machine account, retire what no longer serves a purpose, and protect secrets.
That is a tighter hook for an identity, access management, or secrets-management vendor than the broader exposure-management frame.
The tradeoff is breadth and volume.
One of the two posts uses a skydiving analogy to show how well-designed safeguards earn trust, but offers little technical specificity.
The identity post is a short list rather than a developed argument.
Together, they offer less on attack surface, prioritization, or measuring what to fix first, so a longer co-authored series would need more source material.
This profile draws on five LinkedIn posts published between 11 August 2025 and 1 September 2026, alongside its overview, ideas, relationships, discovery, and campaign-fit sections.
The posts connect exposure management to film editing, literature, history, and legacy technology, and argue for understanding context before prioritizing risk.
Coverage here reflects those five posts, not a complete account of Joe Decker’s work.