bk-monitor-security-audit

Audits frontend code for XSS, CSRF, and injection vulnerabilities using a structured checklist.

840|261|Updated Apr 18, 2019
One-click install
npx skills add https://github.com/TencentBlueKing/bk-bcs --skill bk-monitor-security-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bk-monitor-security-audit
Source: https://github.com/TencentBlueKing/bk-bcs/tree/main/bcs-services/bcs-project-manager/.cursor/skills/bk-monitor-security-audit
Command: npx skills add https://github.com/TencentBlueKing/bk-bcs --skill bk-monitor-security-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Frontend code often contains hidden security flaws such as unsafe DOM manipulation, open redirects, and dynamic code execution that slip through manual review. This Skill provides a systematic audit workflow that detects XSS, CSRF, and injection vulnerabilities before code reaches production.

Core Features & Use Cases

  • Checklist-Driven Audit: Inspects DOM operations (innerHTML, v-html), URL and redirect handling, postMessage cross-origin communication, eval usage, sensitive data exposure, prototype pollution, and ReDoS.
  • Structured Reporting: Outputs findings using a standardized report template with referenced audit rules and a security checklist.
  • Use Case: Before merging a pull request that touches user input rendering, run the audit to verify no v-html bindings or unvalidated redirects introduce XSS or open-redirect vulnerabilities.

Quick Start

Review the security of my frontend code changes and report any XSS or CSRF vulnerabilities.

Frequently Asked Questions about bk-monitor-security-audit

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

FAQPage Schema
How do I audit frontend code for XSS vulnerabilities?

Audit frontend code for XSS by checking all DOM injection points such as innerHTML and v-html bindings, verifying user input is sanitized before rendering, and reviewing URL and redirect handling. This Skill walks through each checkpoint systematically and reports findings.

What security issues does a frontend code review check?

A frontend security review checks DOM manipulation safety, URL and redirect validation, postMessage cross-origin communication, dynamic code execution via eval, sensitive information exposure, prototype pollution, and ReDoS patterns in regular expressions.

When should I run a frontend security audit?

Run an audit during code submission or review, when changes involve DOM operations, URL processing, or user input handling, and whenever XSS, CSRF, or injection concerns are raised about the codebase.

Does this audit detect CSRF and injection flaws beyond XSS?

Yes, the audit checklist covers CSRF risks, injection patterns, open redirects, unsafe postMessage usage, eval-based dynamic execution, prototype pollution, and ReDoS in addition to XSS vectors like innerHTML and v-html.

What are the limitations of a static frontend security audit?

A static audit inspects source code patterns and cannot observe runtime behavior, so it may miss vulnerabilities that only appear through specific data flows or server-side interactions. Combine it with dynamic testing for full coverage.