So what's all this then?

I figured I'd take a stab at writing a simple blog for the same reason why a lot of people write blogs, produce podcasts, or develop other media.  While there is a LOT of great information security content out there, sometimes it doesn't speak for me: Doing InfoSec at an SMB (no, the OTHER SMB) - a small to medium sized business.  An Information Security Program where dedicated security staff headcount is in single digits and where things like "dedicated internal red team", "SANS courses passed out like candy" or "absolute best of breed tools in every corner of our environment" are fantasy. 

Your definition of "Small to medium" will of course vary.  I consider my organization to be well funded considering it's size, and some of the content I plan to post relates to the security stack of this company called Microsoft.  No, seriously: Defender for Endpoint, Azure Sentinel and other tools have been immensely helpful to me while I've been frustrated by the lack of broad knowledge out there.

So thanks for joining me on this journey, and feel free to hit me up on Twitter at @TinyInfoSec
   

Comments

Post a Comment

Popular posts from this blog

MS 365: Handilng False Positives Is Two Step Process on the Back End

Today in "weird things I just noticed", I was looking at a group of messages falsely flagged as Junk Mail in the Explorer (within the 365 Defender portal).  I selected the messages, clicked Message Actions, and then Report Clean.  All done? Not quite.  If you do this within Outlook, your message is reported and automatically moved to the Inbox.  In Explorer, you then need to separately take the action "Move to Inbox"- which presents a Remediation wizard to document what you're doing and set the priority.  Once complete you can go to the Action Center to track process. That's fine, I see where Microsoft is coming from since it's a back-end administrative action that involves getting hands within someone's mailbox.  It's just something to keep in mind if you identify a source of false positives in email filtering.
Read more

Microsoft Sentinel - Hunting for Single Character Filenames

 Hackers, the good ones and the evil ones, are lazy.  In the interest of fewer keystrokes they will use filenames with single characters (e.g. "f.exe" or "2.ps1").  So this short but sweet query will help you find potentially problematic executables: let allowlist = datatable (DName:string) ['because you are going to have exceptions','Put em here']; let allowarray = allowlist | summarize make_set(DName); DeviceProcessEvents | where FileName matches regex @'^.\.[eE][xX][eE]' or FileName matches regex @'^.\.[pP][sS][0-9]' or FileName matches regex @'^.\.[cC][mM][dD]' or FileName matches regex @'^.\.[cC][oO][mM]' | where SHA1 !in (allowarray) | project AccountName, DeviceName, SHA1, FileName, FolderPath, InitiatingProcessAccountName, InitiatingProcessAccountUpn   I was reminded of this when reading this tweet from @GossiTheDog and @h2jazi, but please note that the above query will NOT de...
Read more

Active Directory Identity Protection Alerts & Using Microsoft Sentinel For the Deets

Image
 Ever get one of these? An alert that says "User at Risk Detected... We detected a new user with at least high risk in your [company] directory.  This might be because we noticed suspicious account activity or we found their emails and passwords posted in a public location." This is Azure AD Identity Protection at work.  But if you click on "View Detailed Report" to dig into the risk events, you may get the rather vague "Unfamiliar Sign in Properties" as the source of the alert.  But.what property in particular caused this alert?  The portal doesn't seem to say. The good news is you may be able to find the answer in Sentinel.  Use this query to look at the high risk detection: //The details on identity protection risk detections, highlighting what you're probably looking for @tinyinfosec May, 2022 //Then go back to SignInLogs to review all recent signins in context SecurityAlert | where ProductName == "Azure Active Directory Identity Protectio...
Read more