'risk' 검색 결과

Create safe, deterministic git worktrees for large or risky workstreams. Use when tasks are complex enough to warrant isolation from the main working tree.

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

Use for non-trivial, design-bearing, or architecture-affecting work before execution planning. Creates or updates a versioned spec under planning/specs/active/ with design intent, alternatives, risks, and acceptance criteria.

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

Perform repository-aware code reviews focused on bugs, regressions, architectural violations, missing tests, and operational risks. Use when the user asks for review of diffs, pull requests, patches, or implementation quality.

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

Mandatory final risk-focused review for any repository change. Checks security, architecture boundaries, test coverage, and release readiness before closeout.

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

Use for non-trivial feature, behavior, workflow, or architecture work before execution planning. Create or update a versioned spec under planning/specs/active with design intent, alternatives, risks, acceptance criteria, and planning readiness.

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

Create safe, deterministic git worktrees for large or risky workstreams using the repository-owned runtime helper and Windows-safe defaults.

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

The Metasploit Framework is the world's most widely used penetration testing platform, maintained by Rapid7. It contains over 2,300 exploits, 1,200 auxiliary modules, and 400 post-exploitation modules

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

Detect and exploit NoSQL injection vulnerabilities in MongoDB, CouchDB, and other NoSQL databases to demonstrate authentication bypass, data extraction, and unauthorized access risks.

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

Identifies and exploits SMB protocol vulnerabilities using Metasploit Framework during authorized penetration tests to demonstrate risks from unpatched Windows systems, misconfigured shares, and weak authentication in enterprise networks.

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

Detect risky OAuth application consent grants in Azure AD / Microsoft Entra ID using Microsoft Graph API, audit logs, and permission analysis to identify illicit consent grant attacks.

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

Implement a vulnerability aging dashboard and SLA tracking system to measure remediation performance against severity-based timelines and drive accountability.

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

Establish a structured operational process to triage, test, and deploy Microsoft Patch Tuesday security updates within risk-based remediation SLAs.

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

Plan and execute authorized vishing (voice phishing) pretext calls to assess employee susceptibility to social engineering and evaluate security awareness controls.

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

Monitor and analyze ransomware group data leak sites (DLS) to track victim postings, extract threat intelligence on group tactics, and assess sector-specific ransomware risk for proactive defense.

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

Parses Software Bill of Materials (SBOM) in CycloneDX and SPDX JSON formats to identify supply chain vulnerabilities by correlating components against the NVD CVE database via the NVD 2.0 API. Builds dependency graphs, calculates risk scores, identifies transitive vulnerability paths, and generates compliance reports. Activates for requests involving SBOM analysis, software composition analysis, supply chain security assessment, dependency vulnerability scanning, CycloneDX/SPDX parsing, or CVE correlation.

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

Auditing Google Cloud Platform IAM permissions to identify overly permissive bindings, primitive role usage, service account key proliferation, and cross-project access risks using gcloud CLI, Policy Analyzer, and IAM Recommender.

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

Run a bounded red-green-refactor feedback loop only when the user explicitly requests TDD, accepts reproduction-first proof for a bug, or an accepted high-risk behavior specifically requires red/green evidence; do not trigger for every logic, bug, behavior, or implementation change.

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

Conduct one bounded evidence-grounded code review when the user explicitly requests review or ROSE names a concrete unresolved correctness/quality risk; do not trigger automatically after implementation, before every merge, for every bug fix/refactor, or as a completion gate.

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

Perform a bounded security design/hardening pass for explicit security or threat-model intent, or a concrete auth/authorization/secret/untrusted-input/file-upload/sensitive-data risk; do not trigger for every input, data store, third-party call, implementation, review, or release.

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

Code-review quality gate and test-enhancement rubric. Use when ROSE needs sharper review output contracts, severity and risk prioritization, evidence anchors, negative review cases, fixture or golden-output drift guidance, or a Chinese review report profile; do not use as a duplicate code-review agent or final PASS authority.

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

Scores and prioritizes technical debt by impact, risk, and effort. Provides ranked backlog with ROI analysis and quarterly paydown recommendations. Use for "tech debt", "technical debt management", "code quality", or "refactoring priorities".

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

Generates Request for Comments documents for technical proposals including problem statement, solution design, alternatives, risks, and rollout plans. Use for "RFC", "technical proposals", "design docs", or "architecture proposals".

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

Builds phased data and system migrations using feature flags, dual writes, backfills, and validation. Includes rollback plans and risk mitigation. Use for "data migration", "system migration", "database migration", or "platform migration".

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

Creates safe refactor plans for messy UI code including component splitting strategies, state simplification, performance optimizations, and accessibility improvements. Provides phased approach, risk assessment, and "done" criteria. Use when refactoring "legacy code", "messy components", "performance issues", or "large files".

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