CLICK HERE TO DOWNLOAD THIS IMAGE & COLOR IT IN!Inside: A rallying call for Facilitators’ incident ideas as we stock Ally’s library of ready-to-run scenarios, tales of trusted systems turned against their kingdoms, and a navigation upgrade which simplifies how you journey within our app.


We’re building a warchest and filling it with battle-tested TTX scenario templates, ready for Facilitators to use out of the box in Ally.
The aim is simple: Save you time and ensure exercise relevance by providing a deep arsenal of pre-constructed campaign scrolls to draw from. These scenarios are inspired by the kinds of incidents that have rattled kingdoms in real life. As we stock this warchest, we call to you for aid.
Send us an email with the incidents that have stuck with you most. The diabolical ones. The costly ones. The strange, cascading calamities that made everyone in the war room mutter, “Well...that’s bad.”
Tell us your favorites! They may help inspire what enters the Ally scenario library.
Your allies in IR,
Rob & Scout
P.S. Our next virtual TTX Thursday live event with guest Facilitator Gerard Johansen and co-host Diopter takes place next week on Thursday, August 20. Click here to claim your seat at the table!


Researchers found flaws that could turn AI coding agents into traitorous scribes, stealing secrets and carving paths into the software supply chain. Facilitators can use this tale to test what happens when the kingdom’s newest helper is tricked into serving the enemy. Peruse the findings
A poisoned command can leap from one AI agent to the next, carrying its curse through shared systems and spreading with each jump. Facilitators can use this creeping blight to find out whether defenders can stomp an AI worm before it overruns the kingdom. Study the curse
A parasitic flaw lurking in trusted build systems could let outsiders seize repositories, steal secrets, and taintsoftware. Facilitators can use this infestation to determine what happens when corruption manifests within the kingdom’s supply chain. Examine the parasite
A cyberattack struck everyNorth Carolina Ports location, forcing crews to manually move the realm's cargo while digital systems were healed. Facilitators can use this example to learn if teams can maintain critical operations and summon the right allies. Survey the siege


Mapped by Stacey!
We’re simplifying how accounts work in Ally. All Build, Run, and Report tools now live exclusively within Client Accounts, while your parent account serves as the central command post for managing and accessing those accounts.
Need a proving ground for internal TTXs, testing, or demos? Your organization now has its own Internal Account, complete with an “Internal TTX” badge branded in the top right corner of the account card. Any existing internal exercises and reports have already made the journey there safely, along with your org logo.
This ensures that your adventures within Ally follow a consistent process, regardless of whether you’re using it to guide internal or external parties. May this upgrade serve you well! If you haven't signed up yet, do so below and build your first scenario for free.
.webp)


That’s another one in the books! From treacherousAI scribes to leapfrogging worms, we've explored plenty of new threats to inspire your next TTX. We wish you the best in the quests to come, and we look forward to revealing Ally’s scenario library very soon.
Don’t forget to send an email with your favorite incident examples. Fare thee well!
About Ally Security
Ally is here to support facilitators, which in turn creates a virtuous cycle where exercises take less time, provide more value, are run more frequently, and can make every organization can be better prepared.
The unexpected wins. The client curveballs. The chaos you couldn’t have scripted if you tried. Dear Asa is your space to share the stories that don’t make it into the official post-incident report. Script, submit, and enjoy a chance to be featured or quoted in an upcoming post.
