Common use casesTo simplify the problem, below are the most common use cases in support of vulnerability assessment agents:
- Platform support for agent technologies (Windows, Linux, and MacOS) that are air-gapped, hardened, short time-to-live, cloud, virtual, etc. In other words, you need to scan this asset, and accessing it with a network scanner may not be possible due to routing, location, hardening, or even credentials. A local agent accomplishes the task even if the instance will be short-lived. Think containers.
- Immediate assessment results via API, Scripts, or CLI to support context-aware integration initiatives such as NAC and Adaptive Response.
- Deployment architectures that do not easily support network scans – remote devices, cloud, and mobile (notebooks and tablets) and mobile employees.
- DevOps certification of assets before deployment. If it can be assessed rapidly, automated, and without increasing the risk surface, it should be a part of every Secure DevOps
- Standalone assets, like point of sales systems, ATMs, or embedded devices that require assessments for security best practices or regulatory compliance and may not be routable, have collision domains, or do not permit remote authenticated scans.
Two types of agentsWith these use cases in mind, there are two types of vulnerability assessment agents:
- Local – Agents are installed persistent on the asset and managed. Key management features include:
- Binary version updates
- Signature or audit database updates
- Job scheduling
- Ad-hoc assessments via the management console, API, or CLI
- Store and forward of scan results
- Scriptable installation and minimal resource consumption
- Dissolvable – Agents are installed on-demand via a script or trigger. Once the assessment is complete, the agent automatically uninstalls. Key management features include:
- Installation is complete with latest versions. No need to update before an assessment
- Minimal resource consumption
- Uninstall does not leave any files or fingerprints behind
- Installation, operation, results, uninstall, and fault analysis is available via API or CLI
Morey J. Haber, Chief Technology Officer and Chief Information Security Officer at BeyondTrust
Morey J. Haber is Chief Technology Officer and Chief Information Security Officer at BeyondTrust. He has more than 25 years of IT industry experience and has authored four Apress books: Privileged Attack Vectors (2 Editions), Asset Attack Vectors, and Identity Attack Vectors. In 2018, Bomgar acquired BeyondTrust and retained the BeyondTrust name. He originally joined BeyondTrust in 2012 as a part of the eEye Digital Security acquisition. Morey currently oversees BeyondTrust strategy for privileged access management and remote access solutions. In 2004, he joined eEye as Director of Security Engineering and was responsible for strategic business discussions and vulnerability management architectures in Fortune 500 clients. Prior to eEye, he was Development Manager for Computer Associates, Inc. (CA), responsible for new product beta cycles and named customer accounts. He began his career as Reliability and Maintainability Engineer for a government contractor building flight and training simulators. He earned a Bachelor of Science degree in Electrical Engineering from the State University of New York at Stony Brook.