Michael Brooks is a cybersecurity professional whose work focuses on assessing whether security controls protect sensitive information, including in defense-related organizations.
6.2K followersCybersecurityBased on 10 posts · latest Oct 2026
Most useful for explaining how to assess whether security controls actually protect sensitive information.
Best for
A cybersecurity consulting firm running thought-leadership webinars for defense contractors on resilience and assessment.
Not for
A consumer identity-protection brand seeking high-reach household awareness, paid social video, or influencer-style personal stories.
Key takeaways
They distinguish restoring a system from restoring confidentiality of information already exposed.
Assessment can use four tests: control exists, implemented correctly, effective, and effectiveness can be demonstrated.
A breach review asks who owned risk, which safeguards failed, and how fixes are verified.
Check first: Confirm their audience includes people who can influence or approve a defense-contractor security program.
Main ideas
An assessment's job is to prove controls work · Resilience claims have to survive the loss of confidentiality · A breach should be reviewed through accountability questions
Michael Brooks is a cybersecurity professional and retired military officer whose posts focus on whether security controls protect sensitive information.
Writing about a Pentagon personnel-data breach, they distinguish restoring a system from restoring the confidentiality of information already exposed.
Another post addresses the uncertainty defense contractors face around CMMC, CUI, and system scoping.
These pieces offer a practical, accountability-focused view of cybersecurity assessment: what safeguards should do, how to tell whether they work, and what organizations should do when they fail.
Brooks makes cybersecurity assessment concrete by connecting control questions to the people and information at risk.
In one post, a breach prompts questions about who owned the risk, which safeguards failed, who authorized the system, what supported that decision, and how fixes will be verified.
In another, they reduce assessment to four tests: does a control exist, is it implemented correctly, is it effective, and can that effectiveness be demonstrated?
They also address the uncertainty defense contractors report around CMMC and CUI while keeping the focus on the underlying tasks: understand obligations, protect sensitive information, and make informed decisions.
Michael Brooks's recurring argument is that a security assessment exists to prove protections actually work—not to earn a certificate, clear a checklist, or cause as little disruption as possible.
Read more
Across three posts, they press the same questions about controls, treat a Pentagon data breach as a test of that standard, and return to a stable set of priorities: understand your obligations, protect sensitive information, decide with evidence, keep moving. The posts are short LinkedIn arguments that state a claim, ask pointed questions, and close on the line "the mission continues."
An assessment's job is to prove controls work
Michael Brooks defines a security assessment by what it produces: evidence.
Read more
The test is not whether a control was documented or a report filed, but whether anyone can show that the control exists, is configured correctly, works in practice, and can be proven to do so.
An assessment completed with the least possible disruption has missed its purpose: to find weaknesses before an adversary does.
The same standard applies at the organizational level.
Preventive and detective controls should prevent disclosure, detect activity, and limit exposure.
When they do not, the question is why.
After reporting that unauthorized users accessed unencrypted personal information from the Defense Manpower Data Center, including Social Security numbers, Michael Brooks reduces the test to four questions: Does the control exist?
Resilience claims have to survive the loss of confidentiality
Michael Brooks accepts "from static checklists to continuous cyber resilience" as a worthy ambition but asks whether the change delivers the protection people and the mission require.
Read more
The reasoning turns on an asymmetry: a system can be restored, but exposed information cannot be made secret again.
That makes confidentiality loss the case a resilience program has to answer for.
Continuous resilience means continuous evidence that protections work, plus accountability when they do not.
Reporting described unauthorized access to unencrypted personal data over a span of months. Michael Brooks treats that as more than a single control failing and asks why preventive and detective layers did not prevent disclosure, detect the activity, and limit exposure.
A breach should be reviewed through accountability questions
Rather than treating a breach as a technical incident to close, Michael Brooks uses it as a case for reform and lists what that reform should answer: who owned the risk, which safeguards failed, who authorized the system to operate and on what basis, what evidence supported confidence in those safeguards, and how corrections will be verified.
Read more
Reducing bureaucratic drag is useful only if it strengthens the ability to answer those questions; otherwise, the same failure can recur without anyone showing what changed.
In the Pentagon personnel data breach post, Brooks poses a sequence of questions a reform effort should answer, ending with how it will verify corrections.
Michael Brooks reports hearing the same concern from defense contractors: they want to do the right thing but are no longer sure what that is.
Read more
The pressures named are the Pentagon breach, continued uncertainty around CMMC, contract and system scoping challenges, and ongoing CUI ambiguity.
The response is not a promise of clarity but a short list of what stays constant regardless — understand your obligations, protect sensitive information, make informed decisions, keep moving forward.
The phrase "the mission continues" closes more than one post and carries the same idea.
The quoted line comes from contractor conversations Michael Brooks reports having, not from a named individual; the partners at RADICL are named as session collaborators.
Michael Brooks quotes the recurring line "We want to do the right thing, but we're not sure what the right thing is anymore" and answers it with a four-item list. The post promotes a session with RADICL for the Defense Industrial Base, meant to separate headlines from requirements.
The post makes the tension explicit: contractors describe uncertainty about what the right thing is, while Michael Brooks argues that the underlying mission has not changed.
The people behind the data are the reason the work matters
Michael Brooks writes about breaches as harm to people, not just records.
Read more
The exposed files belonged to people who serve, served, and support the country. A veteran potentially affected and a cybersecurity professional who has evaluated whether controls are implemented and effective, they put the stakes plainly and reject assessments reduced to paperwork: the information and the people behind it matter.
In the breach reaction post, Michael Brooks calls the situation "not okay," notes that the data was reportedly unencrypted, and asks who is accountable.
In a single short piece, Michael Brooks answers the question a newcomer is likely to ask—what do they argue about security assessment?—and sets out the frame that informs the other posts: assessment should prove controls work, not produce paperwork.
The post accepts the slogan “from static checklists to continuous cyber resilience” as a worthy ambition, then asks whether it delivers the protection people and the mission require.
Its core argument rests on a distinction: you can restore a system, but you cannot make exposed information secret again.
The post points to the Pentagon personnel data breach: reportedly unencrypted personal information accessed by unauthorized users over a span of months, which it treats as evidence of more than one control failure.
It lists the questions reform should answer: who owned the risk, which safeguards failed, who authorized the system to operate and on what basis, what evidence supported confidence in those safeguards, and how corrections will be verified.
It closes with the argument that continuous resilience requires continuous evidence that protections work—and accountability when they do not.
Michael Brooks writes as a retired military officer and career cybersecurity professional, and says the breaches are personally troubling.
For brands planning a campaign
This is a natural spine for an opening webinar segment. The five reform questions work as a checklist for the audience, while the distinction between restoring a system and restoring confidentiality gives a host a memorable hook for a continuous-resilience session aimed at defense contractors.
This post shows their voice and personal stake in one read.
Read more
It answers two questions—why does this matter to them, and what do they think an assessment is for?—giving newcomers both the emotional register and the technical point.
The post opens flatly: “This is not okay.”
It then walks through the reported facts of the Pentagon breach: unauthorized users accessed files containing personal information from the Defense Manpower Data Center, including Social Security numbers, and the data was reportedly unencrypted.
Brooks stresses that this was not obscure technical debt buried in a system, but sensitive information belonging to people who serve, served, and support the country.
“I'm one of them,” they write, describing the dual perspective of a veteran potentially affected and a professional responsible for evaluating whether controls are implemented and effective.
The post defines an assessment as a way to find weaknesses before an adversary does—not paperwork, a compliance exercise, or something to complete with the least possible disruption.
It asks four questions of any control: does it exist, is it implemented correctly, is it actually effective, and can we prove it?
The post closes by asking who is accountable.
For brands planning a campaign
This shows they can respond to a live news event with a position, not just a summary—the kind of perspective a news-reactive webinar or commentary slot needs. The four control questions give a host a ready-made structure for the middle of a webinar, while their candor about personal exposure makes a panel feel specific rather than generic.
This post answers a different question: who does Michael Brooks talk to, and what problem do they bring?
Read more
It offers the clearest view of the defense-contractor audience and the everyday confusion the work addresses.
The post centers on a recurring conversation, quoted directly: “We want to do the right thing, but we're not sure what the right thing is anymore.”
It names the pressures behind that uncertainty: the recent Pentagon data breach, continued uncertainty around CMMC, contract and system scoping challenges, and ongoing CUI ambiguity.
Defense contractors, the post says, are overwhelmed as they balance mission requirements, compliance obligations, and cybersecurity risk.
Its response is a short list of what stays constant: understand your obligations, protect sensitive information, make informed decisions, and continue moving forward.
The post announces a session with partners at RADICL and the Defense Industrial Base community to cut through the noise, separate headlines from requirements, and discuss what the current environment may mean next.
It closes with “The mission continues,” a phrase also used elsewhere in the material.
The post tags #cybersecurity, #CUI, and #defenseindustrialbase, and names several people and one firm in the thread.
For brands planning a campaign
This is the audience post.
It shows Brooks working directly with defense contractors facing CUI and CMMC anxiety and appearing in a live, partner-hosted session—evidence of a fit for a webinar series aimed at the same Defense Industrial Base audience.
The quoted contractor line, “we're not sure what the right thing is anymore,” offers a strong, candid framing question for a series promising practical guidance rather than more headlines.
Format: short LinkedIn arguments and a partner session3
Security assessments as proof that controls work2
Continuous resilience judged by protection, not slogans1
Breach accountability and the questions reform must answer1
Defense contractor uncertainty around CMMC, scoping and CUI1
Human stakes and personal accountability in cybersecurity1
Practical guidance for an evolving regulatory and threat landscape1
Security assessments as proof that controls work
Brooks argues that an assessment is not paperwork, a certificate or a compliance exercise.
Read more
Its purpose is to identify weaknesses before an adversary does.
They say an assessment must determine whether a control exists, is implemented correctly, is effective and can be proven.
In the Pentagon breach post, they say unencrypted sensitive files being accessible should raise questions about technology, processes, leadership and assurance activities.
A repeated verification sequence: Does the control exist?
Is it implemented correctly?
Is it effective?
Can we prove it?
For brands planning a campaign
A webinar or guide can focus on evidence-based assessment: how defense contractors test control effectiveness, document proof and find weaknesses early. Avoid framing the topic as minimum-disruption compliance.
Continuous resilience judged by protection, not slogans
Responding to the phrase “from static checklists to continuous cyber resilience,” Brooks asks whether the shift delivers the protection people and missions require.
Read more
They note that a system can be restored, but exposed information cannot be made secret again. After a breach that reportedly involved months of unauthorized access to unencrypted personal data, they say layers of preventive and detective controls should have prevented disclosure, detected activity and limited exposure.
Brooks argues that resilience claims must be tested against confidentiality loss and failed safeguards.
For brands planning a campaign
This supports thought leadership on what continuous cyber resilience should mean in practice: ongoing evidence that safeguards work, clear accountability when they do not, and breach reviews that go beyond restoring systems.
Breach accountability and the questions reform must answer
Brooks treats the Pentagon personnel data breach as a concrete case for reform.
Read more
They ask who owned the risk, which safeguards failed, who authorized the system to operate and on what basis, what evidence supported confidence in safeguards, and how corrections will be verified. They say this was not a single control failure and that eliminating bureaucratic drag should strengthen the ability to answer those questions.
Question-led breach review connecting accountability, authorization, evidence and verification of corrections.
For brands planning a campaign
A campaign can build a session around a breach-review framework: risk ownership, authorization basis, evidence of control confidence and verification of fixes. This gives defense contractors a practical structure for after-action reviews and assurance discussions.
Defense contractor uncertainty around CMMC, scoping and CUI
Brooks describes recent conversations with defense contractors who want to do the right thing but are no longer sure what that means.
Read more
They point to the Pentagon breach, continued CMMC uncertainty, contract and system scoping challenges, and ongoing CUI ambiguity as sources of overwhelm. The mission, they say, remains to understand obligations, protect sensitive information, make informed decisions and move forward.
Brooks names the stressors, then returns to a steady mission sequence: understand obligations, protect sensitive information, make informed decisions and move forward.
For brands planning a campaign
This is a direct opening for a practical webinar series aimed at the Defense Industrial Base: separate headlines from requirements, clarify current obligations, and help contractors make defensible scoping and CUI decisions without waiting for perfect regulatory certainty.
Human stakes and personal accountability in cybersecurity
Brooks writes as a veteran potentially affected by the Pentagon breach and a cybersecurity professional who has evaluated whether security controls are properly implemented and effective.
Read more
They say the exposed information belonged to people who serve, served and support the nation, and that assessments matter because the information and the people behind it matter.
They call the situation “not okay” and ask who is accountable.
Reporting in the post says the breach involved Defense Manpower Data Center files containing personal information, including Social Security numbers.
Ask Brooks for their military branch, rank and dates of service if these details matter to the campaign.
For brands planning a campaign
Messaging can connect technical assurance to mission and people. A campaign should avoid treating breach victims as abstract records and show how assessment decisions affect real people, without relying only on fear.
Practical guidance for an evolving regulatory and threat landscape
Brooks promotes a session with RADICL that will cut through the noise, separate headlines from requirements, discuss what remains relevant today and explore what the current operating environment may mean for the future.
Read more
They encourage defense contractors navigating these challenges to join and share their perspective.
Partner session and community conversation, with an explicit promise to distinguish news coverage from actual requirements.
For brands planning a campaign
A co-hosted webinar or partner-led discussion can use Brooks’s format: headline-versus-requirement breakdown, current relevance, future outlook and audience participation. Brands should position it as practical guidance for the Defense Industrial Base rather than another abstract compliance briefing.
Format: short LinkedIn arguments and a partner session
The posts are short LinkedIn pieces built around a single claim or breach, pointed questions, and a plain closing line such as “the mission continues.”
Read more
One promotes a forthcoming session with RADICL for the Defense Industrial Base. Ask for post dates to assess changes over time and cadence.
Only three posts appear here, with no dates or other formats. Ask for a broader, dated sample to assess the full range and evolution of Brooks’s topics.
For brands planning a campaign
A brand should expect a direct essay style and a willingness to promote partner sessions. Test whether Brooks’s questioning approach can carry a longer webinar format before committing to a multi-part series.
One named working relationship appears in Brooks's posts: RADICL, a cybersecurity firm they describe as a partner in a session for the Defense Industrial Base.
Read more
The same post tags A-LIGN, a compliance and audit firm, but gives no detail about a connection to it. Ask whether any of these relationships involve sponsorship fees, client engagements, business ownership, or employment at a named company.
RADICL
Disclosed partnership
In a post about CMMC uncertainty, contract scoping, and CUI ambiguity facing defense contractors, Brooks says they are "looking forward to connecting with our partners at RADICL" and invites the Defense Industrial Base community to a session.
Read more
Ask whether the arrangement is paid or sponsored and how long it runs.
Michael Brooks writes short, first-person arguments about the purpose of a security assessment.
Read more
Start with the two breach posts together: the reaction to the Pentagon personnel data breach, then the follow-up that turns it into a reform checklist.
The CMMC and CUI post applies the same thinking as practical guidance for defense contractors and is the clearest example of a partner discussion.
Across all three posts, recurring questions — does the control exist, is it implemented correctly, is it effective, can it be proven — drive the argument.
CybersecuritySecurity assessmentContinuous cyber resilienceBreach accountabilityCMMCControlled unclassified information (CUI)Defense Industrial BaseVeteransLinkedIn postsPartner sessions and webinars
Both write about what happens when access controls and monitoring fail, and treat the answer as a question of proof and accountability.
Read more
Motola's posts on unauthorized data access argue that unauthorized access is itself a reportable incident, and that the hard part is preventing it while keeping legitimate access open for investigations and legal compliance — the same tension Michael Brooks presses when they ask whether a control exists, is implemented correctly, is effective, and can be proven.
Motola builds a named interview series, "Identity Nightmares," around conversations with CISOs and other named practitioners, and stays on identity and access management and its regulatory consequences. Michael Brooks writes first-person essays about assessment practice in a defense context; their posts do not include an interview or guest format.
Same subject territory and audience: CMMC, controlled unclassified information, and cyber readiness for the Defense Industrial Base, with attention to small and micro contractors and supply-chain risk from subcontractors who are not yet compliant.
Read more
Makrokanis's posts read as company and program announcements — a US Army NCODE selection, a new product aimed at suppliers under 25 employees, an AUSA reception. Michael Brooks argues for a standard of what an assessment should prove and promotes a partner discussion session rather than a product or program.
Both treat cyber failures as accountability problems rather than purely technical ones, and close posts with direct questions to the reader — who has access to the data, who is responsible, what oversight exists.
Read more
Each also writes from a professional standpoint about the consequences of a breach for the people behind the records.
Rebecca Human AI Trust Leader focuses on AI as an insider and external threat, digital ID and privacy, and speculative future scenarios, arguing from warnings, ethics, and oversight. Michael Brooks focuses on defense-sector assessment practice, drawing on firsthand experience as a veteran potentially affected by a breach.
Michael Brooks’s LinkedIn following of about 6,166 supports a limited-reach placement, not a large-reach campaign.
Read more
Their three posts address defense contractors and cybersecurity assurance peers through topics including continuous assessment, CUI and CMMC uncertainty, and a Pentagon personnel-data breach.
For a thought-leadership webinar series on continuous cyber resilience and security assessment, the key question is whether the following includes people who can influence or approve a defense-contractor security program.
Ask for LinkedIn post and page analytics, a follower demographic breakdown by geography, age or gender, an audience survey covering industry, role, and seniority, and recent results for comparable assessment-focused posts.
LinkedIn followers
6,166
Follower count recorded with the LinkedIn profile (https://www.linkedin.com/in/mdb-michael-brooks) · 2026-10-08
The posts do not list a sponsorship package, rate card, media kit, or published inquiry route for Michael Brooks.
Read more
They show participation in and promotion of live educational sessions with defense-industry partners.
One post invites the Defense Industrial Base community to a session run with the partners at RADICL, covering what remains relevant under CMMC uncertainty, contract and system scoping challenges, and controlled unclassified information (CUI) ambiguity.
The other two posts are commentary from Brooks on security assessment and the Pentagon personnel data breach, with no commercial offer.
For a buyer planning a thought leadership webinar series on continuous cyber resilience and security assessment, session-based collaboration is the only format shown.
No terms, deliverables, or booking process are published; ask Brooks directly about these before pursuing an arrangement.
Co-hosted educational sessions with industry partners
Buyer requirement
The posts show one session held with the partners at RADICL, aimed at defense contractors navigating CMMC uncertainty and CUI ambiguity.
They publish no sponsorship terms, deliverable list, pricing, or booking route, so a webinar series would need to be pitched and negotiated as a new arrangement.
Confirm availability, format, promotional commitments, and compensation directly before building the series into a campaign plan.
A cybersecurity consulting firm asking Michael Brooks to lead a thought-leadership webinar series on continuous cyber resilience and security assessment for defense contractors is matching the work they write about.
They argue that continuous resilience should be judged by whether protections work, not by slogans, and draw a sharp line between restoring a system and restoring confidentiality once information has been exposed.
They offer reusable teaching structures: five reform questions about risk ownership, failed safeguards, authorization, proof, and verification of corrections, and four control questions about whether a control exists, is implemented correctly, is effective, and can be proven.
They also address the named audience directly, writing about defense contractors facing CMMC uncertainty, contract and system scoping challenges, and CUI ambiguity, and promoting a practical session with partners at RADICL for the Defense Industrial Base.
The personal stake is clear: they write as a retired military officer and career cybersecurity professional, and as a veteran potentially affected by the Pentagon breach.
The conditions are practical.
Their reach is niche, at about 6,166 LinkedIn followers, and no engagement or demographic data is available.
The firm should verify that the audience includes people who can influence or approve a defense-contractor security program.
No sponsorship terms, rate card, or booking route are published, so availability, format, promotional commitments, and compensation must be negotiated directly.
The posts are three short LinkedIn posts with no dates or longer-form work.
Test whether they can carry a longer webinar format with one pilot before committing to a series.
When to choose a specialist
Poor fit for a consumer identity-protection brand seeking a high-reach U.S. household awareness campaign on identity theft, using paid social video and influencer-style personal stories, and measuring success mainly by follower growth and broad engagement.
Read more
The brand is asking for a different audience and format than the posts demonstrate.
They target the Defense Industrial Base and cybersecurity assurance peers, not households, and discuss CMMC, CUI, contract scoping, security assessments, and accountability for a Pentagon personnel data breach.
Brooks has a niche LinkedIn following of about 6,166, with no demographic or engagement data to support a high-reach consumer campaign.
The Pentagon breach post has human stakes and could be adapted for identity-theft awareness, but it is framed through assessment, controls, and accountability, not household protection advice.
No video, transcript, longer-form work, or performance data is available, so the posts do not demonstrate experience with paid social video or broad consumer reach.
No sponsorship package, pricing, or booking route is published.
A narrower professional campaign aimed at cybersecurity and compliance teams at public-sector suppliers would change the assessment; for the household campaign as stated, the fit is weak.
A worked campaign example
Worked campaign angle: “Prove It,” a three-session webinar series on continuous resilience and assessment for defense contractors.
The objective is to give defense-contractor security, compliance, and program leaders a practical way to test whether their controls actually work.
The audience is Defense Industrial Base security leads, CMMC and CUI program owners, assessors, and consulting-firm clients.
The format is three 45-minute LinkedIn Live or webinar sessions co-hosted by the consulting firm and Michael Brooks, each built from one of their posts and paired with a working resource.
Session one starts from the continuous-resilience post: a system can be restored, but exposed information cannot be made secret again.
It walks through five reform questions—who owned the risk, which safeguards failed, who authorized the system to operate and on what basis, what documentation supported confidence, and how corrections will be verified—and gives attendees a breach-review question checklist.
Session two uses the assessment post to teach four control questions: Does the control exist?
Is it implemented correctly?
Is it actually effective?
Can we prove it?
It applies those questions to the Pentagon breach reporting as a case and gives attendees a control documentation pack template.
Session three uses the contractor quote—'We want to do the right thing, but we're not sure what the right thing is anymore'—to name the pressure from CMMC uncertainty, scoping challenges, and CUI ambiguity, then returns to the stable sequence of understanding obligations, protecting sensitive information, making informed decisions, and continuing forward.
It gives attendees a scoping decision worksheet.
Promotion runs through Brooks's LinkedIn account and the consulting firm's channels, with direct invitations to defense-contractor contacts and, if available, the RADICL partner network, following the existing partner-session style of practical guidance rather than another compliance briefing.
Measurement should include registrations by employer type and role, attendance, resource downloads, and follow-up assessment requests, not follower growth alone.
Guardrails: run one pilot session before committing to three; verify audience composition and engagement analytics first; negotiate terms, promotional commitments, and compensation directly because no package is published; keep the Pentagon breach discussion factual and sourced; and distinguish a lack of a published sponsorship offer from a claim that Brooks never accepts sponsorship work.
Choose Makrokanis when the series needs to reach small and mid-sized defense suppliers held back by the cost of CMMC and NIST SP 800-171 compliance.
Read more
The posts are written from inside Summit 7's CMMC work.
Summit 7 was one of eight companies picked for the U.S.
Army's NCODE program, described in the post as the Army's answer to the price barrier CMMC poses to businesses with 2 to 10 employees.
A second post pitches a supply-chain readiness session at AUSA for primes and their small subcontractors, aimed at companies under 25 employees, and promises visibility into subcontractor compliance and a lower-cost path for smalls.
If the webinar needs a co-host who can speak directly to getting small suppliers compliant and giving primes visibility into their status, Makrokanis is the closer match for the task.
The tradeoff is teaching depth and format.
The two posts are a program announcement with a CEO quote and press link, and an event invitation with a booking link.
They show reach into the CMMC market and a concrete product angle, but not a reusable assessment method, a close reading of a breach, or the accountability framing in Brooks's posts.
A series built around Makrokanis would lean on program news and event promotion; one built around Brooks would focus on testing whether controls actually work.
Ask both creators for audience size, engagement, and commercial terms.
Choose Motola when the series should center on identity and access management and the regulatory cost of unauthorized access, rather than control assessment for defense contractors.
Read more
The two posts promote an 'Identity Nightmares' interview series.
One features Kayla Williams, CISO at Devo, arguing that unauthorized access is itself a reportable incident that can trigger large GDPR fines, and that IAM has to block intruders while keeping authorized investigation and legal teams working.
The other features Barry Gordon on privileged access, overlooked legacy systems, and misconfigurations that escalate into breaches.
For a series with named practitioner guests and a GDPR and enterprise angle, the interview format is ready to reuse.
The tradeoff is focus and authorship.
Motola's material is IAM- and GDPR-centric and built around other people's interviews, so it carries less of the creator's own framework and little on defense-contractor requirements such as CMMC, CUI, or assessment evidence.
It also sits further from the stated task: continuous resilience and assessment for defense contractors.
The posts are promotional episode summaries, not full interview transcripts; ask for the transcripts to assess the depth of the conversations.
Ask for audience, engagement, and commercial data before booking.
Choose this creator when the need shifts toward AI trust, autonomous-agent risk, insider threat, or consumer digital identity instead of defense-contractor control assessment.
Read more
The two posts cover an autonomous AI hack of three companies that Anthropic disclosed after the fact, framed around oversight, accountability, and the limits of machine 'understanding,' and the arrival of U.S. passport digital ID in Apple Wallet, framed around privacy, data access, and personal autonomy. For a broader AI-and-privacy angle or a session on insider and AI-driven threats, this material opens that conversation.
The tradeoff is that this work asks questions more than it supplies method.
The posts raise concerns—who has access, who can sell the data, whether digital ID erodes autonomy—and invite comment, but they do not offer a reusable assessment framework, defense-contractor specifics, or the breach-review questions Brooks supplies.
Much of the framing is consumer-focused and speculative, which suits an awareness audience better than a compliance or assessment audience.
Ask for verified post examples, audience size, engagement, and commercial terms before booking.
Michael Brooks's three LinkedIn posts here cover continuous cyber resilience, using a Pentagon personnel data breach as a case; a reaction to that breach arguing why security assessments matter; and CMMC uncertainty, contract scoping, and controlled unclassified information for defense contractors.
The posts also provide the basis for the page's discussion of topic, brand, and audience.
Short LinkedIn posts from three other cybersecurity creators explain why readers might consider someone else.
The posts have no publication dates, so the page describes recurring arguments rather than a timeline, and the three posts are a sample of the work rather than a full record.
No books, talks, articles, videos, transcripts, longer-form writing, engagement analytics, audience demographics, media kit, or sponsorship terms appear here.
Michael Brooks had about 6,166 followers on LinkedIn on 8 October 2026.
Dated posts and longer-form work showing how the assessment argument holds up over more than a few paragraphs could change the recommendation.
