'sast' 검색 결과

Plan and run backups, set recovery objectives, and run disaster recovery drills. Use this skill when defining RPO/RTO targets, designing backup architecture, deciding what to back up and how often, planning for full-region or platform outages, or running a restoration drill. Triggers on backup, restore, RPO, RTO, disaster recovery, DR, business continuity, what if the database is gone, what if our hosting goes down, recovery drill, ransomware planning. Also triggers when an incident reveals a gap in restoration capability.

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

OpenStack backup operations skill for protecting cloud infrastructure through systematic backup strategies and disaster recovery procedures. Covers database backups (MariaDB full and incremental with mariabackup), configuration backups (globals.yml, inventory, Fernet keys), volume snapshots (Cinder LVM snapshots), image exports (Glance), instance snapshots (Nova), backup encryption (GPG/OpenSSL), retention policies (daily/weekly/monthly rotation), restore procedures (database point-in-time recovery, service rebuild), RPO/RTO planning, and disaster recovery drills. Use when planning backup strategy, scheduling automated backups, testing restore procedures, or executing disaster recovery.

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

アプリケーションコードでの自動脆弱性検出のための静的アプリケーションセキュリティテスト（SAST）ツールを設定します。セキュリティスキャンの設定、DevSecOps実践の実装、またはコード脆弱性検出の自動化時に使用してください。

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

FEMA disaster declarations, NOAA weather alerts, and USGS earthquake data. 3 tools for real-time disaster monitoring.

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

Write custom Semgrep SAST rules in YAML to tespit etme
application-specific vulnerabilities, enforce coding standards, and integrate into CI/CD pipelines.

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

bu skill covers integrating Static Application Security Testing (SAST) tools—CodeQL and Semgrep—into GitHub Actions CI/CD pipelines. It addresses configuring automated code scanning on pull requests and pushes, tuning rules to reduce false positives, uploading SARIF results to GitHub Advanced Security, and establishing quality gates that block merges when high-severity vulnerabilities are Detected.

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

Use when a carrier asks about disaster recovery (DR) and business continuity planning (BCP) — cyber incident, natural disaster, terminal loss, key-person departure, financial liquidity event, major customer loss, insurance crisis, or fuel supply disruption. Covers risk assessment, continuity strategy, communication plans, and recovery time objectives.

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

Set up Strix security checks in CI/CD to test pull request changes, report verified vulnerabilities, and gate merges. Covers both a CLI running on your own infrastructure and a managed service with pull request comments.

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

• Check pull request changes for vulnerabilities before merging
• Add Strix scans to GitHub Actions or GitLab CI
• Choose between managed reviews and scans on your own runners

Review authorized source code or pull request changes for security flaws. Combine automated static analysis, which checks code without running it, with manual validation to document affected locations, data flows, reproduction examples, and suggested fixes.

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

• Reviewing pull request changes for security issues
• Checking scanner findings for false positives
• Investigating authorization and injection flaws

Plan systems across AWS, Azure, GCP, and OCI by comparing services and architecture patterns. Helps guide service selection, disaster recovery, migration planning, and cost decisions while considering ways to reduce dependence on a single provider.

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

• Planning a system across multiple cloud providers
• Designing disaster recovery in another cloud
• Comparing cloud services for a workload

Check security audit findings against code evidence and trace how untrusted input moves through a system. Guide a second review, document verification gaps, and assess draft reports against a minimum quality score before delivery.

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

• Verifying evidence behind security review findings
• Rechecking input flows after an initial analysis
• Assessing report quality before delivery

Configure Backup for GKE to protect Kubernetes configurations and persistent data. Set backup schedules, retention periods, and customer-managed encryption keys, then prepare restore plans with explicit policies for handling existing resources.

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

• Setting scheduled backups and retention periods
• Backing up persistent data and Secrets
• Encrypting backups with customer-managed keys

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

Static Application Security Testing (SAST) for code vulnerability analysis across multiple languages and frameworks

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

Configure Static Application Security Testing (SAST) tools for automated vulnerability detection in application code. Use when setting up security scanning, implementing DevSecOps practices, or automating code vulnerability detection.

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

Implement disaster recovery strategies and runbooks. Configure RPO/RTO targets and failover procedures. Use when planning for business continuity.

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

Generate a Disaster Recovery plan with RTO/RPO targets. Use when someone asks to "create a DR plan", "disaster recovery", "business continuity", or "RTO RPO". Do NOT use for step-by-step restoration runbooks — use /pmstudio-recovery instead. Designed for SaaS platform products where Coco Inc is the customer — focuses on service continuity, data recovery, and vendor dependency management rather than infrastructure rebuild.

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

Static Application Security Testing patterns, OWASP Top 10 checklist, language-specific vulnerability patterns, Semgrep rule writing guide, and CI/CD integration. Use when scanning code for security vulnerabilities or writing custom SAST rules.

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

Design and implement disaster recovery strategies with RTO/RPO planning, database backups, Kubernetes DR, cross-region replication, and chaos engineering testing. Use when implementing backup systems, configuring point-in-time recovery, setting up multi-region failover, or validating DR procedures.

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

Use when designing disaster recovery strategies, defining RPO/RTO targets, implementing failover mechanisms, or conducting chaos engineering tests - covers active-active, pilot light, and backup strategiesUse when ", " mentioned.

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

Bearer CLI is an open-source static application security testing (SAST) tool that scans source code to identify, filter, and prioritize security vulnerabilities and privacy risks. Covers OWASP Top 10 and CWE Top 25 with data flow analysis across multiple languages.

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

Preserve and conserve library and archival materials. Covers environmental controls (temperature, humidity, light), handling procedures, book repair techniques (torn pages, loose spines, foxing), acid-free storage, digitization for preservation, and disaster recovery planning. Use when establishing preservation practices for a new or existing collection, when materials show signs of deterioration, when setting up environmental controls for storage, when planning digitization to preserve fragile originals, or when creating a disaster recovery plan for a library or archive.

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

AI-first security scanning with Medusa. 3,000+ detection patterns covering AI/ML, agents, MCP, RAG, prompt injection, and traditional SAST vulnerabilities. Wraps Medusa CLI with SARIF/JSON parsing, structured finding output, OWASP mapping, and remediation guidance.

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