Skip to main content

NinjaOne: Third-party patching

  • January 9, 2026
  • 0 replies
  • 30 views

Forum|alt.badge.img+13

Just wanted to see if any of you are servicing customers that have recently implemented NinjaOne for endpoint management and patching. 

If so, how have you approached the third-party patching? 

  • cert pinned app bypass? 
  • domain bypasses?
  • ssl no decrypt policies? 
  • mix of all of the above? 

We have our endpoint management team working but we just foresee a massive maintenance task in the future for the needed and potentially changing domains? A wildcard approach seems like too much of a security hole.