'security' 검색 결과

Review and strengthen security in claude-flow v3 by addressing dependency risks, password hashing, credential generation, input validation, file paths, and command execution. It also guides threat modeling and tests for security-critical code.

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

• Reviewing security boundaries and potential threats
• Updating dependencies and checking audit results
• Revising password hashing and credential generation

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

Match identified security threats with controls that prevent, detect, or help recover from attacks. Use the mappings to find coverage gaps, prioritize security spending, and create remediation plans with multiple layers of protection.

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

• Prioritizing security investments
• Creating a security remediation roadmap
• Checking gaps in existing security controls

Investigate excessive privileges inside Kubernetes pods by reviewing security settings, runtime events, and audit logs. Use admission policies to restrict risky configurations and Falco monitoring to detect suspicious privilege changes and container activity.

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

• Finding pods running as root or in privileged mode
• Reviewing host filesystem access and dangerous Linux permissions
• Detecting privilege changes while containers are running

Design and configure VLANs, logical network partitions, to separate employee devices, servers, guests, and IoT equipment. Covers traffic restrictions between zones, switch security settings, and tests to verify that the intended isolation works.

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

• Separating guest WiFi and IoT devices from internal systems
• Planning network isolation for payment processing systems
• Restricting communication between network zones

Plan and run authorized security tests that simulate deceptive emails, calls, text messages, and in-person approaches. Measure employee responses, compare results across test methods, and report gaps in security awareness training and access controls.

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

• Planning an authorized social engineering assessment
• Measuring responses to simulated phishing
• Evaluating phone and physical access checks

Build Splunk pipelines that import threat intelligence and match security events against indicators such as malicious IP addresses, domains, and file hashes. Add source, confidence, and severity details so analysts have context when investigating matches.

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

• Importing external threat feeds into Splunk
• Matching network and endpoint logs against threat indicators
• Adding threat and asset context to alerts

Set up Microsoft Sentinel to collect security logs from AWS, Azure, and GCP. Build detection queries, investigate historical activity, and create automated response workflows for a centralized security operations team.

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

• Centralizing security monitoring across multiple clouds
• Migrating from an existing SIEM platform
• Automating responses to suspicious cloud activity

Audit AWS, Azure, and GCP configurations against CIS Benchmarks, security configuration guidelines. Use automated scan results to identify failed checks, prioritize fixes, report compliance by area, and establish ongoing monitoring for configuration changes.

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

• Running an initial cloud security configuration audit
• Preparing CIS-related evidence for SOC 2 or ISO 27001 audits
• Prioritizing fixes for failed security checks

Analyze git history to map contributors to security-sensitive files, identify reliance on too few people, and find stale areas. Export CSV and JSON results for ownership reviews, graph exploration, and comparison with CODEOWNERS.

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

• Find stale security-sensitive code with few maintainers
• Check reliance on individual authentication or cryptography maintainers
• Compare CODEOWNERS with actual contribution history

Analyze git history to map contributors to security-sensitive files, identify reliance on too few people, and find stale areas. Export CSV and JSON results for ownership reviews, graph exploration, and comparison with CODEOWNERS.

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

• Find stale security-sensitive code with few maintainers
• Check reliance on individual authentication or cryptography maintainers
• Compare CODEOWNERS with actual contribution history

Implement an authorized fix for a reviewed security issue, check the plan against current code, and add regression tests to catch recurrence. Verify affected components and open a pull request that closes the issue while respecting disclosure rules.

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

• Implementing an approved security remediation plan
• Rechecking a reviewed fix against current code
• Adding regression tests for a security boundary

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

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

Test REST, gRPC, and WebSocket APIs for weaknesses in authentication, access controls, input handling, and configuration. Provides protocol-specific checks, tool guidance, and detection indicators to help document reproducible findings and severity during authorized assessments.

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

• Check access controls across users and roles
• Review token lifecycles and request limits
• Assess gRPC and WebSocket security

Evaluate supplied security findings against repository code and security policy without running the software. Classify each claim as confirmed, not actionable, or needing review, then rank relevant findings by exploitability and explain evidence gaps and next steps.

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

• Assess findings from a vulnerability scanner
• Review security tickets from Jira or Linear
• Evaluate GitHub alerts and security advisories

Analyze HTTP security headers of web domains to identify vulnerabilities and misconfigurations. Use when you need to audit website security headers, assess header compliance, or get security recommendations for web applications. Trigger with phrases like "analyze security headers", "check HTTP headers", "audit website security headers", or "evaluate CSP and HSTS configuration".

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

Migrate Spring Security 5 to Spring Security 6 configuration. Use when removing WebSecurityConfigurerAdapter, replacing @EnableGlobalMethodSecurity with @EnableMethodSecurity, converting antMatchers to requestMatchers, or updating to lambda DSL configuration style. Covers SecurityFilterChain beans and authentication manager changes.

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

LLM and AI application security testing — prompt injection, jailbreak resistance, OWASP LLM Top 10 (2025), RAG and agent/tool-use security, model supply chain, and AI red teaming for authorized assessments

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

Use when you need to design, review, or improve security in Micronaut applications — including micronaut-security authentication, @Secured and intercept-url-map rules, JWT/session strategies, SecurityService checks, CORS, CSRF awareness for browser apps, rejection handlers, and sensitive-data-safe logging. This should trigger for requests such as Add Micronaut security support; Review Micronaut security configuration; Improve API authorization in Micronaut; Add JWT security in Micronaut; Harden Micronaut route authorization rules. Part of Plinth Toolkit

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

Use when you need to design, review, or improve security in Quarkus applications — including Quarkus Security with JWT/OIDC, basic auth, @RolesAllowed / @Authenticated / @PermitAll, SecurityIdentity, permission checks, path-based authorization in configuration, exception mapping for auth failures, and sensitive-data-safe logging. This should trigger for requests such as Add Quarkus security support; Review Quarkus security configuration; Improve API authorization in Quarkus; Add JWT/OIDC security in Quarkus; Harden Quarkus authorization rules. Part of Plinth Toolkit

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

Audit cloud infrastructure (AWS, GCP, Azure) for misconfigurations, excessive permissions, and security gaps. Use when the user mentions 'cloud security,' 'cloud audit,' 'AWS security,' 'GCP security,' 'Azure security,' 'IAM audit,' 'S3 bucket,' 'cloud misconfiguration,' 'cloud hardening,' or needs to review cloud infrastructure security.

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

AWS Security Audit workflow skill. Use this skill when the user needs Comprehensive AWS security posture assessment using AWS CLI and security best practices and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

API Security Testing Workflow workflow skill. Use this skill when the user needs API security testing workflow for REST and GraphQL APIs covering authentication, authorization, rate limiting, input validation, and security best practices and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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