David Meece is a cybersecurity researcher and educator who shares career resources and practical learning guidance, including material on GRC, information security, and red-team skills.
GRC reading lists group standards like NIST, ISO, PCI DSS, and CIS by subject.
Red Teaming 101 combines red-team fundamentals with hands-on homelabs for practice.
An October 2026 OSINT social-engineering post profiles employees, then promotes Cloaked with #Ad.
Check first: Confirm audience analytics and an official inquiry route before discussing a paid placement.
Main ideas
Defenders should consider what an attacker can learn about people · Pair clear learning resources with practical work · Professional relationships can help people find a way into cybersecurity
David Meece is a cybersecurity researcher and educator who shares career resources and practical learning guidance.
Their reviewed work includes the co-authored book Red Teaming 101, which they describe as combining red-team fundamentals with hands-on homelabs, and the co-curated Stronger Together: Women in Cybersecurity, a collection of stories from more than 100 contributors.
They also publish resources for people entering GRC and information security and write about social engineering and personal-data exposure.
Follow them for accessible entry-point resources, practical cybersecurity learning, and community-focused projects.
Meece connects cybersecurity learning with concrete next steps.
The GRC resource list groups standards and frameworks by subject, making a large field easier for newcomers to explore; the red-team book announcement points to homelabs as a way to practise, not just read.
In a social-engineering post, they explain how public information about employees can help an attacker sound convincing, broadening the usual focus on technical defenses and phishing awareness.
Their work also has a community-building side: the cybersecurity networking post gives job seekers a repeatable routine for making connections, while the women-in-cybersecurity book supports visibility and scholarships.
Some posts share or promote others’ work rather than presenting original instruction: the GRC list credits Aron Lange, and the social-engineering post promotes Cloaked.
The brief AI-attacks post links to an article but does not explain its claims; ask for a fuller analysis of that topic.
David Meece’s posts present cybersecurity as both a technical discipline and a route into work: learn with practical resources, consider how attacks exploit people as well as systems, and help others enter the field through networks and community projects.
Defenders should consider what an attacker can learn about people
Social engineering can begin before an attacker contacts anyone, Meece argues.
Read more
Security teams should consider what personal information about employees is publicly available, rather than rely only on technical controls or awareness training.
In a post about social engineering, Meece asks what an attacker could learn about employees from data brokers, people-search sites, public records and social media. The post presents Cloaked’s data-removal and monitoring service as one response; the product description appears in a post marked as advertising.
Professional relationships can help people find a way into cybersecurity
Meece presents networking as a repeated practice, not a one-time introduction: tell your story, join conversations and keep building connections.
Read more
The advice comes with an offer to connect job seekers to a broader professional network.
A LinkedIn post outlines three steps and names cybersecurity professionals and hiring managers readers can follow or contact. It encourages people to share their goals and look for leads in the thread.
Widening access to cybersecurity takes a community effort
Meece’s book announcements connect cybersecurity education with support for people who face barriers to entering the field.
Read more
The posts describe collaborative projects and direct proceeds toward scholarships or community training.
Meece introduces Stronger Together: Women in Cybersecurity, co-curated with Emily Zakkak, as a collection of more than 100 contributors’ stories, with proceeds directed to WiCyS scholarships.
The post says the book addresses barriers, allyship and DEI.
The Red Teaming 101 announcement separately says a portion of proceeds supports Pass IT On, Inc.’s community training.
Answers the question: does David Meece teach social-engineering awareness or only share links?
Read more
This is the fullest worked example of the topic in their posts.
David Meece walks through an attacker's thought process: who works at a target company, who can access sensitive systems, what personal email addresses, phone numbers, and home locations can be found, and how much can be learned before any contact.
The post argues that data brokers, people-search sites, public records, and social media provide raw material for a convincing approach—and that ordinary security controls and awareness training were not built to address the problem.
It explains that Cloaked scans more than 1,000 data brokers and other sites for exposed employee information, helps remove it, and monitors for reappearance.
The post ends with a call to run a free domain scan and includes hashtags such as #Ad, #SocialEngineering, and #OSINT.
For brands planning a campaign
A training company can use this as a ready-made subject-matter framing: defenders should manage employee exposure, not just teach phishing recognition. The example is a disclosed advertisement for a privacy-removal product, not a training vendor, and asserts Cloaked's coverage numbers without independent detail.
Answers the question: what community work is this person known for?
Read more
It shows a large collaborative project and the values behind it, which many name searches surface before any single post.
David Meece introduces Stronger Together: Women in Cybersecurity, a book co-curated with Emily Zakkak that gathers stories from more than 100 women in IT and cybersecurity worldwide, with forewords by Lynn Dohmm and Gabrielle B.
The book addresses challenges women face entering the industry, the importance of male allyship, and DEI.
All proceeds go to Women in CyberSecurity (WiCyS) for scholarships.
The post thanks named contributors and participating male allies, credits the cover designer, and links to a purchase page.
For brands planning a campaign
The project offers a training brand a credible diversity and scholarship angle for sponsorship or co-marketing, and shows that David Meece can organise contributors and coordinate a published product. The post announces a curated fundraising project; ask for evidence of their own curriculum-design role.
Answers the question: what does David Meece publish about GRC specifically?
Read more
It is the clearest evidence for the GRC half of a subject-matter expert brief.
The post lists free standards and frameworks for breaking into GRC and information security, grouped under risk management, information-security fundamentals, control frameworks, audit, and business continuity.
Named items include ISO 31000:2018, ISO 27000:2018, ISO 22301:2019, several NIST publications (SP 800-30, 800-53, 800-53A, 800-53b, 800-161, and others), PCI DSS 4.0, CIS Critical Security Controls v8, and the ISACA IT Audit Framework.
The list is credited to Aron Lange.
The post closes by asking readers to follow for weekly cyber resources and personal-branding tips.
Two very similar versions appear in the posts: one headed 'Resources that will help you to break into GRC and information security' and one headed 'FREE resources'.
For brands planning a campaign
The list can serve as an outline for a GRC learning path or lead magnet, and its repeated publication suggests an audience for resource roundups. It originates with a third party and is reposted with credit, so treat the curation and framing—not authorship of the cited standards—as the contribution.
Answers the question: who is this person's audience, and how does Meece treat them?
Read more
It is the clearest signal in the posts of how their following is invited to participate.
David Meece offers to open their professional network to people looking for cybersecurity jobs and says it includes hiring managers and practitioners.
The post lays out a three-step routine: introduce yourself and tell your story, engage in comments to build relationships, and repeat weekly.
It lists dozens of named professionals to connect with and follow, including people in security leadership, threat research, and recruiting, and asks readers to share goals and find leads in the thread.
For brands planning a campaign
The post points to an audience of job seekers and early-career entrants, a fit for training, certification, and awareness products aimed at people entering or advancing in the field.
It also uses a contributor-friendly format that promotes many names at once, useful for a workshop or mentorship campaign.
Ask for audited outcomes before relying on the networking advice.
Meece repeatedly publishes free lists of governance, risk, and compliance material, grouped into risk management, information-security fundamentals, control frameworks, audit, and business continuity.
Read more
The lists point readers to ISO 31000, NIST SP 800-30 and 800-53, BSI Standard 200-3, PCI DSS 4.0, CIS Critical Security Controls v8, the ISACA IT Audit Framework, and ISO 22301, among others. Three posts carry near-identical versions of this list.
Short lead-in, emoji-marked category headings, one link per standard, and a closing invitation to follow for weekly cyber resources and personal branding tips.
The lists are credited to Aron Lange, demonstrating curation of another practitioner's material as much as first-party GRC authorship.
For brands planning a campaign
A GRC training or certification provider could sponsor or co-publish this recurring format. The lists show exactly which frameworks the audience is being directed toward, helping position a course, tool, or assessment against named standards.
One post walks through social engineering that needs no technical vulnerability: an attacker learning who works somewhere, who holds access, and what personal email addresses, phone numbers, and home locations are already exposed.
Read more
It names data brokers, people-search sites, public records, and social media as the raw material, and argues that conventional controls and training were not built for that exposure. The post then recommends Cloaked for finding and removing exposed employee information across more than 1,000 data brokers and monitoring it afterward, with a free domain-scan call to action.
First-person 'if I were thinking like an attacker' framing establishes the problem concretely before introducing a product, then closes with the mirrored defender question.
The post claims the recommended product has reach and effectiveness; ask for evidence supporting those claims. The linked material was not reviewed.
For brands planning a campaign
This is the closest existing fit to a social-engineering awareness partnership. The post weaves a vendor product into an attack-thinking narrative without breaking the educational tone and carries a disclosed advertising marker.
Meece announced Red Teaming 101, co-written with Dr.
Read more
Willie Sanders, Jr., combining 30+ years across information technology, cybersecurity, and academia.
The book covers red-team fundamentals and attacker mindset, plus home-lab exercises readers can run immediately.
A portion of proceeds supports Pass IT On, Inc.'s community technical training, described as closing the digital skills gap for youth and adults from disadvantaged backgrounds.
Book paired with practical homelabs, combining conceptual fundamentals with exercises readers perform at home.
For brands planning a campaign
Shows a track record of packaged training products suited to a co-branded curriculum, course sponsorship, or lab-tool partnership, with a stated community-reinvestment angle sponsors could align with.
A short post shares an article on AI-enabled cyber attacks, framing it as a defender's job to keep up with fast-moving threats and information worth spreading to non-specialists as well as security professionals.
Read more
The post is essentially a pointer and a recommendation to read the article.
For brands planning a campaign
A vendor with timely threat research could supply material for this redistribution format, reaching an audience beyond security practitioners.
Meece co-curated Stronger Together: Women in Cybersecurity with Emily Zakkak, gathering contributions from more than 100 women in IT and cybersecurity, with forewords by Lynn Dohmm and Gabrielle B.
Read more
The stated purpose is to encourage women to enter the field and address the barriers they face, the role of male allyship, and DEI.
All proceeds are directed to Women in CyberSecurity (WiCyS) for scholarships.
The red-teaming book follows the same pattern of directing proceeds to community training.
Multi-author books serve as fundraising vehicles, mentorship artifacts, and a platform for contributor visibility.
For brands planning a campaign
A brand could support scholarship or diversity-in-security work through these book and community vehicles. The publicly stated charitable destination and contributor network make the partnership scope concrete.
One post opens Meece's network to job seekers, offers a three-step LinkedIn routine — introduce yourself, engage in comments, repeat weekly — and lists dozens of cybersecurity professionals and hiring managers to follow and connect with.
Read more
The premise is that opportunities come from relationships rather than applications.
Actionable numbered routine plus a tag-and-follow list that turns a post into a connection prompt.
For brands planning a campaign
A recruiting, employer-brand, or community campaign could plug into this amplification format, reaching candidates and hiring managers in the same thread.
Meece's posts here document one clearly disclosed paid promotion, for the privacy service Cloaked, plus two charitable connections tied to books they co-created: proceeds from Stronger Together: Women in Cybersecurity go to Women in CyberSecurity (WiCyS), and part of the proceeds from Red Teaming 101 support Pass IT On, Inc.
Cloaked
Sponsor
Meece wrote a social-engineering and OSINT post built around Cloaked's employee-data removal service.
Read more
It walks through how an attacker would research the people behind a firewall rather than the network itself, then explains that Cloaked scans for exposed employee information across more than 1,000 data brokers and points readers to a free domain scan at cloaked.com/risk. The post is tagged #Ad, marking it as a paid promotion.
Meece co-curated the book Stronger Together: Women in Cybersecurity with Emily Zakkak and said all proceeds are donated to WiCyS, which told the authors the money would be allocated solely to scholarships.
Read more
The post explains the book's purpose, thanks contributors and foreword writers, and links to a purchase page. The connection is a donation of book proceeds.
Announcing that Red Teaming 101, co-written with Dr.
Read more
Willie Sanders, Jr., was in print, Meece said a portion of all proceeds goes to Pass IT On, Inc's community technical training work. They describe that work as closing the digital skills gap for youth and adults from disadvantaged backgrounds, and link to the book on Amazon.
Start with the recurring resource lists mapping the frameworks behind governance, risk, and compliance work, including NIST publications, ISO standards, PCI DSS, and the CIS Controls.
Then read the social-engineering post: it argues that attackers can learn plenty about employees from data brokers, people-search sites, public records, and social media before making contact, and recommends a data-removal service in a post marked as advertising.
A third strand covers getting into and getting on in cybersecurity: a step-by-step networking post names people to follow and connect with, alongside two book projects.
Red Teaming 101, co-written with Willie Sanders, Jr., pairs red-team fundamentals with home-lab exercises; Stronger Together: Women in Cybersecurity, co-curated with Emily Zakkak, gathers stories from more than 100 contributors, with proceeds going to WiCyS scholarships.
Follow Meece for curated framework references and entry-level career material.
Both write on LinkedIn about governance, risk, and control frameworks — NIST, RMF, and how requirements land on real teams — opening with a first-person observation about a governance problem before giving a practical takeaway.
Read more
David M.'s posts work at the level of federal cloud authorization practice: inherited and hybrid controls, shared responsibility matrices, and friction between assessors and administrators. Their posts stay at the level of curated framework lists and career entry, so readers seeking authorization detail should follow David M. instead.
Both take a governance or cyber-risk subject and develop the argument in a long LinkedIn post, using a concrete example before naming a commercial tool or service that responds to the problem.
Read more
Rajakovich builds arguments from threat statistics and product development — third-party risk, software bill of materials and exploitability checks, and the RiskOS and STREAM work — for security and risk leaders. Meece curates other practitioners' framework lists, writes mainly for people entering the field, and their one vendor post is a disclosed advertisement rather than a product of their own.
Both use teaching formats on LinkedIn — structured sessions, named takeaways, and book or curriculum projects — and connect security leadership work to career progression.
Read more
Tembi teaches enterprise AI strategy to executives and managers and interviews sitting CISOs and CIOs about visibility and sponsorship. Meece's education material targets people breaking into cybersecurity and GRC practitioners who need references, not AI adoption plans.
The posts support a cautious, clearly bounded placement decision.
Read more
David Meece can put a GRC and security-awareness message in front of a large LinkedIn following, but the posts don’t describe who follows the account.
It showed 136,527 followers on 23 October 2026 — the only audience figure available.
The eight posts, dated 11 August to 22 October 2026, show the topical mix a sponsor would sit alongside: a beginner-facing GRC and information-security reading list (NIST, ISO, PCI DSS and CIS frameworks, credited to Aron Lange) reposted three times across August, September and October; a social-engineering and OSINT post that walks through how an attacker profiles employees and then links to Cloaked, a personal-data removal service, tagged #Ad; an AI-threat awareness post pointing readers to outside reporting; a job-networking thread inviting followers to connect with named cybersecurity professionals; and two book announcements — a co-authored red-teaming book, with proceeds supporting community technical training, and a curated anthology, Stronger Together: Women in Cybersecurity, whose proceeds go to WiCyS scholarships.
The writing addresses newcomers and career-builders as much as sitting practitioners.
The posts provide no measured audience composition: no post, survey or analytics states followers’ geography, age, gender, job function, seniority or employer.
The follower count shows how many people are attached to the account, not whether they are GRC managers, security analysts, students or recruiters.
For a campaign aimed at GRC and awareness training, treat this as grounds for an exploratory awareness placement with large top-of-funnel reach, not proof of alignment with a purchasing-level GRC audience.
Ask for audience analytics before committing to a purchase-level campaign.
LinkedIn followers
136,527
Follower count recorded on David Meece's LinkedIn account · 2026-10-23
David Meece's posts contain one clearly commercial placement: an October 12, 2026 LinkedIn post on OSINT-driven social engineering that recommends Cloaked's data-broker removal service, links to a free domain scan, and carries an #Ad disclosure.
Read more
The remaining posts are educational or community work—free GRC and information-security resource lists, two books they co-created, and a networking post opening their connections to job seekers.
No official inquiry route is verified, so brands should contact them through their LinkedIn account and agree on terms directly.
The sponsored example shows the format: explain the attacker's method first, then present the vendor as the practical defense, with the link and disclosure inside the post.
Disclosed sponsored post with a product link
Buyer requirement
Negotiate directly; the posts mention no public rate card, package, or booking process.
Expect the creator to make the security case in their analytical voice before naming the sponsor, then frame the sponsored product as the answer—as in the Cloaked post, where they detail how attackers use public personal data and point to the vendor's domain scan.
Supply the problem framing and destination link, agree on the disclosure label and link tracking in advance, and confirm the post will carry an #Ad or equivalent marker before booking.
Brief one: a cybersecurity training company wants a GRC and security-awareness subject-matter expert, and proposes a social-engineering awareness content partnership built on David Meece's posts.
Read more
This is a strong fit.
The training half of the campaign is what Meece already publishes.
Across August, September and October 2026, they post free reading lists for people breaking into governance, risk and compliance, grouped under risk management, information-security fundamentals, control frameworks, audit, and business continuity.
The lists point to ISO 31000, NIST SP 800-30 and 800-53, BSI Standard 200-3, PCI DSS 4.0, CIS Critical Security Controls v8, the ISACA IT Audit Framework and ISO 22301.
A training company gets a partner who already organises the field into a learning path and tells readers which standards to study next.
The lists are credited to another practitioner, Aron Lange, so the contribution is curation and framing rather than authorship of the standards themselves.
For a training campaign, that is a strength: curating a credible syllabus is the job.
The social-engineering awareness half also has a direct precedent.
The October 2026 post on OSINT-driven social engineering does not lead with a product.
It explains how an attacker profiles a company first, asking who works there, who holds access, and what personal email addresses, phone numbers and home locations can be found.
It names data brokers, people-search sites, public records and social media as raw material.
Only then does it introduce a vendor, presenting a data-broker removal service as the practical defence, with a free domain-scan call to action and an advertising disclosure.
That is the shape a training company needs: an educational argument that makes the sponsor's offer the natural next step.
There is teaching substance beyond the posts.
Meece co-wrote a red-team book with Dr.
Willie Sanders, Jr., aimed at people entering the industry.
It pairs attacker-mindset fundamentals with home-lab exercises readers run themselves, and part of the proceeds go to community technical training.
A co-authored, hands-on product is meaningful evidence for a sponsor seeking a course, cohort or lab-based module, and shows a practical rather than purely conceptual teaching style.
The LinkedIn account recorded 136,527 followers on 23 October 2026.
The posts do not provide an audience breakdown, so ask for one before treating that reach as access to GRC buyers.
No media kit, rate card or booking route is described; agree terms directly.
The sponsored post's product claims are the post's own, not independently documented.
When to choose a specialist
Brief two: a compliance-automation vendor wants a gated lead-generation campaign aimed at GRC managers and security leaders at large enterprises, with audience segmentation, a defined sponsorship package, and campaign performance reporting.
Read more
This is a weak fit based on what the posts say.
Nothing describes who the audience is.
The only measured figure is 136,527 LinkedIn followers on 23 October 2026; no post, survey or analytics report states followers' job function, seniority, employer size or geography.
A vendor buying access to compliance decision-makers cannot tell whether the following contains them or is mostly people trying to get into the field.
Two signals point toward job-seekers and early-career professionals: a networking post that opens Meece's connections to people looking for cybersecurity jobs and gives a three-step routine for using LinkedIn to find one, and resource lists explicitly aimed at breaking into GRC and information security.
Senior practitioners may also follow, but alignment with a purchasing-level audience is unproven.
Ask for audience data before booking.
The commercial machinery is also absent.
The posts show one clearly commercial placement, the disclosed post for a privacy-removal service.
There is no sponsorship policy, package, rate card, booking page or verified inquiry route, and no description of newsletter, webinar, podcast or event formats.
A buyer needing fixed deliverables and a reporting cadence would be negotiating blind; ask for a package and reporting terms.
The sponsored post asserts the vendor's coverage across more than 1,000 data brokers without independent detail.
A buyer requiring verified claims and tested conversion performance should run a paid pilot rather than commit to a campaign.
Meece has co-authored a red-team book with home labs, but a vendor seeking to confirm curriculum depth or compliance-specific teaching content should request the material directly.
A simpler awareness-stage placement would fit better: trade reach and credibility for brand recognition, not gated leads to named roles.
A worked campaign example
Worked campaign angle for a cybersecurity training company: a social-engineering awareness partnership.
Concept.
Build the campaign around the defender side of the attacker-profiling argument Meece already makes.
The premise: employees cannot recognise a convincing approach when the attacker already knows their name, role and personal details, so awareness training has to cover what is publicly discoverable about staff, not only how to spot a suspicious email.
The sponsor's course or module is the practical answer.
Post shape.
Open in the first person, as the existing post does: what I would look for if I were planning an approach against a company, and how little of it requires a technical weakness.
Name the specific raw material: data brokers, people-search sites, public records and social media.
State the uncomfortable finding plainly: conventional controls and standard phishing training were not designed for an attacker who opens with accurate personal detail.
Then introduce the sponsored training as what changes employee behaviour, with one clear next step, such as a free assessment or a module preview.
Close by mirroring the question back to the reader, as the existing post does with its defender version.
What the sponsor supplies.
One concrete attack scenario drawn from its own training data or incident material, so the post carries a real example rather than a generic warning; the destination link and its tracking parameters; and the exact disclosure wording.
If the course maps to frameworks, the sponsor can point to standards Meece's lists already name, such as NIST SP 800-53 and ISO 27000, when positioning the module.
What Meece supplies.
The narrative, the attacker-perspective framing, and the transition into the sponsor's product without breaking the educational tone.
A realistic second asset is a short follow-up on what employees should do differently, or a link to the free GRC resource list already in circulation, used as supporting material for the audience segment still building a career.
Disclosure and terms to settle first.
The post must carry an advertising marker, as the existing sponsored post does.
Agree the label, link tracking, whether the sponsor may reuse the post on its own channels, and whether any cause-alignment element is attached, since both of Meece's books direct proceeds to community training and scholarships.
Pricing and deliverables require direct negotiation.
Measurement.
LinkedIn does not provide public engagement figures, and none appear in the posts.
Define measurement up front: clicks on the tracked link, domain-scan or assessment completions if the sponsor hosts the destination, and any post-level metrics Meece agrees to share.
Set expectations for an awareness placement: judge the campaign on reach and completion of the assessment step, not enterprise pipeline.
If a paid pilot matters, run one post before committing to a series.
Before booking, ask for audience data rather than assuming the following is mostly GRC managers.
Whether Meece will work in webinar, newsletter or event formats is undocumented.
For a longer training partnership, discuss curriculum and rights for the co-authored red-team book and its home labs; only the announcement post appears here.
Prefer this account when a campaign needs a federal compliance practitioner rather than an awareness voice.
Read more
The posts work through cloud authorization in the detail a compliance audience recognises: one explains that controls inherited from a FedRAMP-certified provider are not handled and forgotten, still belong in the authorization package, and are often hybrid.
The provider's shared-responsibility matrix establishes where one side's duty ends.
The other describes friction between auditors and system administrators, arguing that their disagreement reflects different vantage points, not different goals, and suggests stepping into the other seat to understand it.
A training company building a course for GRC or RMF practitioners, or a sponsor selling into teams that run authorizations, gets material that speaks directly to that audience's daily work and shows real subject depth.
The buyer's task changes shape here: instead of a social-engineering awareness argument aimed at general employees, the deliverable is practitioner guidance on control ownership and assessor relationships.
The subject drops the employee-facing half of a campaign aimed at general employees.
Neither post deals with social engineering, attacker profiling, phishing recognition or awareness training, so a sponsor wanting the campaign built on that argument would be starting from nothing on this account.
The audience is narrower and more technical: cloud authorization, RMF and the ISSO/ISSM relationship, which reaches fewer people and is harder to convert into a general awareness course.
No follower count, engagement figure, media kit or commercial format is documented, and the posts carry no sponsor offer; ask for availability and terms.
Only two posts were available, both from August 2026, so there is not enough material to judge cadence or range.
The name is recorded only in a partial form; ask for the full name to verify the account.
Choose this account when a campaign is about third-party and supply-chain risk, or governing AI inside a GRC programme, and the sponsor wants evidence-led argument rather than straight teaching.
Read more
One post answers a challenge about whether third-party attacks are rising and works through cited figures: 30% of breaches involving a third party in the 2025 Verizon DBIR, a 431% rise in supply-chain attacks between 2021 and 2023, and rising weekly attacks in 2024.
It then turns to practical controls, asking suppliers for a software bill of materials and a vulnerability exploitability exchange document.
It names the difficulty directly: most companies are not examining supplier risk in detail, and some ask irrelevant questions.
The other post argues that a rogue AI agent looks like normal activity, gives a concrete procurement-agent example, and sets out a governance rule: AI may recommend and explain, but scores move only with evidence and human approval.
A training company could use this as a module on supplier risk or AI governance; the evidence-first structure also lends itself to a course exercise.
The posts double as promotion for the poster's own product, with a direct message invitation on one and a named risk platform on the other, so a sponsor would be placing its content alongside a vendor working an adjacent problem.
That is a different relationship from a training company hiring a subject-matter expert; the framing is partly a competitor's.
The published figures are the post's own reading of third-party reports and were not verified against the underlying sources, so a sponsor needing audited claims should check them first.
There is no social-engineering awareness or curriculum material in the posts, the audience is unmeasured, and only two posts were available, from November 2025 and September 2026, which is too little to establish how often this account publishes or how it changes over time.
Consider this account when a campaign shifts from security awareness to executive education on AI adoption, especially if the sponsor wants a partner who already teaches and can turn material into a session with a takeaway.
Read more
The post describes a 90-minute class at Roanoke College on building an AI strategy and lays out the structure in usable detail: why quiet automation of unowned repetitive work beats another chatbot, how to find hidden tasks, a filter for identifying problems large enough to justify an AI project, who has to be in the room, a prototype built for under $500, and a 60-second pitch.
It ends with a concrete deliverable: a one-page plan naming a use case, data sources, three stakeholders, a rough return estimate, and a two-week prototype.
The interview post does similar work for careers, drawing out a CISO's answer on visibility and translating security outcomes into budget and revenue language.
For a sponsor whose course targets business and security leaders rather than general staff, this shows a teaching format, an output the learner keeps, and a network of executives and practitioners.
The subject is enterprise AI strategy and leadership, not GRC or social-engineering awareness, so the sponsor's course would have to move to match it.
The audience is senior, which suits an executive programme but is a different need from an employee awareness campaign built on attacker profiling.
The posts also promote the poster's own class and company, including the number of agents reportedly run in the company, so a sponsor would share the frame with a competing offer.
No follower count, engagement figure, sponsorship offer, or media kit is documented, only two posts were available, from September and October 2026, and the claims about the class and company results rest on the posts themselves rather than independent records.
This profile draws on eight LinkedIn posts dated August to October 2026: three GRC resource lists credited to Aron Lange, a Cloaked promotion, a networking post for cybersecurity job seekers, announcements of two books, and a link to reporting on AI-enabled attacks.
The lists overlap substantially.
The books and linked articles are not assessed here; product claims are attributed to the post that makes them.