It's #TableTopTuesday On Twitter | What Serious Silliness Did We Spot While Redefining Security With Meg Hargrove?
Manage episode 291500333 series 1535672
Unless there's a plan that's been practiced, one's gut reaction is probably how things will roll when an incident occurs. #TableTopTuesday on Twitter from Meg Hargrove captures some of those "moments" — let's discuss.
Before we do, though, do any of these sound like your go-to first step during a cyber incident?
- “Brown alert”
- “Cry for a minute”
- “Update resume”
While there may get a chuckle from someone looking in on a fake situation presented on social media, incident response is no joking matter when real life is at stake. And that's why I wanted to have a conversation with @cybersecmeg — what she is doing with #TableTopTuesday on Twitter is nothing short of brilliant: present an incident use case and get feedback from the community for how they would respond.
There's no single right nor wrong answer, of course. And, the conversation doesn't just stop abruptly with an answer either — there's some good dialog from the community, presenting some solid options and some meaningful back-and-forth as the scenario unfolds.
Take this scenario, for example:
Credentials for your AWS cloud environment have been accidentally left hard coded into a PUBLIC GitHub repository. You check your cloud portal and find $75K worth of spend not created by your org. What do you do?
Well, time us up. The incident is happening. What do you do? What should you do?
First, listen to this chat with Meg and then check out the #TableTopTuesday threads to start planning and practicing.
Meg Hargrove, Cybersecurity Incident Response Manager (@cybersecmeg on Twitter)
This Episode’s Sponsors
Inspiration for this conversation:
To see and hear more Redefining Security content on ITSPmagazine, visit:
Are you interested in sponsoring an ITSPmagazine Channel?