'sec' 검색 결과

Cryptographic security for agentic systems — zero-trust agent networking, signed message envelopes (JWS/JWE), capability-based security (ocaps), Merkle tree audit trails, WASM sandboxing, and formal verification. Covers CLI dev tool security, mTLS between agents, permission boundaries (least privilege for AI agents), and supply chain security for skills/plugins. Activate on: "agent security", "zero trust agents", "secure agent communication", "capability-based security", "ocap", "signed messages between agents", "agent audit trail", "sandbox agent execution", "agent permissions", "mTLS agents", "cryptographic verification", "agent supply chain", "OWASP agentic", "prove agent did X", "tamper-proof agent logs". NOT for: application-level SAST scanning (use security-auditor), network firewall rules (use infrastructure), SOC2/HIPAA compliance (organizational), or prompt injection defense (use prompt-engineer).

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

Performs a comprehensive security review of code changes in a GitHub PR or issue. Checks out the branch, analyzes changed files against a 9-category security checklist, and produces PASS/WARNING/FAIL verdicts. Use when reviewing pull requests for security vulnerabilities, hardcoded secrets, injection flaws, auth bypasses, or insecure configurations. Trigger keywords - security review, code review, appsec, vulnerability assessment, security audit, review PR security.

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

Expert security auditor specializing in DevSecOps, comprehensive cybersecurity, and compliance frameworks. Masters vulnerability assessment, threat modeling, secure authentication (OAuth2/OIDC), OWASP standards, cloud security, and security automation. Handles DevSecOps integration, compliance (GDPR/HIPAA/SOC2), and incident response. Use PROACTIVELY for security audits, DevSecOps, or compliance implementation.

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

Quarkus 앱의 인증, 접근 권한, 입력 검증을 구현하고 점검합니다. 비밀 정보 관리, 비밀번호 해싱, 요청 제한, 감사 로그와 의존성의 알려진 취약점도 다룹니다.

• Quarkus API에 JWT 또는 OIDC 인증 추가
• 역할별 권한과 데이터 소유자 확인 점검
• 입력 검증과 데이터베이스 조회 검토

Laravel 앱의 인증과 권한 관리부터 데이터 처리, 폼, API, 운영 설정까지 보안을 점검합니다. 일반적인 취약점을 피하는 구현 예제를 참고할 수 있습니다.

• 로그인과 권한 관리 점검
• 쿼리와 입력 검증 확인
• 폼의 CSRF·XSS 방어 확인

Look up current US import duties for a product and exporting country using the USITC tariff schedule. Review base rates, Section 301 and 232 additional duties, applicable conditions, and whether the estimated total is complete.

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

• Check current US duties for a product and country
• Review Section 301 and 232 tariff applicability
• Separate confirmed duties from conditional charges

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

Scan a codebase or selected changes for security issues, then request targeted patch files for findings. Independent agents verify reported issues and proposed fixes, while you review and apply patches yourself.

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

• Auditing an entire repository or a selected area
• Checking security issues in branch or pull request changes
• Scanning a single commit

Turn identified threats and business needs into specific, testable security requirements. Define priorities, explain the rationale, and develop security user stories, acceptance criteria, and test cases linked to the risks they address.

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

• Turn threat models into security requirements
• Write security user stories and acceptance criteria
• Develop security test cases

Guides Kubernetes security configuration with network restrictions, Pod execution rules, and role-based access control. Use its configuration examples to separate workloads, limit permissions, and enforce deployment requirements across a cluster.

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

• Restricting communication between application components
• Giving ServiceAccounts only the permissions they need
• Running Pods with restricted privileges

Analyze ModSecurity, AWS WAF, and Cloudflare logs for SQL injection, attempts to manipulate database queries through web requests. Groups related requests, tracks source IPs, classifies attack methods, and produces incident reports.

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

• Investigating suspected SQL injection attempts
• Tracking repeated attacks from the same source
• Connecting requests across an attack campaign

Audit GitHub Actions workflows and CI/CD configurations for supply chain risks. Use Python and YAML parsing to identify unpinned actions, unsafe event expressions, excessive permissions, dependency confusion, and potential exposure of secrets in build pipelines.

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

• Reviewing GitHub Actions workflow security
• Checking action version pinning
• Finding unsafe event expressions in scripts

Assess Bluetooth Low Energy devices by capturing wireless traffic, inspecting available data services, and checking pairing security. Identify signs of interception, reused commands, and data access that lacks authentication.

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

• Assess BLE security on IoT devices
• Check whether devices accept replayed commands
• Investigate suspicious pairing and device impersonation

Scan code, configuration files, and Git history for exposed AWS credentials with TruffleHog. Checks whether detected keys remain active and guides key replacement, incident investigation, and automated checks before commits and during CI/CD.

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

• Auditing Git history for exposed AWS keys
• Adding credential checks before commits and in CI/CD
• Investigating credential exposure after a GuardDuty alert

Review Python, JavaScript/TypeScript, and Go code for security issues using guidance for the project's languages and frameworks. Get prioritized findings, suggested improvements, or help writing new code with safer defaults.

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

• Review an existing application's security
• Create a report organized by severity
• Write new code with safer defaults

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 Python, JavaScript/TypeScript, and Go code for security issues using guidance for the project's languages and frameworks. Get prioritized findings, suggested improvements, or help writing new code with safer defaults.

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

• Review an existing application's security
• Create a report organized by severity
• Write new code with safer defaults

Run repeated, independent security reviews of an entire repository or a selected directory. The skill combines validated findings and coverage records into a final report, helping reduce variation between individual reviews.

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

• Reviewing an entire repository through repeated security audits
• Running an intensive review of a selected directory
• Combining validated findings and coverage into one report

Review smart contract security through five steps covering Slither scans, special features, diagrams, documented safety conditions, and manual checks. Get project-specific findings, testing setup guidance, and a prioritized action plan for development or deployment reviews.

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

• Review smart contract security before deployment
• Triage Slither findings and false positives
• Visualize inheritance and access permissions

Turn validated Codex Security findings into tracked issues in Linear, Jira, or GitHub, or draft GitHub security advisories. Checks duplicates and visibility, previews exact changes for approval, and verifies results after writing.

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

• Create issues for validated security findings
• Check whether a finding is already tracked
• Register a reviewed batch of findings

Develop security design improvements from vulnerability reports, incident documents, source code, or scan results. Compare architectural options with before-and-after diagrams, engineering tradeoffs, and migration plans to support a concrete design decision.

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

• Find structural causes shared by several vulnerabilities
• Compare security architecture options and costs
• Explain proposed changes with before-and-after diagrams

Run repeated, independent security audits of a repository or selected directory with Codex Security. It combines validated findings into a report that records the reviewed scope, exclusions, and any incomplete coverage.

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

• Run repeated security audits across a repository
• Audit a specific directory
• Combine validated findings from independent scans

Use when you need to design, review, or improve security in Spring Boot applications — including SecurityFilterChain, OAuth2/JWT resource server patterns, form login basics, method security (@PreAuthorize), CSRF and CORS for APIs, session fixation, security headers, exception handling, password encoding, and sensitive-data-safe logging. This should trigger for requests such as Add Spring Boot security support; Review Spring Boot security configuration; Improve API authorization in Spring Boot; Add JWT resource server security in Spring Boot; Harden Spring Boot security headers and CSRF settings. Part of Plinth Toolkit

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

Translate technical security work into the language of non-security audiences — board, executives, engineering, customer success, customers, legal, procurement, sales. Covers incident communication, post-mortem narrative, audit-findings-for-stakeholders, risk justification, security spend justification, and customer-facing breach disclosure. Use when the user mentions 'security comms,' 'communicate this finding,' 'explain to my boss,' 'board update,' 'executive summary,' 'incident communication,' 'breach notification,' 'customer disclosure,' 'security memo,' 'post-mortem narrative,' 'risk justification,' 'why this matters to the business,' 'translate this finding,' 'stakeholder update,' or has technical security work that needs to land with a non-security audience.

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