Security Engineer. Ex-MEM and Jamf Pro admin. Passionate about empowering and reducing friction for end users.

Texas, USA
Joined December 2017
Colin Wilkins retweeted
BREAKING: Internal #DeepSeek database publicly exposed 🚨 Wiz Research has discovered "DeepLeak" - a publicly accessible ClickHouse database belonging to DeepSeek, exposing highly sensitive information, including secret keys, plain-text chat messages, backend details, and logs.
118
768
372
2,831
878,793
Are you ready? In just a few weeks, #Microsoft will turn on full enforcement of strong certificate mapping on domain controllers. For those unprepared, there will be outages! Wi-Fi and #VPN, most likely. #mobility #security #PKI #aovpn rmhci.co/42tr9lO
8
74
1
306
24,575
Colin Wilkins retweeted
Fun Fact!!! Going "Passwordless" doesn't protect against this Phishing attack exploiting Device Code Authorization Token theft :) aadinternals.com/post/phishi… Implement CA policies to block Device Auth Flows ASAP. Only make exceptions when required. learn.microsoft.com/en-us/en…
2
1
1
130
Colin Wilkins retweeted
Attention #ITpros 📢 As of v111, #AzureAD auth works seamlessly w/o the need for the 'Windows Accounts' plug-in. Simply grab the ADMX and enable the 'Allow automatic sign-in to Microsoft® cloud identity providers' policy. 🥳 #IdentityManagement #Intune chromeenterprise.google/poli…
4
51
2
154
18,459
Colin Wilkins retweeted
I've recently noticed that Azure AD admins are being asked to create multi-tenant apps in their corporate tenant. In some instances, it was the devs in the org asking for this, in other instances it was the application vendor. Here are some things to watch out for 👇 Multi-tenant apps are meant for ISVs and SaaS vendors to create an instance of an app in 'their own tenant'. Examples of such apps are ServiceNow and SalesForce. When an app is created as a multi-tenant app, ANY user from ANY Azure AD tenant can visit the app's url and sign in. If you create a multi-tenant app in your corporate tenant and apply a conditional access policy. The policy only applies to users in your tenant. ⚠️ I'll repeat ➟ your CA policies do not apply to users signing into your multi-tenant app in their own tenant. So, what is the general rule of thumb that Azure AD admins and cybersecurity teams should follow? If the app is from a vendor/SaaS provider: ✅ Add the app to your tenant from the Azure AD Application Gallery ✅ If the app is not in the gallery, you as the customer can request the vendor to get their app listed on the Azure AD app gallery ✅ If app gallery is not an option, request the vendor to create the app in their own tenant. Use the admin consent model to add the app to your tenant. ✅ If the only option provided by the vendor is to create the app in your tenant, push for the vendor to allow you to create a single tenant app. If the app is developed by devs in your org and is only meant for users in your own org. ✅ Ask why the dev needs this to be a multi-tenant app? ✅ Ask if the devs have implemented appropriate checks to prevent sign-ins from other tenants. There are many valid scenarios for creating multi-tenant apps in your tenant, including ✅ You are a SaaS vendor or ISV and you create and publish apps that Azure AD customers can consume ✅ You manage multiple Azure AD tenants in your org and you need a single service principle (workload identity) to access the other tenants (e.g. automate DevOps tasks across your tenants) Here are some further reading on the topic of multi-tenancy. These are meant for devs however its good reading for admins to appreciate what it takes to build a least-privilege multitenant app. 👉 learn.microsoft.com/en-us/az… 👉 learn.microsoft.com/en-us/az… Liked this post? Please retweet this to share with your network. 🚀 Feel free to follow me. I try to post at least one weekly tip related to Microsoft Identity, Azure Active Directory or Microsoft Graph. 🙏
18
136
10
500
73,044
Colin Wilkins retweeted
Well - Over the next 72 hours or so everyone will have access to EPM (aka.ms/IntuneEPMDocs). Some of you may get access earlier if you're part of another Intune preview, if you see something funky that's probably the reason. This is the beginning of our journey to help organizations run as a standard user by using the conduit already on the device, Microsoft Intune. We have a pretty rich backlog and plan on delivering a ton of value over the next 12 months. Our goal is that you don't use us just because it's built in, you use us because we're the best... and we have our work cut out for us. Our plan is to ship our first two feature pillars, User Confirmed and Automatic. We will GA those two pillars in the April timeframe. Then we will shift our sights to Support Approved in the summer timeframe. We have a lot we want to add that wouldn't fit in this release (see our deployment considerations doc page), but we're committed to fixing all of those items over the coming weeks/months. Let me know if I can help.
21
79
4
212
27,507
Colin Wilkins retweeted
You’ve hopefully done this already, but this feature isn’t enabled by default so I figure I’d mention it. Why this isn’t on by default is criminal.
1
1
Colin Wilkins retweeted
PSA… today is PatchTuesday. We started a website that aspires to have the “latest and greatest” information about each patch Tuesday. We’re just getting started… we’ll get better and more relevant each and every month… patchtuesday.com #microsoft #windows
10
81
3
277
New blog post! 📃 It will give a primer on how you can implement security boundaries in your infrastructure to prevent compromise of critical assets based on tiered administration posts.specterops.io/establis…
4
108
5
262
Colin Wilkins retweeted
Ever thought - Why does this person know a lot about hybrid join? Here's my secret - share it with everyone you know, twice -> docs.microsoft.com/en-us/azu…
3
33
102
Colin Wilkins retweeted
#Win10 Scanning: •No policies configured--> WU •WSUS configured--> WSUS •WSUS +deferrals--> WU •WSUS +deferrals +disable dual scan --> WSUS •WSUS +deferrals +scan source policy--> each update type from specified source WU or WSUS Switch from dual scan to scan source!
5
45
1
126
Colin Wilkins retweeted
🚨Giveaway alert🚨 We're raffling 3️⃣ tickets and hotel stays for @mmsmoa 2022!! 🤩 To learn how to enter, click the image below 👇 Winners will be announced Friday! Good luck! 🎉#MMSMOA #PatchMyPC #ConfigMgr #SCCM #MSIntune #sysadmin pmpc.io/mms-raffle-2022
1
140
28
69
Colin Wilkins retweeted
First mindmap - Am I vulnerable to Log4shell (v5.0, updated with higher impact for CVE-2021-45046)
11
443
19
1,160
Colin Wilkins retweeted
If you're using #patchmypc, and miss #configmgr ADR (automatic deployment rule) capabilities in #MSIntune- then we would like to talk to you. We have ADRs for Intune in private preview now and are looking for customers willing to deploy it in PROD. Email [email protected]
8
45
4
122
Colin Wilkins retweeted
⏰New Settings Alert⏰ We've added 200+ new settings to the settings catalog with the November release of #MicrosoftEndpointManager. Of note is the addition of highly requested policy settings in the 🔎Auditing and ⚙️System catagory. Changes are rolling now, so keep an eye out.
7
36
3
106
Colin Wilkins retweeted
I know it’s not Friday… but new version of #patchmypc shipped today, including support of customized and localized end user text / notifications. #configmgr #msintune #memcm
3
11
74
Replying to @bdam555
Leave it to marketing and licensing to kill adoption of great innovation.
3
1
28