# David Meece

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.

- Profile: https://b2binfluencer.marketing/creators/david-meece/
- LinkedIn: https://www.linkedin.com/in/david-meece-cybertech-dave
- LinkedIn followers: 136,527
- Topics: artificial-intelligence, cybersecurity, social-engineering
- Based on 14 dated posts, latest 2026-10-22

## Summary

Most useful for accessible cybersecurity learning resources and social-engineering awareness content, especially for newcomers.

- Best for: Cybersecurity training or awareness campaigns that need GRC learning paths and practical entry-level resources.
- Not for: Gated lead-generation campaigns targeting verified enterprise GRC managers or security leaders.
- Check first: Confirm audience analytics and an official inquiry route before discussing a paid placement.

### Takeaways

- 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.

## Main ideas

- **Defenders should consider what an attacker can learn about people**: Social engineering can begin before an attacker contacts anyone, Meece argues. Security teams should consider what personal information about employees is publicly available, rather than rely only on technical controls or awareness training.
- **Pair clear learning resources with practical work**: Meece points readers to structured learning materials and hands-on practice. Their posts make a path into cybersecurity more concrete: start with named frameworks and standards, then build skills through exercises.
- **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. The advice comes with an offer to connect job seekers to a broader professional network.
- **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. The posts describe collaborative projects and direct proceeds toward scholarships or community training.

## Work to read

- [Social engineering starts with what's already public about staff](https://www.linkedin.com/posts/david-meece-cybertech-dave_cybersecurity-socialengineering-osint-activity-7515444049345032194-SSKn)
- [Red Teaming 101, a co-authored print book](https://www.linkedin.com/posts/david-meece-cybertech-dave_cybersecurity-redteam234289-activity-7519050420908965888-i-0f)
- [Stronger Together: Women in Cybersecurity](https://www.linkedin.com/posts/david-meece-cybertech-dave_my-friend-emily-zakkak-and-i-are-excited-activity-7518330685724565506-PocB)
- [A reusable free GRC and information-security resource list](https://www.linkedin.com/posts/david-meece-cybertech-dave_free-resources-that-will-help-you-to-break-activity-7492981378675048450-piux)
- [Opening a network to cybersecurity job seekers](https://www.linkedin.com/posts/david-meece-cybertech-dave_cybersecurity-networking-jobs-activity-7514739958016860160-weIQ)

## Brand relationships

- **Cloaked** (sponsor)
- **Women in CyberSecurity (WiCyS)** (mention)
- **Pass IT On, Inc - Community Technical Training** (mention)

## Partnerships

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. 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.

## Alternatives

- David M.: Prefer this account when a campaign needs a federal compliance practitioner rather than an awareness voice. 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.
- David Rajakovich: 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. 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.
- Zack Tembi: 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. 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.

---
AI-assisted summary of public posts. Audience demographics are not available. Engagement appears only where we checked recent posts. Method: https://b2binfluencer.marketing/methodology/