Jan 16 2021 11:04 PM
Jan 16 2021 11:04 PM
It seems that to address the "Block persistence through WMI event subscription", there is nothing in the Intune GUI that you can check/enable. You need to use an Administrative template and specify the OMR-URI value.
I've done this and assigned this admin template to a subset of my users (I've assigned this policy to users not devices), about 13 Users.
And after looking at the results, I get about 9 errors out of the 13 Users... and they seem to vary from day to day. Also I can also get a status per device..
Obviously, either in the policy results or in the device page, I don't see any details besides "Failed"
Did I miss anything?
Jan 17 2021 02:18 AM
Your probably not the only one.
But are you talking about persistence or WMI commands (One is Intune ready the other is not)
I get the same inconsistent results but when I check the PowerShell script run by devices I see that it is not the case. I have checked that the devices are indeed registered and even more that the devices are managed by Intune (MDM - you have to becareful that the same devices are not also managed by MAM) and comply with the prerequisites required to run said scripts.
If you look at the development of Endpoint Manager (yes Microsoft still call it Intune) you will see its on the agenda.
I am beginning to get so annoyed with this that I am considering turning it into a Endpoint Analytics proactive remediation script to see what the hell is going on. Microsoft provide two very good examples that you can see here.
The code for PowerShell is here
Jan 18 2021 02:08 AM
Thanks for your reply.
So you're not using an admin template but rather a PS script?
I am not sure I understand if it works in your case or not. Are you managing to see the recommendations go away?
Jan 19 2021 07:55 PM
Yes both go away (since there are two associated with WMI)
I will ditch the PowerShell script when its officially supported by Intune
I just checked 3 machines that have a high "uptime" and its not reported in any of them, so resolved.
Jan 19 2021 11:12 PM
Do you have other ASR rules applied then you might look at this trick:
How I manage my device from Endpoint Manager - taste your own medicine - Part 2 of 4 (mindcore.dk)
Jan 20 2021 01:32 AM - edited Jan 20 2021 01:50 AM
Okay having a look,
Recommendation 11,12 and 13 via ASR in Endpoint manager
Recommendation 14 implemented via PowerShell script iaw our discussions, Windows devices must be managed by Intune either registered or joined, and must be MDM not MAM.
Recommendation 14 - interesting solution - shall investigate your solution as blogged.
Recommendation 15, 16 doesn't appear in my list of "global" recommendations so its already managed
Recommendation 17, 18 exist but I'm not pushing this as I have MFA (Ill get to the golden ticket problem)
Recommendation 19 - nope doesn't exist - so managed.
Recommendation 20 - I don't agree with and that's domain, public and private - end users should know IMHO
I have 53 recommendations in total over 7 Windows 10 test devices one of which is a dud. I changed the name before a restart and ended up with a bullcrap entry that pulls my score down. 30 days from now it should clear itself (I actually hate this - in that you cant delete obsolete or renamed devices), and then Ill push it back up to 180 days.
I run Sentinel. This was the solution that Microsoft used to discover the SolarWinds debacle (biggest hack to date). I have also read the Fireeye post report as well including the CISA alert. I also have MCSA enabled and this also tells me a great deal.
At best I can get my security recommendations down to 16 on joined machines, 19 on registered and then I have my bogus entry and as of writing I am getting new reports on Chrome browser.
My gut feeling - I can never get this to zero as my hardware is to old, and Microsoft keep upping the ante as they should based on what they see across a billion devices.
If you read this post
and can implement it you are doing well, then there are these
I am not exactly sure what you are trying to achieve. Perfection, not going to happen, to many factors involved and way to many seriously smart and over resourced organizations trying to find a way in.
I read a post somewhere that basically says - assume you are going to be breached. Eventually you will be but then how long does it take you to realize it, and close the door.
I tell you one thing, this is the most engaging conversation I have had on this forum so if you feel like continuing to share please keep replying. Remember though I am a amateur, I don't have certifications yet that confirm my love of this content.
I am also on LinkedIn, my profile is here. Feel free if you think I am worthy to add me to your list.
The fact is I believe we have the same goals and you might teach me a thing or two, and we can not upset the Microsoft moderator by keep deviating from our posts.
Make sure you tell me its you.