'vulnerabilities' 검색 결과

Review source code with Strix to trace data flow and authorization checks, then test suspected vulnerabilities in a running environment. Receive proven findings with exploit examples and code locations, while keeping unconfirmed observations clearly identified.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing a repository for security vulnerabilities
• Checking authorization logic in a specific service
• Reviewing security risks introduced by a branch

Review web application security across user input, authentication, external services, dependencies, personal data, and AI features. Identify threats, apply protective controls, and verify changes with checks covering access permissions, sensitive information, and untrusted model output.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing login and access permissions
• Checking file uploads and external API connections
• Assessing dependency vulnerabilities before release

Turn Strix vulnerability findings into focused code fixes, prioritized by severity. Address root causes, rerun security scans and original exploit examples, and report the changes and verification results for each issue.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Fixing vulnerabilities reported by Strix
• Prioritizing remediation by severity
• Retesting original exploits after code changes

Review code and infrastructure for vulnerabilities, insecure dependencies, and exposed credentials. Combine automated scans with manual review to produce audit reports that identify affected locations, rate severity, and prioritize practical fixes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing code for security vulnerabilities
• Checking dependencies and exposed credentials
• Auditing cloud and infrastructure security

Scans code for security vulnerabilities with CodeQL by tracing data across functions. Builds and checks analysis databases, models project-specific APIs, and saves findings in SARIF, a structured results format, with broad or focused scan options.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Scanning a codebase for security vulnerabilities
• Tracing untrusted input through custom APIs
• Choosing broad or high-precision security scans

Scan code for security vulnerabilities, misconfigurations, and exposed secrets. Use when a user asks to audit security, find vulnerabilities, check for OWASP issues, scan for secrets, review dependencies for CVEs, detect SQL injection, find XSS vulnerabilities, or harden an application. Covers OWASP Top 10, dependency auditing, secrets detection, and generates fix recommendations with severity ratings.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

저장소에서 외부 요청이나 사용자 입력으로 악용할 수 있는 취약점을 찾습니다. 입력 경로와 재현 절차, 영향을 확인해 버그 바운티 보고서 작성을 지원합니다.

• 외부 요청으로 도달 가능한 취약점 조사
• 정적 분석 결과 검토
• 최소 재현 절차와 영향 정리

Retrieve current cyber threat data, including malware indicators, addresses of attacker control servers, and vulnerabilities known to be exploited. Filter by threat type, source, severity, and date to identify relevant threats for review and reporting.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing recently observed malware indicators
• Finding high-severity exploited vulnerabilities
• Checking attacker control server indicators

Assess software dependencies, build pipelines, and container images for security risks. Create a software component inventory, check vulnerabilities and license conflicts, verify artifact signatures, and prioritize fixes based on whether vulnerable code can actually be reached.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating and auditing a software component inventory
• Prioritizing dependency vulnerabilities by actual exposure
• Auditing CI/CD pipelines and secret handling

Analyze a software bill of materials, an inventory of software components, against known vulnerability records. Trace indirect dependencies, assess risk, and produce reports that help teams prioritize fixes and review supplier software.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Assessing vulnerabilities in vendor-provided software inventories
• Checking whether a newly disclosed CVE affects deployed software
• Adding SBOM vulnerability checks to CI/CD

Checks application code, dependencies, and security controls to identify vulnerabilities and plan fixes. Includes Python scanners, reports, incident response workflows, and guidance for adding security checks to CI/CD, the automated build and deployment process.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking code for exposed secrets and injection risks
• Prioritizing fixes for known dependency vulnerabilities
• Adding security checks to CI/CD pipelines

Retrieve security findings from Google Cloud Security Command Center for initial assessment. Filter active vulnerabilities, threats, and external exposures, inspect one finding’s full details, or group counts by category to understand the reported risks.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Retrieving full details for a named security finding
• Listing active vulnerabilities or external exposures
• Summarizing active finding counts by category

Review source code, dependencies, and infrastructure settings for security issues. Find exposed credentials, unsafe input handling, and access control gaps, then organize findings into a report with severity levels, affected locations, and recommended fixes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review code security before deployment
• Find API keys and passwords embedded in files
• Check dependencies for known vulnerabilities

Review pull requests, commits, branch differences, or local patches for security vulnerabilities. Inspect changed and deleted text files, trace relevant supporting code, and return validated findings, review comments, and a report describing coverage gaps.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review a pull request for security vulnerabilities
• Check a commit or branch diff before merging
• Inspect local changes, including deleted files

Review pull requests, commits, or local changes for security vulnerabilities, including deleted files. Validate potential issues, trace how attacks could reach them, and produce a report showing confirmed findings and gaps in review coverage.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Security review of a pull request
• Checking a commit or branch diff for vulnerabilities
• Reviewing local changes before committing

This skill should be used when the user asks to "identify web application vulnerabilities", "explain common security flaws", "understand vulnerability categories", "learn about injection attacks", "review access control weaknesses", "analyze API security issues", "assess security misconfigurations", "understand client-side vulnerabilities", "examine mobile and IoT security flaws", or "reference the OWASP-aligned vulnerability taxonomy". Use this skill to provide comprehensive vulnerability definitions, root causes, impacts, and mitigation strategies across all major web security categories.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Pull AWS Security Agent findings (penetration tests and code reviews) and drive remediation. Use this whenever the user mentions Security Agent, security findings, pentest or penetration test results, code review findings, vulnerabilities found in their AWS account, "what did the security scan find", remediating or triaging security risks, or wants to start fixing reported vulnerabilities — even if they don't name the service explicitly. Trigger it for phrases like "get my security findings", "what vulnerabilities do we have", "let's fix the pentest results", or "triage the security report". The skill discovers scans, exports findings to a gitignored local directory (so sensitive exploit detail is never committed), produces a prioritized triage summary, and offers to start fixing the highest-risk issues.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Security vulnerabilities in AI-generated code and LLM applications, covering OWASP Top 10 for LLMs, secure coding patterns, and AI-specific threat modelsUse when "ai code security, llm vulnerabilities, ai generated code review, owasp llm, secure ai development, security, ai, llm, owasp, code-review, vulnerabilities" mentioned.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Hardens code against vulnerabilities. Use when auditing an input handler for vulnerabilities, when handling user input, authentication, data storage, or external integrations, or when checking a login flow is safe against the OWASP Top Ten. Use when building any feature that accepts untrusted data, manages user sessions, or interacts with third-party services. Use when auditing dependencies for known vulnerabilities, triaging package-manager audit findings, or assessing supply-chain risk in a new package. Use when personal data or privacy compliance (GDPR, CCPA) is involved.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

AI-powered codebase security scanner that reasons about code like a security researcher — tracing data flows, understanding component interactions, and catching vulnerabilities that pattern-matching tools miss. Use this skill when asked to scan code for security vulnerabilities, find bugs, check for SQL injection, XSS, command injection, exposed API keys, hardcoded secrets, insecure dependencies, access control issues, or any request like "is my code secure?", "review for security issues", "audit this codebase", or "check for vulnerabilities". Covers injection flaws, authentication and access control bugs, secrets exposure, weak cryptography, insecure dependencies, and business logic issues across JavaScript, TypeScript, Python, Java, PHP, Go, Ruby, and Rust.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

AI-powered codebase security scanner that reasons about code like a security researcher — tracing data flows, understanding component interactions, and catching vulnerabilities that pattern-matching tools miss. Use this skill when asked to scan code for security vulnerabilities, find bugs, check for SQL injection, XSS, command injection, exposed API keys, hardcoded secrets, insecure dependencies, access control issues, or any request like "is my code secure?", "review for security issues", "audit this codebase", or "check for vulnerabilities". Covers injection flaws, authentication and access control bugs, secrets exposure, weak cryptography, insecure dependencies, and business logic issues across JavaScript, TypeScript, Python, Java, PHP, Go, Ruby, and Rust.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

This skill should be used when the user asks to "identify web application vulnerabilities", "explain common security flaws", "understand vulnerability categories", "learn about injection attacks", "review access control weaknesses", "analyze API security issues", "assess security misconfigurations", "understand client-side vulnerabilities", "examine mobile and IoT security flaws", or "reference the OWASP-aligned vulnerability taxonomy". Use this skill to provide comprehensive vulnerability definitions, root causes, impacts, and mitigation strategies across all major web security categories.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Implement and review security measures in Quarkus applications. Covers sign-in, access permissions, input validation, password hashing, secret storage, request limits, audit logs, and checks for known vulnerabilities in dependencies, with implementation and configuration examples.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding JWT or OIDC authentication to a Quarkus API
• Checking role permissions and resource ownership
• Reviewing input validation and database queries

Django 배포나 변경 제안 전에 환경, 코드 품질, 데이터베이스 변경, 테스트, 취약점과 설정을 순서대로 검증하고 단계별 통과 여부와 수정할 문제를 보고합니다.

• Django 변경 제안 전에 확인할 때
• 데이터베이스 마이그레이션을 확인할 때
• 테스트 커버리지 목표를 확인할 때