Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://digitaldarkage.cc/users/iaintshootinmis/statuses/113192286227491172">IAintShootinMis (iaintshootinmis@digitaldarkage.cc)'s status on Tuesday, 24-Sep-2024 20:35:36 JST</a><a href="https://digitaldarkage.cc/@iaintshootinmis" title="iaintshootinmis@digitaldarkage.cc"><img src="https://gnusocial.jp/avatar/103494-48-20230302104853.webp" width="48" height="48" alt="IAintShootinMis" style="position: absolute; left: 0; top: 0;">IAintShootinMis</a><div><ul><li></ul></div></section><article><p><a href="https://cyberplace.social/@GossiTheDog">@GossiTheDog</a> respectfully sir, and I mean this sincerely (your toots are considered Infosec scripture in this house), I argue there's a lot to do and I've been doing it. (Its in my Troop Leading Procedures thread here: <a href="https://digitaldarkage.cc/@iaintshootinmis/113189506131608638" rel="nofollow noreferrer">https://digitaldarkage.cc/@iaintshootinmis/113189506131608638</a> )</p><p>I can't put mitigations in place, or start patching, but we can brace ourselves and partners for the oncoming Storm.</p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/3718544#notice-7282957">In conversation</a><time datetime="2024-09-24T20:35:36+09:00" title="Tuesday, 24-Sep-2024 20:35:36 JST">about 9 months ago</time> <span>from <span><a href="https://digitaldarkage.cc/@iaintshootinmis/113192286227491172" rel="external" title="Sent from digitaldarkage.cc via ActivityPub">digitaldarkage.cc</a></span></span><a href="https://digitaldarkage.cc/@iaintshootinmis/113192286227491172">permalink</a><h4>Attachments</h4><ol><li><article><header><div>No result found on File_thumbnail lookup.</div><h5><a href="https://digitaldarkage.cc/@iaintshootinmis/113189506131608638">IAintShootinMis (@iaintshootinmis@digitaldarkage.cc)</a></h5><div> from <span>IAintShootinMis</span></div></header><div>I had several people I know tell me they weren't doing anything about #EvilSocket 's potential disclosure because it was inactionable. I wish I were at a keyboard right now. But of course its actionable! In the military we often received warning orders and we always followed our troop leading procedures. Heres a break down of those and how they apply to your role in #InfoSec A 🧵.</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
IAintShootinMis (iaintshootinmis@digitaldarkage.cc)'s status on Tuesday, 24-Sep-2024 20:35:36 JSTIAintShootinMis
- Kevin Beaumont
@GossiTheDog respectfully sir, and I mean this sincerely (your toots are considered Infosec scripture in this house), I argue there's a lot to do and I've been doing it. (Its in my Troop Leading Procedures thread here: https://digitaldarkage.cc/@iaintshootinmis/113189506131608638 )
I can't put mitigations in place, or start patching, but we can brace ourselves and partners for the oncoming Storm.
In conversationabout 9 months ago from digitaldarkage.ccpermalink
Attachments
1. No result found on File_thumbnail lookup.
  IAintShootinMis (@iaintshootinmis@digitaldarkage.cc)
  from IAintShootinMis
  I had several people I know tell me they weren't doing anything about #EvilSocket 's potential disclosure because it was inactionable. I wish I were at a keyboard right now. But of course its actionable! In the military we often received warning orders and we always followed our troop leading procedures. Heres a break down of those and how they apply to your role in #InfoSec A 🧵.

Public

Embed Notice

HTML Code

Corresponding Notice