Tracking asset ownership has come up in a ton of customer conversations over the past few months. It's hard to take action on an asset if you don't know who's the current user, business, IT, or security owner. I'm excited that we delievered asset ownership to @runzero@infosec.exchange in the v3.5 release this month. #CAASM #CMDB
More info: https://www.runzero.com/blog/runzero-3.5/
What’s new with runZero 3.5? Automatic asset ownership mapping and tracking Integration performance and scalability User interface enhancements New protocols and fingerprints New Rapid Response queries Automatic asset ownership mapping and tracking runZero Enterprise customers can now track asset ownership automatically using existing integrations, configurable rules, and customizable ownership types. The default ownership type, Asset Owner, is automatically populated by supported integrations, and can be used as-is, renamed, reordered, or hidden through the new Ownership section in the user interface.
Most CAASM solutions tell you that "you already have all the data, you just need to aggregate it" to get to asset inventory. Great story, except it isn't true.
After having covered vuln management solutions, I look at EDR solutions as a source to get asset inventory from. This is in the context of CISA BOD 23-01 but the same is true for any other asset inventory initiative.
Read the blog post here:
OT engineers are reluctant to scan their ICS networks because they've had bad experiences with vulnerability and other network scanners.
We've researched why these scanners are destabilizing some devices and have created software that's now in use across over a dozen OT industries today.
Read about our research and what we're doing differently:
Do you still believe active scanning in OT environments isn’t safe? We all know passive scanning is difficult to deploy, misses assets, and is costly. With the right solution, and some best practices, active scanning can work in OT environments across any industry.