@CptSC Security is constantly blamed because ops or iam implemented something without doing impact analysis and breaks something. When people dont know whats wrong, they always blame security.
🔥 Maester 2.0 is LIVE! 🚀
And this one’s big.
💥 Over 1,000,000 Microsoft tenants have now used Maester 🤯.
An insane milestone that shows what happens when open-source meets real enterprise impact. Yes, that's not a typo. Maester has been used in over 1 million tenants.
God fortsättning, 2026 blir ett spännande år för Cantargia tror bolaget har goda chanser att uppnå alla dagens riktkurser (7-14kr)
Närmst väntar jag på en milestone utbetalning från Otsuka som fyller på kassan ytterligare som redan idag räcker över 2 år
$CANTA #IL1RAP
I just learned that AdminByRequest has a secure remote access solution with a container image for web access and Cloudflare tunneling to reach the destination machines. Has anyone tried it? What are your thoughts? adminbyrequest.com/en/secure-remo…
@CptSC@NathanMcNulty I wonder if I should just signup with a personal email account for the free tier. Can the EPM product be fully self-hosted or is it always dependent on a cloud service somewhere?
@awakecoding I don't think so, and you need their cloud console for configuration and reporting anyway
I loved working with their API many years ago, built a bunch of reports so we could remove admin rights from the few hundred users that had it
Hey community, how do you manage your monthly server patching? For a 24hr shop, how do you manage server maintenance windows, patching, rebooting, etc? We’ve moved from #ConfigMgr to #Azure update manager and we use extension attributes to designate “patch codes” which dictate which patch window/group a server is in. Then we have a server team spending a night managing patching. Is this normal? We’ve got about 1200 servers globally.
@DecryptedTech@CptSC@IAMERICAbooted I'm embarrassed I don't know this. Would you still require, at least, all 2019 DCs and then run a command to upgrade?
@IAMERICAbooted Get-ADObject (Get-ADRootDSE).schemaNamingContext -Property objectVersion |
Select-Object -ExpandProperty objectVersion
88 and below should mean that badsuccesor is no issue. Permissions over msDS-KeyCredentialLink would still be problematic. SpecterOps has a write up I think
So, to catch you up in case you missed the akamai post, it's still exploitable after the patch, especially if you control an OU object with write permissions. But ky understanding is it needs the correct schema version to exploit it. I have patch to OU control from low privilege so I want to be sure.