Erin Joe is an attorney who advises clients on cybersecurity incidents and critical-infrastructure issues, including telecom, satellites, and government contracting. Joe's posts draw on experience Joe describes in the FBI, Mandiant, and Google Cloud, and discuss incident response, regulatory reporting, and national-security careers.
Erin Joe is most useful for practical guidance on cyber incident response, regulatory reporting, and critical-infrastructure legal preparation.
Best for
A cybersecurity legal services firm planning a client webinar on incident response and reporting.
Not for
A consumer cybersecurity product or mass-market brand seeking high-reach awareness and impressions.
Key takeaways
Map reporting requirements in advance and involve cyber counsel early.
Assign leaders to incident workstreams and document when reporting clocks begin.
A data compromise can create long-tail customer, government, and exposed-data reporting obligations.
Check first: Confirm paid collaboration availability, format, contact route, and audience demographics.
Main ideas
Cyber incidents require an ecosystem, not a single organization · Prepare leaders and people, and understand the scope—not just the plan · Map reporting clocks and secure privilege early
Erin Joe is an attorney whose posts connect cybersecurity incident response with legal judgment, critical-infrastructure concerns, and national-security careers.
Drawing on experience they describe in the FBI, Mandiant, and Google Cloud, the posts explain how organizations can prepare for an incident and how people can find meaningful paths into cyber and public service.
Follow them for practical guidance on reporting requirements, decision-making, and the people and expertise involved in responding to attacks.
Joe makes complicated incident-response problems concrete.
In one post, they recommend mapping reporting requirements in advance, involving cyber counsel early, assigning leaders to incident workstreams, and documenting decisions about when reporting clocks begin.
Other posts widen the frame: preparation depends on people and practiced leadership, while a data compromise can create a long tail of customer, government, and exposed-data reporting obligations, particularly in satellite and defense settings.
A career post offers a counterpoint to the technical and legal material: they describe a non-linear path from an English major to national- and cyber-security leadership and advising.
Together, these posts offer actionable questions to consider before an incident and a view of the broader professional ecosystem around cybersecurity.
Joe’s posts frame cyber incident response as a legal, operational, and relationship challenge that starts before an incident and continues long after it.
Read more
The recurring arguments: map reporting obligations and secure cyber counsel early; rehearse leadership and internal decision-making; draw on a wider ecosystem of security professionals, analysts, attorneys, and government agencies; and prepare for the long-tail work of reporting exposed data and managing customer and government relationships. A separate theme is making national-security and cyber career paths visible, including non-linear routes into law, policy, and public service.
Cyber incidents require an ecosystem, not a single organization
Erin Joe argues that ransomware and nation-state attackers target thousands of victims at once, so a victim’s response depends on a wider group: security professionals, data analysts, attorneys, and government agencies.
Read more
The priority is to identify and bring in that support rather than treat the incident as an internal problem.
In one post, Erin Joe credits a Wiley Rein conversation with Pamela Signorello and Lyn Brown about decades of experience helping clients understand, prepare for, and navigate cyber threats, issues, and incidents. In another, a checklist urges organizations to leverage the ecosystem and rally with people who have handled incidents many times before.
Prepare leaders and people, and understand the scope—not just the plan
Joe treats crisis-management preparation and leader preparation as distinct tasks, argues that people rather than plans get organizations through challenges, and says teams need to understand scope and scale before acting.
Read more
A six-point list in Joe’s cyber response post covers crisis management preparation, leader preparation, putting people over plans, understanding scope and scale, leveraging the ecosystem, and rallying with experienced people. Joe credits Pamela Signorello for the questions that prompted those points.
From an InfraGard/INMA panel, Joe reports that many organizations face multiple mandatory reporting requirements, not all of which immediately involve cyber legal counsel, and that many still need practiced internal decision-making.
Read more
The recommendations: map reporting obligations in advance; secure cyber counsel and assert privilege over legal advice and deliberations immediately; assign clear leadership and resources to every workstream; and document when the reporting clock starts, since a regulator may interpret the trigger differently.
The panel took place at INMA’s Congress honoring 30 years of the FBI’s InfraGard program, with more than 200 attendees. Joe names fellow panelists Dan Adams, Andy Maus, Neal Schubert, and Michael Carr.
The costliest part of a data compromise is often the long tail
Joe argues that the period after a data compromise is often the most extensive, unexpected, and costly part of the incident.
Read more
Satellite and defense organizations may have to report not only the incident but also specifics about exposed data, then manage customer and government relationships and requirements.
For a CyberSat roundtable on November 2 at the Hyatt Regency in Reston, Virginia, Joe planned to share lessons learned on post-incident customer and government relationships. Joe says Mark Holmes contacted them about 10 years earlier as CyberSat Summit was forming, and they have served as a supporter and advisor since.
Joe describes a move from the FBI to Mandiant and Google Cloud to Wiley Rein LLP, shifting from sharing new and novel cyber attack types to advising critical-infrastructure clients—including telecom, satellites, and government contractors—on post-incident reporting and relationships.
Make national security and cyber career paths visible and purpose-driven
Joe argues that non-linear backgrounds can lead to national and cyber security leadership.
Read more
They see career navigation across law, national security, cyber, policy, and public service as a subject worth discussing openly—including how to know whether you are on the right track, overcome adversity, and lead with purpose.
Joe describes an English-major and attorney background that did not point toward a career in national and cyber security leadership and advising. They joined the National Security Institute at George Mason University’s Antonin Scalia Law School for a discussion with Jamil Jaffer and Arun Gupta.
This is a separate priority from the incident-response thread; in the posts here, it appears as a single event topic rather than a recurring incident-response argument.
What should someone considering a career in law, national security, cyber, policy, or public service know?
Read more
Erin Joe shares their nonlinear path and the purpose-driven career perspective that runs through the account.
Erin Joe describes being an English major and attorney before joining the National Security Institute at George Mason University's Antonin Scalia Law School for a discussion with Jamil Jaffer and Arun Gupta.
The post explores career navigation across cybersecurity, technology, law, policy, and public service; how to know whether you’re on the right track; overcoming adversity; and taking a broader view of a career.
It presents leadership and advisory roles in national and cyber security as accessible career paths, not ones reserved for a single credential.
For brands planning a campaign
For a law firm, university group, or association planning a webinar, this post shows Erin Joe speaking to a mixed audience about career paths and purpose, not just technical incident details. It supports an early-career or cross-disciplinary panel and can attract attendees weighing how law, cyber, and policy fit together.
Why does a single cyber attack affect more than one organization?
Read more
Erin Joe makes the case for an ecosystem-wide response, before turning to preparation steps or reporting clocks.
Erin Joe writes that ransomware and nation-state attackers run campaigns against thousands of victims, not just one.
Security professionals, data analysts, attorneys, and government agencies can draw on their experience to support victims through an incident.
The post thanks Wiley Rein LLP and Pamela Signorello for a conversation with Lyn Brown about decades of experience helping clients understand, prepare for, and navigate cyber threats, issues, and incidents.
For brands planning a campaign
For a cybersecurity legal services firm, this post offers a client-facing message about coordinated incident response. It can shape webinar messaging around the roles of counsel, analysts, and agencies, and introduce legal services as part of a broader response ecosystem.
What does hands-on cyber-incident preparation look like?
Read more
Erin Joe offers a compact checklist that frames their incident-response advice.
Erin Joe lists six aspects of preparing for a significant cyber incident: crisis management preparation; leader preparation; people, not plans, get you through challenges; understanding scope and scale; leveraging the ecosystem; and rallying with people who have gone through it many times before. The post credits Pamela Signorello for questions that raise awareness of the real challenges in cyber response.
For brands planning a campaign
This post can anchor a preparedness webinar, with modules on leadership readiness, people, scope, the ecosystem, and experience. It gives firms a concrete structure for a client-facing session on incident response.
How should organizations handle reporting ambiguity when they have 72 hours or less to report a cyber incident?
Read more
Erin Joe shares specific observations on regulatory reporting.
At a panel during INMA's Congress honoring 30 years of the FBI's InfraGard program, Erin Joe shared four observations for organizations.
Many of the 200+ attendees had three or more mandatory reporting requirements for cyber incidents; Joe recommends mapping them in advance.
Some organizations do not involve cyber legal counsel immediately after discovering a potential incident; Joe recommends securing cyber counsel and asserting privilege immediately over legal advice and deliberations.
Many organizations still need to establish and practice internal decision-making processes for the issues an incident creates; Joe recommends identifying clear leadership and resources for every workstream.
An organization's decision about when the clock starts may differ from the regulator's, so Joe recommends documenting the decision and gut-checking it with experienced counsel.
Fellow panelists included Dan Adams, Andy Maus, Neal Schubert, and Michael Carr.
For brands planning a campaign
This post supports a webinar on incident-response preparedness and regulatory reporting.
It offers four ready-made modules: map mandatory reporting requirements, involve cyber counsel and address privilege early, practice internal decision-making, and document the reporting-clock decision.
Firms can use these points to demonstrate practical judgment rather than offer generic compliance advice.
What happens after a data compromise in satellite, telecom, or defense work?
Read more
Erin Joe focuses on these industries and on the part of incident response that often costs the most.
Mark Holmes contacted Erin Joe about 10 years ago, when CyberSat Summit was forming, with a vision of building a network across cybersecurity, satellites, and government partners.
Joe has served as a supporter and advisor since.
They describe moving from the FBI to Mandiant and Google Cloud, where their focus was sharing new and novel cyber attack types, and now working as an attorney at Wiley Rein LLP serving clients in critical infrastructure, including telecom, satellites, and government contractors.
Joe plans to host a roundtable on the long tail of handling a data compromise, which they call often the most extensive, unexpected, and costly part of a compromise.
Satellite and defense industries may have to report not only an incident but also specifics about exposed data.
Joe plans to share lessons on preparing for customer and government relationships and requirements after an incident.
The roundtable is listed for November 2 at 11:30am at the Hyatt Regency in Reston, Virginia.
For brands planning a campaign
For a satellite, telecom, defense, or critical-infrastructure brief, this post shows Erin Joe's domain expertise and ability to lead a roundtable on post-incident reporting and relationship management. It supports a campaign focused on the long-tail costs of data compromise, exposed-data reporting, and government and customer obligations—not just initial breach response.
Format: panel conversations, roundtables, and checklist takeaways5
Responding as part of an ecosystem, with people over plans2
Cyber incident reporting deadlines and privilege decisions1
The long tail of a data compromise in telecom, satellite, and defense work1
Career paths and purpose-driven leadership in law, national security, and cyber1
Cyber incident reporting deadlines and privilege decisions
Erin Joe's InfraGard/INMA panel recap reports that most of the 200-plus attendees had three or more mandatory cyber incident reporting requirements, and that not every organization brings in cyber legal counsel as soon as it discovers a potential incident.
Read more
The recommendations: map reporting obligations in advance; secure cyber counsel and assert privilege over legal advice and deliberations early; establish and practice internal decision-making, with clear leadership for each workstream; and document when a reporting clock starts, since a regulator may interpret the trigger differently.
For brands planning a campaign
This is the strongest fit for a webinar on incident response preparedness and regulatory reporting: Erin Joe can frame the session around the four panel findings and lead attendees through a reporting-map and clock-decision exercise.
The long tail of a data compromise in telecom, satellite, and defense work
At CyberSat, Erin Joe describes hosting a roundtable on the often extensive, unexpected, and costly period after a data compromise.
Read more
Satellite and defense organizations may have to report not only the incident but also specifics about exposed data, then manage customer and government relationships and requirements. The post says Joe shares lessons learned and preparation steps, drawing on time in the FBI, Mandiant, and Google Cloud and current work as an attorney serving critical infrastructure clients, including telecom, satellites, and government contractors.
For brands planning a campaign
A webinar segment on post-incident obligations beyond initial notification would address a gap many clients underprepare for. Erin Joe's sector-specific examples can pair with a preparation checklist for customer and government reporting.
Responding as part of an ecosystem, with people over plans
Two posts frame cyber response as a team and ecosystem problem.
Read more
One notes that ransomware and nation-state attackers run campaigns against thousands of victims at once, and that security professionals, data analysts, attorneys, and government agencies can bring experience to support victims.
The other lists preparation priorities: crisis management and leader preparation, understanding scope and scale, leveraging the ecosystem, and rallying with people who have been through incidents many times.
Its central point: people, not plans, get organizations through challenges.
For brands planning a campaign
Supports a practical webinar module on assembling the response team and running a crisis-management rehearsal. A legal-services firm can position its attorneys as part of the response ecosystem alongside security and government partners.
Career paths and purpose-driven leadership in law, national security, and cyber
In a National Security Institute event post at George Mason University's Antonin Scalia Law School, Erin Joe describes an English-major and attorney background that did not predict a career in national and cyber security leadership.
Read more
The discussion covers navigating careers across law, national security, cyber, and policy; knowing whether you are on the right track; overcoming adversity; and purpose-driven leadership and public service.
The career discussion focuses on professional development and purpose, not incident response or regulatory reporting.
For brands planning a campaign
This topic is a weaker fit for the incident-response webinar brief. It better suits a recruiting, mentorship, or public-service thought-leadership session for early-career lawyers and policy professionals.
Format: panel conversations, roundtables, and checklist takeaways
Erin Joe's posts center on events and moderated conversations: contributing to an INMA/FBI InfraGard panel, hosting a CyberSat roundtable, joining a Wiley Rein conversation with another attorney, and speaking at a university national-security event.
Read more
The recurring format is a short post summarizing a discussion and ending with a practical list, such as four panel takeaways or six preparation points.
Reviewed five LinkedIn posts: two event or panel posts, two event-conversation recaps, and one panel-lessons post with a four-point checklist.
For brands planning a campaign
Plan a moderated webinar with a co-panelist rather than a solo lecture, and ask Erin Joe for a closing list of takeaways for a client handout.
Erin Joe's posts mention the law-firm employer at the time of posting, three earlier employers, an advisory role with one conference, and panel appearances with two organizations.
Wiley Rein LLP
Employment
Erin Joe describes their work as an attorney at Wiley Rein LLP, serving critical-infrastructure clients in telecom, satellites, and government contracting.
Read more
A separate post thanks the firm for hosting a conversation on preparing for and navigating cyber incidents.
A conference organizer approached Erin Joe about a decade before this post.
Read more
They say they have supported and advised CyberSat Summit since, and will host a roundtable on the long tail of handling a data compromise at the November 2 event in Reston, Virginia.
Erin Joe was a panelist at INMA's Congress honoring 30 years of the FBI's InfraGard program.
Read more
The post's findings: most attendees faced three or more mandatory incident-reporting requirements, not every organization involves cyber counsel immediately, and internal decision-making often needs more practice.
Erin Joe joined the National Security Institute at George Mason University's Antonin Scalia Law School for an October 13 discussion, "The Mission Generation: Careers, Purpose, and National Security," with Jamil Jaffer and Arun Gupta.
Read more
They discussed career paths in law, national security, cyber, and policy.
Erin Joe's posts help readers track how organizations prepare for a cyber incident and handle its legal and regulatory aftermath.
Read more
Start with the InfraGard/INMA panel recap on reporting clocks, counsel, and privilege; the cyber response checklist on crisis management and leader preparation; and the CyberSat roundtable post on the long tail of a data compromise in telecom, satellite, and defense work.
For a career-focused perspective, the National Security Institute conversation covers non-linear paths into law, policy, and national security.
The comparison list below points to other attorneys writing about cyber incident law, international attribution, and executive-level cyber briefings.
Cyber incident responseIncident reporting deadlines and legal privilegeCritical infrastructure securityPost-incident recovery and stakeholder relationshipsCyber and national security careersPanel discussions and roundtablesPractical checklistsCybersecurity and privacy lawyersCritical infrastructure and government contractor teams
Giulio Coraggio
Coraggio writes about the legal questions that follow a breach investigation: when the compromise started, what data was reachable, whether protection was reasonable, and whether the facts are established enough to notify authorities.
Read more
In one post, he uses a ransomware takedown to show how misconfigured cloud access becomes a legal matter, addressing the same timeline problem Joe raises. Both treat the reporting clock and what was known as central questions, not technical afterthoughts.
Coraggio works from the European regulatory side, building analysis around GDPR, NIS2, DORA, and CRA obligations.
Erin Joe works from the U.S. side, where privilege, cyber counsel, and law-enforcement relationships shape the response.
Coraggio also covers technology-driven legal change more broadly; Joe stays closer to incident preparation and sector-specific reporting.
Giannoni-Crystal treats cyber operations as a legal attribution problem, explaining through doctrine when a non-state group's conduct can be tied to a state under the ARSIWA articles.
Read more
Like Erin Joe, she ends posts with takeaway points and directs readers to her longer work for the fuller argument.
Her focus is international law, attribution, and space law, including satellites and lunar resource questions, rather than U.S. incident reporting or post-incident client relationships. Her posts read as doctrinal commentary with paper citations, while Erin Joe's are practitioner notes from panels and client conversations.
Cordero briefs senior executives on nation-state threats and breach costs, then gives them numbered questions for their CISOs on frameworks, backup testing, vulnerability monitoring, and BEC controls.
Read more
The format resembles Erin Joe's four panel takeaways and six preparation points: a short written summary followed by a practical list a leadership team can act on.
Cordero's material is a structured executive education program on threat actors and security controls for boards and CISOs.
Erin Joe focuses on the legal and reporting side of an incident and the relationships that follow it.
For a legal services firm planning a webinar on incident-response preparedness and regulatory reporting, the question is reach and relevance, not follower volume.
Read more
Erin Joe’s LinkedIn profile shows 4,930 followers as of October 9, 2026—a small professional audience rather than a mass channel.
Five posts from October 1–5, 2026, offer short practitioner notes on incident reporting clocks, privilege and cyber counsel, and critical-infrastructure obligations.
One post says the INMA Congress panel drew 200+ attendees.
The topics signal a fit with security, legal, and compliance practitioners, but don’t verify who follows or reads the posts.
Before booking, ask for recent results on comparable topics, depth, and formats; per-post engagement and video performance; and any audience survey or platform demographic report covering geography, age, gender, employer, occupation, job seniority, or company size.
Erin Joe's posts describe their participation in panel discussions and roundtables with INMA/InfraGard, CyberSat, the National Security Institute at George Mason University, and Wiley Rein.
Read more
They do not specify sponsorship terms, pricing, deliverables, audience guarantees, or an inquiry process. Buyers considering a campaign should confirm whether paid or sponsored collaborations are available, along with the format, requirements, and contact route, before planning.
A cybersecurity legal services firm wants to run a client-facing webinar on cyber incident response preparedness and regulatory reporting.
Reasons
The posts offer a ready structure for a campaign on incident response and regulatory reporting. In the InfraGard/INMA panel recap, Erin Joe reports that many of the 200-plus attendees had three or more mandatory cyber incident reporting requirements; not every organization brings in cyber legal counsel as soon as it discovers a potential incident; organizations still need to practice internal decision-making, with clear leadership for every workstream; and an organization's view of when a reporting clock starts may differ from the regulator's. The accompanying recommendations — map obligations in advance, secure cyber counsel and assert privilege early over legal advice and deliberations, assign leadership and resources per workstream, document the clock decision and gut-check it with experienced counsel — are practitioner observations from a panel, not generic compliance filler.
A second post offers a six-point preparation frame to open a session: crisis management preparation, leader preparation, the point that people rather than plans carry an organization through a challenge, understanding scope and scale, leveraging the ecosystem, and rallying with people who have been through incidents many times before.
A third post extends the topic beyond initial notification to what Erin Joe describes as often the most extensive, unexpected, and costly phase: reporting specifics about the exposed data as well as the incident, then managing customer and government relationships and requirements. The post names telecom, satellites, and government contractors, giving the webinar a defensible client segment.
A fourth post frames cyber response as a team problem, naming security professionals, data analysts, attorneys, and government agencies as an ecosystem that supports a victim. This positions a law firm as one part of the response rather than the whole answer — a credible message for a legal services firm to sponsor.
The format evidence supports the ask. Erin Joe's reviewed public material features panels, roundtables, moderated conversations, and posts that end with short practical lists, including a four-point panel checklist and a six-point preparation list. A moderated client webinar fits the documented formats better than a solo lecture.
One post falls outside a campaign on incident response or regulatory reporting: the National Security Institute talk on career paths and purpose-driven leadership focuses on professional development. It could support an attendance or early-career angle, but not core content.
Two constraints should shape the plan. The posts state only one audience figure: 4,930 LinkedIn followers, observed October 9, 2026. With no per-post engagement counts, plan for a modest, qualified professional audience rather than a large one; the realistic growth path is co-marketing to the firm's own client list. The posts do not list sponsorship formats, pricing, deliverables, audience guarantees, or an inquiry route. Confirm speaking terms, fee, and contact route directly before building the plan.
When to choose a specialist
Poor fit.
Read more
Brief
A consumer cybersecurity product or mass-market brand wants a high-reach awareness campaign judged on impressions and total audience volume.
Reasons
The posts state one audience figure: 4,930 LinkedIn followers, observed October 9, 2026. That is a small professional audience, not a mass channel.
The five posts are short practitioner notes for security, legal, compliance, and government-contractor readers, covering incident reporting clocks, privilege and cyber counsel, critical-infrastructure obligations, and post-incident data-compromise handling.
The posts provide no audience geography, age, gender, employer, occupation, job seniority, or company size, and no per-post engagement counts, video performance data, or platform demographic report. Ask for verified audience composition before underwriting a volume campaign.
The formats shown are event announcements, event-conversation recaps, and checklist posts, rather than broadcast, high-volume, or entertainment formats.
No sponsorship formats, priced deliverables, or audience guarantees are documented. Confirm the commercial terms before considering a paid high-volume campaign.
A worked campaign example
Angle
The 72-hour reporting clock: what to decide before an incident. A 45-to-60-minute client webinar hosted by the firm, with Erin Joe as featured speaker and one firm attorney as co-panelist and Q&A partner.
Open items
The posts do not list a speaker fee, deliverables, inquiry route, or audience guarantee. Confirm terms, format, and contact route directly, and ask for recent results on comparable topics, session length, and formats before booking.
No transcript or long-form writing was available to preview the session's depth from a published article or recording.
Set registration expectations against the 4,930-follower audience in evidence. The realistic path to attendance is co-marketing to the firm's client list, rather than relying on the creator's own reach.
Structure
Open with six preparation checks: crisis management and leader preparation, people rather than plans, understanding scope and scale, leveraging the ecosystem, and rallying with people who have handled incidents many times. This sets the frame without a compliance lecture.
Reporting map: most attendees at Erin Joe's InfraGard/INMA panel had three or more mandatory reporting requirements. Walk clients through mapping their obligations by regulator and jurisdiction in advance, and show what an unmapped obligation can cost during an incident.
Counsel and privilege: discuss the observation that not all organizations involve cyber legal counsel immediately after discovering a potential incident, and the recommendation to secure cyber counsel and assert privilege early over legal advice and deliberations.
Decision-making and leadership: discuss the observation that many organizations still need to establish and practice internal decision-making for the many issues an incident creates, and the recommendation to name clear leadership and resources for every workstream.
The clock decision: explain that an organization's view of when a reporting clock starts may not match the regulator's, and recommend documenting the decision and gut-checking it with experienced counsel.
The long tail: for telecom, satellite, defense, and government-contractor clients, cover post-incident reporting of specifics about exposed data, plus the customer and government relationships and requirements that follow. Erin Joe describes this phase as often the most extensive, unexpected, and costly part of a compromise.
Close with the ecosystem framing — security professionals, data analysts, attorneys, and government agencies supporting one victim — and a short list of takeaways the firm can turn into a one-page client handout.
Why it works
The posts pair moderated conversation with checklist takeaways, making a two-person panel a better fit than a solo lecture. The content is specific and first-hand, not general compliance advice, and can tie directly to a short client-facing deliverable.
The four client-facing modules map one-to-one onto the reviewed panel observations and recommendations, so the session relies almost entirely on verified claims about Erin Joe's work.
When a webinar needs to focus on European reporting regulations, Giulio Coraggio’s posts speak directly to that decision.
Read more
One works through the KillSec ransomware takedown and the legal questions that arise alongside the technical investigation: when the compromise began, what data and which jurisdictions were affected, whether reasonable protection can be shown, whether personal data was exfiltrated, whether the actor remains in the systems, and whether enough is known for a preliminary notification.
Another connects AI-assisted vulnerability discovery to a compressed timeline for establishing when a vulnerability became an incident, tying that timeline to GDPR, NIS2, DORA, and CRA duties.
For a legal services firm whose clients face EU notification regimes, this material is better suited to a campaign for those clients than a US-centric incident-response session.
The cloud-misconfiguration example also gives the session a concrete failure mode to open with.
The frame is European and regulatory, focused on reporting duties rather than crisis leadership, privilege, or government contractors.
Firms serving US critical-infrastructure clients or government contractors—or running a webinar on privilege decisions and when the US reporting clock starts—will find less relevant material here.
The posts also lack the moderated-panel and checklist formats featured in Joe’s posts.
When a campaign concerns attribution, state-sponsored operations, or clients in the satellite and space sector, Francesca Giannoni-Crystal’s work is the sharper match.
Read more
One post examines the legal attribution of Handala’s reported attacks, arguing that the use of Starlink connectivity does not change the analysis under ARWSIA Articles 4, 8, and 11, and cites a published law review article on cyberattacks on satellites.
Another, from a space-resource program, lists several published papers on lunar development and space resource utilization.
A firm advising space, satellite, or defense clients on the international-law side of a cyber incident would get specific, citable material rather than general preparedness advice, backed by a published scholarly record.
The emphasis is attribution and legality under international law, not the operational reporting clock, privilege decisions, or internal decision-making needed for a preparedness-and-reporting webinar.
The focus on space and satellites is narrow for a general incident-response audience, and the posts offer fewer practical takeaways than Joe’s panel recap.
The posts span March and May 2026, leaving a thin picture of current themes.
When a webinar targets boards and executives and needs a governance frame, Pete Cordero’s posts are built for that room.
Read more
The two posts, part of a “Hacking The Cyber Threat” program update, lay out numbered questions executives should ask their CISOs.
They cover ransomware, the cost of a breach, notable data-breach examples, nation-state actors including Volt Typhoon and Salt Typhoon, the six NIST CSF 2.0 functions, mobile and application access, business email compromise and the FBI’s IC3 recovery route, threat hunting, and whether leadership has resourced the security function.
A legal services firm that wants clients to leave with a question list for their boards gets a ready structure; the InfraGard, ISAC, and sector-body tags name the audiences a webinar could target.
The material is organized around executive questions rather than legal analysis, so it offers less on privilege, reporting duties, or the notification-clock decision that anchors Joe’s fit for a legal-services webinar.
The posts, dated June 2025, read as a training-program update and are older and more list-driven than the recent panel-based content.
Ask about audience size, format history, and commercial availability.
Erin Joe's five LinkedIn posts published by October 9, 2026, cover an incident reporting and privilege panel hosted by INMA in connection with InfraGard's 30th-anniversary Congress, a crisis-preparation checklist, a recap of a cyber response conversation, a CyberSat Summit roundtable on the long tail of a data compromise in telecom, satellite, and government-contractor work, and a National Security Institute careers discussion at George Mason University.
The posts are more than titles or snippets.
LinkedIn showed 4,930 followers on October 9, 2026.
Posts from three other cybersecurity attorneys help explain nearby writers and how Joe's material differs.
Several gaps remain, and they shape what this page does not claim.
Joe's posts do not include transcripts, video, long-form articles, a media kit, or audience demographic or engagement data, so an account of their work rests on short written posts and the on-stage conversations those posts describe.
The posts do not establish whether Joe has authored a book or other signature work that would explain additional name-search interest.
No sponsor terms, fees, or inquiry route appear in the posts here, so readers who want to plan a project should confirm those directly.
These posts do not support claims about Joe's work beyond what they describe.
