vulnerability-scanning

Scan application code, dependencies, and container images for security vulnerabilities.

17|5|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/MonumentalSystems/Atlas-Agent-Teams --skill vulnerability-scanning-monumentalsystems
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vulnerability-scanning
Source: https://github.com/MonumentalSystems/Atlas-Agent-Teams/tree/main/teams/security/skills/vulnerability-scanning
Command: npx skills add https://github.com/MonumentalSystems/Atlas-Agent-Teams --skill vulnerability-scanning-monumentalsystems

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Vulnerability scanning helps teams identify security weaknesses in their applications, dependencies, and containers so they can remediate issues before exploitation.

Core Features & Use Cases

  • SAST (Static Application Security Testing): Detects vulnerabilities by analyzing source code and execution paths without running the application; used for pre-merge checks and code reviews.
  • DAST (Dynamic Application Security Testing): Detects vulnerabilities by testing a running application via crawling, fuzzing, and authentication checks; used for validating real-world exposure.
  • SCA (Software Composition Analysis): Identifies known vulnerabilities in third-party libraries and transitive dependencies; used for reducing supply-chain risk and managing patch cycles.
  • Container security scanning: Finds vulnerabilities in base images, application packages, and container configurations; used for DevSecOps pipelines and image hardening.

Quick Start

Run vulnerability scanning across your codebase, running web app, and dependency set to produce a prioritized list of SAST, DAST, and SCA findings and remediation targets.

Frequently Asked Questions about vulnerability-scanning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the difference between SAST, DAST, and SCA vulnerability scanning?

Vulnerability scanning uses SAST to analyze source code statically, DAST to test running applications dynamically, and SCA to identify known vulnerabilities in third-party dependencies. Each targets different attack surfaces across the development lifecycle.

How do I scan container images for security vulnerabilities in a CI/CD pipeline?

Container security scanning analyzes base images, application packages, and container configurations to find vulnerabilities. It integrates into DevSecOps pipelines to harden images and reduce supply-chain risk before deployment.

Does vulnerability scanning work for pre-release code reviews and pre-merge checks?

SAST vulnerability scanning is designed for pre-merge checks and code reviews. It analyzes source code and execution paths without running the application, detecting security flaws early in the development workflow.

What's the best way to reduce third-party library supply-chain risk?

Software Composition Analysis (SCA) identifies known vulnerabilities in third-party libraries and transitive dependencies. It helps manage patch cycles and reduce supply-chain risk by mapping your dependency tree against common vulnerability databases.

Can I validate real-world web application exposure with dynamic security testing?

DAST vulnerability scanning validates real-world exposure by testing a running web application. It uses crawling, fuzzing, and authentication checks to detect runtime vulnerabilities that static analysis alone cannot uncover.

How are vulnerability scanning results prioritized for remediation?

Vulnerability scanning produces a prioritized list of SAST, DAST, SCA, and container findings. Results are ranked using common vulnerability databases to target the most critical security weaknesses for remediation first.