Check first: Confirm media kit, rate card, sponsorship example, inquiry route, and independent verification of the 506% figure.
Main ideas
Explain the design decisions behind security, not the threat headlines · Put the engineers and researchers in front instead of the communicator · Treat a flagship conference as a launchpad, not a logistics exercise
Lise Feng works in security communications at AWS, developing stories about security innovation and how it can help customers protect their environments.
Their posts trace a path from PR work for cybersecurity startups to explaining cloud security for broader audiences.
Follow their work for examples of how technical topics—from encryption and infrastructure to AI-agent permissions—can be framed through concrete technologies, experts, and customer concerns.
Feng’s distinctive contribution is connecting technical security details to clear communications formats.
One post names Nitro, AWS KMS, and Bedrock AgentCore Identity to illustrate a broader point about investing in security architecture; another describes a re:Invent media panel on securing AI as customers move from experimentation toward production.
The posts also show program-level work: Feng reports a 506% year-over-year increase in security stories and credits collaboration with security leaders and reporters.
Ask for supporting data behind the reported figure.
Lise Feng works in security communications at AWS.
Read more
Across the three posts reviewed here, they argue for leading with how defences are built and who built them, rather than the threat of the week, and for putting the company's engineers and researchers in front of the story. They also prioritise quieter coverage of research and defensive advances over breaches, supported by reporter relationships that help get it published.
Explain the design decisions behind security, not the threat headlines
Feng makes security legible by explaining architectural choices and what each does for customers, rather than leading with an attack or vulnerability.
Read more
The AWS anniversary post frames security as a long-term investment made ahead of a threat, with engineering decisions explained for a business audience.
The anniversary post highlights three structural examples: Nitro reworking the hypervisor to isolate operator access from customer data; AWS KMS as a fully managed, cloud-native key management service using symmetric encryption; and authentication controls such as Amazon Bedrock AgentCore Identity that enforce permissions for AI agents.
Put the engineers and researchers in front instead of the communicator
Across the posts, Feng describes organising storylines, access, and formats while others provide the technical perspective.
Read more
Credit extends to the experts who make the argument and the collaborators thanked by name for their work behind a programme.
The anniversary post directs readers to perspectives from Eric Brandwine, Gee Rittenhouse, and Ken Beer, then closes with a long list of named internal collaborators, including Chris Warfield and Jeremy Bartram, credited for collaborating from day one.
The posts credit these people as sources of technical perspective but do not specify their roles.
Ask for their roles if that matters to your brief.
Treat a flagship conference as a launchpad, not a logistics exercise
Feng's account of a year in the role describes building a news cycle around re:Invent, not just attending it: inventing a press format the conference had not offered before and measuring the result against the previous year.
Read more
For re:Invent 2025, Feng reports organising the conference's first-ever security panel for media.
AWS security leaders explained how customers defend their environments as they move agentic AI from experimentation into production.
Feng also reports a 506% increase in security stories over the previous year; the figure is their own, given in the post.
The earlier arrival post states Feng's aim: joining AWS to support the security business by inventing compelling storylines. The one-year reflection shows what that produced in practice: a new media format and a reported jump in story volume.
Pitch the non-threat news, and cultivate reporters so it has somewhere to go
Feng prioritises security work that is not an incident: research, defensive advances, and stories that do not lead with a breach.
Read more
They present sustained reporter relationships as essential to securing coverage, alongside internal experts who can speak to the work.
Feng thanks reporters “old and new” for hearing out non-threat research news and credits dozens of internal collaborators across security, PR, and business teams in the same post.
The moment worth covering in AI security is the move into production
These posts frame AI security as a deployment problem, not a novelty.
Read more
The key question is what changes when an experimental agent becomes a production system with real permissions, and how identity and permission controls keep it within bounds.
Feng describes security leaders explaining how AWS helps customers defend their environments as they move agentic AI from experimentation to production. They cite AWS AI security agents and controls such as Amazon Bedrock AgentCore Identity as mechanisms for enforcing permissions.
Regulation and changing posture are what make security worth following
Feng's account of entering the field distinguishes security's attention-grabbing side from what sustained their interest.
Read more
Heists, sabotage, and vulnerabilities drew their initial attention; the deeper pull was how defences and compliance rules are designed to protect assets. That is also the frame they use to explain why security matters to businesses.
Feng describes starting a cybersecurity communications career as the extra intern staffing a PR agency's anti-virus, authentication, and encryption startup accounts. They write that changing security postures and compliance regulations designed to protect valuable assets deepened their interest.
Answers what Lise Feng does and how they entered security communications.
Read more
A newcomer should start here: it traces their path from agency intern work on security startup accounts to in-house storytelling at AWS.
This is an arrival and positioning post.
Lise Feng describes starting a cybersecurity communications journey as the extra intern who staffed a PR agency's anti-virus, authentication, and encryption startup accounts, then joining AWS to tell stories about security innovation.
The post frames security as a building block for modern businesses and traces a path from early interest in cyber heists, sabotages, and vulnerabilities to a deeper focus on security postures and compliance rules designed to protect valuable assets.
For brands planning a campaign
For a cybersecurity communications brief, this post shows how an origin story can make a technical career legible to a business audience. A brand could use a similar first-person narrative to explain why a security practice exists, pairing it with concrete work examples rather than relying on the career move alone.
Answers how Lise Feng translates deep technical security programs into communications.
Read more
It models a technical proof post with concrete innovations, named experts, and a clear frame about long-term architectural investment.
This post packages AWS security history into a short, source-linked explainer.
It names specific technical investments: Nitro re-imagining the hypervisor to isolate operator access from customer data, AWS KMS as a fully managed cloud-native key management service using symmetric encryption, and AWS AI security agents with authentication controls such as Amazon Bedrock AgentCore Identity to enforce permissions.
The post directs readers to perspectives from Eric Brandwine, Gee Rittenhouse, and Ken Beer.
For brands planning a campaign
A security vendor could use this structure to turn a platform milestone, anniversary, or launch into a buyer-relevant proof story. The lesson is to make an abstract security-first message inspectable through named technologies and responsible experts, rather than copying the AWS claims.
Answers what Lise Feng did in a year of in-house security communications and why it matters.
Read more
A newcomer should open it for operational detail on re:Invent media programming, agentic AI security, and the collaboration behind a security storytelling program.
This anniversary reflection marks a first year in AWS Security Innovation PR.
Lise Feng says the move from Silicon Valley to Seattle was meant to learn fast, cites the leadership principles Learn And Be Curious and Deliver Results, and reports a 506% increase in security stories over the previous year.
Part of that came from a first-ever security panel for re:Invent media, where security leaders discussed how AWS helps customers defend their environments as they move from agentic AI experimentation to production.
The post credits a long list of named collaborators and thanks reporters for hearing out non-threat research news.
For brands planning a campaign
For a PR or cybersecurity communications brief, this post shows Lise Feng working at the program level: building media events, increasing story volume, and coordinating spokespeople.
A brand planning an announcement or executive visibility push could ask about a similar panel or story pipeline.
The 506% figure is self-reported and would need separate verification before use.
Putting internal experts forward instead of the spokesperson3
Agentic AI security as a production concern, not a demo2
Security storytelling anchored in architecture, not threat headlines1
Event-driven media programs built around a flagship conference1
Reporter relationships and pitching non-threat research news1
Compliance and security posture as the deepening interest1
Forward-looking risk framing: post-quantum and emerging threats1
Security storytelling anchored in architecture, not threat headlines
Feng writes about AWS security as a long-term design choice, not a reaction to the threat of the day.
Read more
Their examples are structural: Nitro reworking the hypervisor so operator access is isolated from customer data, KMS as a fully managed cloud-native key management service using symmetric encryption, and authentication controls such as Amazon Bedrock AgentCore Identity that enforce permissions for AI agents. The through-line: security is built into the platform and explained to a business audience through concrete engineering decisions.
For brands planning a campaign
For a vendor differentiated by design rather than a feature list, Feng's approach points to a narrative that leads with how the product is built — isolation, key management, permission enforcement — then translates each choice into what it means for customers defending live environments. For a campaign targeting customers evaluating product architecture, lead with architecture first, headlines second.
Event-driven media programs built around a flagship conference
Feng's one-year reflection describes using re:Invent as the centre of a news cycle, including a first-of-its-kind security panel for conference media where AWS security leaders explained how customers were moving agentic AI from experimentation into production.
Read more
They report a 506% increase in stories compared with the previous year, attributing part of it to that experimental format.
Conference-led news cycle: a new press format plus a timely customer narrative staged at the event.
For brands planning a campaign
A cybersecurity company with a flagship event can use it as a launchpad, not just a logistics exercise: invent a format the press has not been offered before, put security leaders in front of reporters to explain a specific customer transition, and measure the resulting story volume against the prior cycle.
Reporter relationships and pitching non-threat research news
Feng thanks reporters "old and new" for hearing out non-threat research news — security work that is not a breach, a vulnerability disclosure or a hack.
Read more
The same post lists dozens of internal collaborators across security, PR and business teams.
For brands planning a campaign
Sustained press relationships can help a company earn coverage for quieter, research-driven security stories. A comms program that only surfaces incidents will miss this channel; one that cultivates reporters over time can place work explaining how defences are advancing.
Agentic AI security as a production concern, not a demo
In these posts, AI security appears as a deployment problem rather than a novelty.
Read more
Feng describes security leaders explaining how AWS helps customers defend their environments as they move agentic AI from experimentation to production, and cites identity controls that enforce permissions so AI agents stay within bounds.
For brands planning a campaign
For a company selling AI governance or agent security, the useful angle is the transition point: what changes when an experimental agent becomes a production system with real permissions. That framing gives technical buyers a reason to act now.
Compliance and security posture as the deepening interest
Feng traces a communications career that began as an extra intern staffing a PR agency's anti-virus, authentication and encryption startup accounts.
Read more
Cyber heists, sabotage and vulnerabilities drew attention, but they write that changing security postures and compliance regulations designed to protect assets deepened their interest. Joining AWS was about telling stories on security innovation as a building block for modern businesses.
For brands planning a campaign
This vocabulary suits vendors selling to regulated buyers: regulation and posture change, not incident drama, as the reason customers invest. A campaign built on that reasoning can speak to risk and compliance owners, not just incident-response audiences.
Forward-looking risk framing: post-quantum and emerging threats
Feng's post marking AWS's 20th anniversary highlights innovations positioned against emerging AI and post-quantum threats, noting that symmetric encryption remains computationally infeasible to crack.
Read more
The framing presents AWS as having anticipated threats years ahead of them.
For brands planning a campaign
A cybersecurity company can borrow this forward-looking structure: pick a threat that is not yet urgent for most buyers, show the architectural work already underway, and demonstrate that the company plans beyond the current news cycle.
Putting internal experts forward instead of the spokesperson
These posts name AWS security figures — Eric Brandwine, Gee Rittenhouse and Ken Beer among them — as sources of perspective, and credit a long list of internal collaborators and two close colleagues from day one.
Read more
Feng's role reads as organising the story and access rather than occupying the frame.
Whether this reflects a company convention or Feng's preferred working style is not established by the posts alone.
For brands planning a campaign
For a company with deep technical staff but limited media experience, this suggests using a communications partner to connect reporters with named experts, package their perspective and keep the program running across the year. The spokesperson model is one option; the expert-byline model is another, and Feng's work shows the latter at conference scale.
Lise Feng writes about how security gets explained: the architecture behind AWS security services, the engineers and researchers who can speak to it, and the reporter relationships that bring non-threat research news into print.
Read more
Three posts make a useful sequence: the arrival post explains why security communications drew Feng in, the AWS anniversary post shows the architecture-first framing, and the one-year reflection describes building a news cycle around re:Invent and a first-time security panel for conference media.
Marketers considering Feng should ask for more examples if they need to assess the breadth of their work.
The creators below cover overlapping ground from different angles: practitioner education, CISO advisory writing, and vendor-side security marketing.
Velica explains cybersecurity frameworks for a professional audience, including the 14 domains of ISO 27001 and a 17-item breakdown of audit types.
Read more
Both make security concepts legible to readers outside specialist teams and package the material as ordered lists they can save and reuse.
Velica teaches frameworks directly to practitioners in security, GRC, and compliance, building checklists they can take into an audit or review. Feng writes about communicating security: a communications program, the experts who front it, and the reporters who cover it, using architecture as an explanatory frame rather than a syllabus.
Roberts frames security as a business and leadership problem, demonstrating the business value of security investment and addressing AI, data privacy, regulatory compliance, and quantum readiness.
Read more
Feng likewise explains why architectural choices matter to a business audience. Both focus on decisions and priorities rather than exploits.
Roberts addresses CISOs, boards, and executive leadership directly, offering advisory lists and arguing that leadership continuity sustains long-term security strategy. Feng writes from inside a cloud provider about how a security story is assembled and who tells it, crediting named engineers and researchers rather than advising security leaders.
Trawick writes about security topics Feng covers — certificate lifecycle changes, post-quantum migration, and crypto-agility — for a professional LinkedIn audience, relaying industry developments and promoting events in the same short-post format.
Read more
Both explain security as an industry story for people who follow it.
Trawick's posts pair company announcements and promotions with vendor links and webinar registration calls. Feng offers reflective accounts of a communications program, including a format they helped invent and the collaborators behind it, without pitching a product.
The audience question is only partly answerable from Feng’s posts.
Read more
A buyer considering Feng for a cybersecurity communications campaign has one measured figure: roughly 2,300 LinkedIn followers as of October 2026.
The profile focuses on AWS security storytelling, suggesting modest, professional-scale reach suited to security practitioners, communications peers and industry press—not consumers or broad developer outreach.
Feng’s anniversary post names dozens of security leaders and thanks “reporter friends” for covering non-threat research news, suggesting an audience drawn from security and tech media.
The posts don’t establish audience geography, job function, seniority or employers.
Before committing, ask for recent engagement results on comparable security-storytelling posts and any audience survey or platform data on job function and seniority.
Lise Feng's three posts describe employer-side security communications work at AWS: joining to tell stories about security innovation, coordinating security leaders for a first-ever re:Invent media panel, and promoting a CSO Online piece on AWS security history with named spokespeople.
Read more
They show how Feng works with spokespeople and reporters inside a company, not a published creator offering.
The posts include no media kit, rate card, sponsored-content example, disclosure policy, or inquiry route.
Buyers should ask directly about available formats, deliverables, pricing, and process rather than assume a standard package.
Strong fit for a strategy, communications-counsel, or event-media collaboration. Not a verified paid creator sponsorship fit: no commercial format is documented.
Read more
Brief
A cybersecurity company selling cloud security and agentic AI governance wants to elevate its communications strategy: build a media program around a flagship event, explain architecture proof points to enterprise buyers, and earn coverage in security press.
Reasons
The documented work is directly on point: Lise Feng joined AWS to tell security-innovation stories and spent the first year driving a security narrative around re:Invent, including what they describe as a first-ever security panel for re:Invent media.
Feng's posts show a repeatable method for translating architecture into communications: Nitro isolating operator access from customer data, AWS KMS as managed cloud-native key management, and Amazon Bedrock AgentCore Identity enforcing permissions for AI agents.
The agentic AI angle is framed as a production problem rather than a demo — exactly the transition enterprise security buyers are trying to explain internally and to the press.
Feng works expert-forward, naming Eric Brandwine, Gee Rittenhouse, and Ken Beer as sources of perspective and crediting a long list of internal collaborators. That suits a company that wants its own security leaders in front of reporters rather than a single spokesperson.
Feng's stated interest in reporter relationships and non-threat research news fits a company trying to earn coverage for preventive security work, not only incident response.
Caveats
Before discussing a paid engagement, ask for a media kit, rate card, sponsorship example, and inquiry route.
The 506% increase in stories is Feng's own reported figure in the post; verify it independently before using it in a case study or sales claim.
Audience reach is modest and professional-scale — about 2,322 LinkedIn followers as of October 2026 — so this is not a mass-reach distribution play.
When to choose a specialist
Poor fit based on the posts here.
Read more
Brief
A consumer cybersecurity app wants a high-volume paid creator campaign: twenty short-form videos, affiliate installs, lifestyle demos, direct-to-consumer reach, and a fixed rate per post.
Reasons
The posts show employer-side B2B security communications at AWS, not independent creator sponsorship work. Before evaluating a paid campaign, ask for a sponsored-content example, disclosure policy, rate card, and format menu.
The audience figure is roughly 2,300 LinkedIn followers, a professional-scale audience rather than a consumer install-driving one.
The posts provide no evidence of video, short-form, lifestyle-demo, or affiliate performance.
The posts center on technical security storytelling and reporter relationships, not product conversion or direct-response campaigns.
Because no commercial offer is described in the posts here, proposing a fixed paid package would invent terms that the posts do not support.
A worked campaign example
Brief
For the good-fit brief, use the company's move into agentic AI governance as the news hook.
Campaign angle
Run a press-only panel at a flagship event on what changes when agentic AI moves from experimentation to production. Put customer security leaders and one internal architect on the panel; focus the story on permission enforcement, identity, isolation, and the operational decisions that keep agents within bounds. Use Feng's non-threat research-news framing to give reporters a forward-looking defense story instead of another breach headline.
Execution
Define the transition in one sentence: experimental agents become production systems with real permissions, data access, and business consequences.
Select three proof points the company can explain concretely — isolation of operator access, managed key management, and permission enforcement for agents — and prepare a one-page technical brief for each.
Convene a panel of customer security leaders plus one named company architect. Give each panelist a specific deployment decision to explain, not a product testimonial.
Pitch reporters in advance on the question 'what changes when agents get production permissions?' and offer the panel as access to practitioners who have made that transition.
Publish a short recap after the event linking the panel to the technical briefs, so buyers who were not in the room can inspect the story.
Measure qualified coverage, reporter attendance, and inbound conversations that mention agent governance — not just total mentions.
Open questions
Ask whether Lise Feng is available for a paid advisory, speaking, or collaboration role.
Verify any re:Invent story-volume figure independently before repeating it.
Request audience composition data before using Feng's LinkedIn audience for distribution; follower count alone does not show job function, seniority, or buying authority.
Choose Marcel Velica to teach security frameworks and audit structure to GRC, IT, risk, and compliance audiences.
Read more
The compact, saveable explainers — the 14 ISO 27001 domains and a 17-type audit taxonomy — bring people, process, technology, suppliers, and business continuity into one reference. For a company whose buyers need to understand how security is owned, managed, measured, and improved, that framing is more reusable than a press or event storyline.
The posts are practitioner reference lists: short definitions under numbered headings, ending with a reshare request.
They do not show reporter relationships, event media programs, or close readings of a company's architecture, so they are not a route to putting named security leaders in front of the press.
This approach trades earned-media storytelling and event coverage for evergreen framework content that practitioners save and reuse.
Choose Sandra Roberts when the audience is CISO, board, and executive level and the message is strategic: quantum readiness and harvest-now-decrypt-later risk, the business value of security investments, and board-CISO partnership on long-term roadmaps that outlast leadership turnover.
Read more
The posts also frame AI as both an attack enabler and a defensive tool. This suits a company seeking executive-level language about risk continuity rather than an event-driven media push.
The posts offer executive commentary and priority lists — top areas of focus and roadmap guidance — rather than press-program or event execution.
They show no media-relations work, panel convening, or reporter-facing activity.
This route favors boardroom framing of long-term strategy over the earned security-press coverage and flagship-event media program the campaign needs; ask for examples of that work before hiring.
Choose Duncan T. for product-led technical marketing aimed at PKI, certificate-lifecycle, and post-quantum practitioners.
Read more
The posts pair a concrete industry change — the CAB Forum approving Apple's proposal to cut publicly trusted SSL/TLS certificate lifespans from 398 days to 47 by 2029 — with a vendor call to action and webinar promotion covering crypto-agility and a recent acquisition. This fits a company that wants its own roadmap and webinars at the center of the campaign.
The posts take the vendor's perspective and tie the story to a named employer's offerings, making them promotional rather than independent editorial.
A company seeking earned press coverage and reporter relationships would get a pitch-first, product-linked approach instead of neutral, research-forward framing that puts security leaders and their architecture decisions in front of the media.
Ask for examples of independent press work before hiring.
Lise Feng's three LinkedIn posts announce a move to AWS in a security innovation PR role, discuss AWS security innovations marking the company's 20th anniversary, and reflect on one year of security PR and re:Invent media work.
The posts do not show publication dates, so claims are dated only where a post dates itself.
The 506% year-over-year increase in security stories is Feng's own reported figure and is not independently verified.
The posts do not mention signature books, shows, or businesses, and publish no commercial formats — rates, sponsorships, or an inquiry route.
Similar-creator comparisons and topic tags rest only on the posts cited for each creator, not on a full body of work.
Claims are limited to what these posts show; employers and credentials are not verified beyond them.
