Alert icon Keyboard navigation enabled.
Alert icon TAB or Shift+TAB to navigate across. Down ↓ to open menu. ESC to close menu.
Alert icon Down ↓ to select section. Right → to activate. Up ↑ / Down ↓ / Tab to traverse all. ESC to exit.
BeyondTrust
Skip to content Use space or enter to skip.

What can we help you find today?

Instant Results
  • Website Results
  • Technical Documentation

Filter Options

Focus your search

Filtering by

Your recent searches:

Contact Us Chat with Sales Get Support
  • English
  • Deutsch
  • français
  • español
  • 한국어
  • português
  • Home
  • Resources
  • Blog
  • Use Cases for Performing Vulnerability Assessments with Agent-Based Technology current page
Link copied

Use Cases for Performing Vulnerability Assessments with Agent-Based Technology

Jun 5, 2018
Author:
Morey Haber Headshot 2024
Morey J. Haber
Chief Security Advisor
Blog banner default
Use Cases for Performing Vulnerability Assessments with Agent-Based Technology
Morey Haber Headshot 2024
Morey J. Haber
Chief Security Advisor

Agent technology is nothing new. In fact, many organizations wrestle with quantity, conflicts, and updates for the wide variety of agents they have today. So why should a vulnerability assessment agent be anything special? It is not—except that the usage is not widespread and not all vendors are equal in their agent offerings and their accompanying management capabilities. It becomes a conscious choice for many organizations to network scan or use agent technology based on use cases, frequency, and device access.

Common use cases

To 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 agents

With 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

Agent technologies for vulnerability assessments offer a viable alternative to network scans. The results are comparable to credentialed scans and offer a method to obtain results without the potential problems and nuances of traditional network scanners.

  • Scan to reveal privileged credential and access vulnerabilities across your environment with our free tool!
Latest Posts
  • Hooked on Identity (Part 2): Abusing OAuth Trust Boundaries in Okta
    Jun 12, 2026 Hooked on Identity (Part 2): Abusing OAuth Trust Boundaries in Okta
    Blog
    7m
  • Hooked on Identity: Abusing SAML Assertion Inline Hooks in Okta
    Jun 9, 2026 Hooked on Identity: Abusing SAML Assertion Inline Hooks in Okta
    Blog
    6m
  • Joining Project Glasswing: Securing the Privilege Backbone of the AI Era
    Jun 8, 2026 Joining Project Glasswing: Securing the Privilege Backbone of the AI Era
    Blog
    5m
  • The Most Common & Most Dangerous Types of Shadow IT
    Jun 5, 2026 The Most Common & Most Dangerous Types of Shadow IT
    Blog
    19m
  • 14 Password Management Best Practices
    May 28, 2026 14 Password Management Best Practices
    Blog
    12m
Related
  • Least Privilege: The Most Effective Approach to Endpoint Security
    May 6, 2020 Least Privilege: The Most Effective Approach to Endpoint Security
    Blog
    1m
  • The Clock Strikes 13 on the 2020 Verizon Data Breach Investigations Report
    May 29, 2020 The Clock Strikes 13 on the 2020 Verizon Data Breach Investigations Report
    Blog
    1m
Share this Article
  • Link
Stay up to Date
Get the latest news, ideas, and tactics from BeyondTrust. You may unsubscribe at any time.

Keep up with BeyondTrust

Customer Support Get Started
  • LinkedIn
  • X
  • Facebook
  • Instagram
  • Add BeyondTrust as a preferred source on Google
  • Privacy
  • Security
  • Manage Cookies
  • Do Not Sell My Data
  • WEEE Compliance

Copyright © 2003 — 2026 BeyondTrust Corporation. All rights reserved. Other trademarks identified on this page are owned by their respective owners. BeyondTrust Corporation is not a chartered bank or trust company, or depository institution. It is not authorized to accept deposits or trust accounts and is not licensed or regulated by any state or federal banking authority.

Prefers reduced motion setting detected. Animations will now be reduced as a result.