「hardening」の検索結果

Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (`audit_cluster.sh`), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny and Dataplane V2 logging), isolating high-risk pods inside GKE Sandbox (`gVisor`), enforcing Pod Security Standards (`restricted` labeling), and mounting Secret Manager secrets via CSI (`SecretProviderClass`). Use when auditing cluster security posture, isolating namespaces, applying pod security standards, setting up Workload Identity, or configuring network policies and secret volume mounts. Don't use for cluster-wide control plane security, RBAC hardening, Binary Authorization, Shielded Nodes, or enabling platform-level GKE add-ons (use gke-platform-security instead).

日本語の概要は準備中です。原文の説明を表示しています。

Manages core GKE cluster provisioning, credentials, Autopilot vs Standard selection, and workload deployment. Use when creating GKE clusters, fetching kubectl credentials, configuring Workload Identity, or deciding between Autopilot and Standard modes. Don't use for specialized GKE networking (use gke-networking), advanced security hardening (use gke-platform-security or gke-workload-security), or cluster upgrades (use gke-upgrades).

日本語の概要は準備中です。原文の説明を表示しています。

Use when designing or configuring public pages on an Experience Cloud site — guest user profile setup, page-level access settings in Experience Builder, object/field visibility for unauthenticated visitors, and explicit sharing rules that expose data on public pages. Triggers: 'configure public pages Experience Cloud', 'guest user profile setup', 'unauthenticated site access', 'public community page visibility', 'make page visible without login'. NOT for authenticated user features (use admin/experience-cloud-member-management). NOT for security hardening or remediation of guest user exposure (use security/guest-user-security). Also covers the deployable shape: pageAccess on the route file, the guest Profile's objectPermissions and fieldPermissions, sharingGuestRules, siteGuestRecordDefaultOwner on CustomSite, and the Network guest flags.

日本語の概要は準備中です。原文の説明を表示しています。

Runs a 5-phase enterprise compliance and security hardening pipeline: regulatory review, GDPR audit, SOC 2 evaluation, dependency scan, and penetration test with cross-framework control mapping..

日本語の概要は準備中です。原文の説明を表示しています。

Plan, create, and configure production-ready Google Kubernetes Engine (GKE) clusters using the golden path Autopilot configuration. Covers Day-0 checklist, Autopilot vs Standard, networking (private clusters, VPC-native, Gateway API), security (Workload Identity, Secret Manager, RBAC hardening), observability, scaling, cost optimization, and AI/ML inference. WHEN: create GKE cluster, provision GKE environment, design GKE networking, secure GKE, optimize GKE cost, GKE autoscaling, GKE inference, GKE upgrade, GKE observability, GKE multi-tenancy, GKE batch, GKE HPC, GKE compute class.

日本語の概要は準備中です。原文の説明を表示しています。

Express.js API guidance — routing, middleware architecture, error handling, security hardening, and production setup.

日本語の概要は準備中です。原文の説明を表示しています。

Professional Electron: main/renderer architecture, IPC, security hardening, packaging, and auto-updates. Use when writing, reviewing, or structuring Electron apps.

日本語の概要は準備中です。原文の説明を表示しています。

Secure containerized workloads — image hardening, registry scanning, runtime protection, and supply-chain integrity.

日本語の概要は準備中です。原文の説明を表示しています。

Strengthen defensive security operations — detection engineering, hardening, monitoring, and continuous defense improvement.

日本語の概要は準備中です。原文の説明を表示しています。

Design, audit, harden, review, or upgrade MCP servers and MCP Apps with revision-aware protocol profiles, explicit HTTP/deployment boundaries, capability-centered validation, bilingual reporting, and reproducible evidence. Use for MCP server architecture, JSON-RPC or Streamable HTTP bugs, security hardening, protocol-version migration, MCP Apps widget boundaries, review reconciliation, test planning, and public engineering evidence.

日本語の概要は準備中です。原文の説明を表示しています。

Use when authoring or reviewing CI/CD pipelines — GitHub Actions workflows, reusable workflows, composite actions, OIDC federation to AWS/GCP, caching, artifacts, and pipeline security hardening. Triggers on edits to .github/workflows/**, action.yml, composite action definitions, or mentions of "CI", "CD", "pipeline", "GitHub Actions", "workflow", "OIDC", "runner", "deploy script", "release", or "build pipeline".

日本語の概要は準備中です。原文の説明を表示しています。

Scan and redact PII and sensitive data (emails, phone numbers, SSNs, API keys, IP addresses, credentials, amounts, company/person names) from repository files. Includes a pre-commit hook to block commits containing PII. Use when asked to audit code for sensitive data, sanitize files before publishing, or install PII detection hooks. For application security hardening see security-engineering.

日本語の概要は準備中です。原文の説明を表示しています。

Hardens code against vulnerabilities. Use when handling user input, authentication, data storage, or external integrations. Use when building any feature that accepts untrusted data, manages user sessions, or interacts with third-party services.

日本語の概要は準備中です。原文の説明を表示しています。

Evaluate error handling, i18n, text overflow, and edge cases.

日本語の概要は準備中です。原文の説明を表示しています。

IAM policy review, hardening, and least privilege implementation

日本語の概要は準備中です。原文の説明を表示しています。

Apply npm/pnpm supply-chain hardening when adding a dependency, editing package.json/.npmrc/pnpm-workspace.yaml, reviewing a lockfile change, or configuring CI install steps. Covers the 17 practices from lirantal/npm-security-best-practices.

日本語の概要は準備中です。原文の説明を表示しています。

Hardens code against vulnerabilities. Use when handling user input, authentication, data storage, or external integrations. Use when building any feature that accepts untrusted data, manages user sessions, or interacts with third-party services.

日本語の概要は準備中です。原文の説明を表示しています。

Use when taking a repo open source, or hardening one that already is. Run /oss-launch and it scans the repo (stack, existing files, git remote, secrets), asks only what it cannot infer, then generates a tailored OSS file collection (README, LICENSE, CONTRIBUTING, CODE_OF_CONDUCT, SECURITY, CHANGELOG, .gitignore, .github/ issue + PR templates, CI/CD). Also covers launch (GitHub metadata, badges, Show HN, Reddit, YouTube), release cadence (SemVer + CHANGELOG), and demo-GIF generation. Triggers on "open source this", "OSS checklist", "prep for launch", "make this repo public", "add a license / contributing / security policy", "Show HN", "release workflow", "star growth", "get contributors".

日本語の概要は準備中です。原文の説明を表示しています。

Practical security review and hardening guidance for application code in Python, JavaScript/TypeScript, and Go. Use this skill whenever the user asks for a security review or audit, wants to harden authentication (password hashing, sessions, JWT, OAuth2/OIDC, MFA), fix OWASP Top 10 issues (injection, XSS, IDOR, CSRF, SSRF, deserialization), threat-model with STRIDE, clean up secrets and .env handling, or set up dependency scanning (pip-audit, npm audit, osv-scanner, gitleaks, SBOM). Also trigger for "make this secure", "is this safe to deploy", bcrypt/argon2id, rate limiting logins, RBAC/ABAC, CSP and security headers, cookie flags, and secure-by-default coding help.

日本語の概要は準備中です。原文の説明を表示しています。

Especialista em containerização Docker com conhecimento profundo de multi-stage builds, otimização de imagens, segurança em containers, orquestração com Docker Compose e padrões de deploy em produção. Use PROATIVAMENTE para otimização de Dockerfile, problemas em containers, problemas de tamanho de imagem, hardening de segurança, networking e desafios de orquestração.

日本語の概要は準備中です。原文の説明を表示しています。

Apply the Opquast Digital Quality Framework (245 rules, 14 categories) when building, reviewing, or auditing websites and web applications. Use for web development quality assurance, accessibility compliance, security hardening, privacy implementation, e-commerce best practices, and holistic digital quality checks.

日本語の概要は準備中です。原文の説明を表示しています。

Design, audit, harden, review, or upgrade MCP servers and MCP Apps with revision-aware protocol profiles, explicit HTTP/deployment boundaries, capability-centered validation, bilingual reporting, and reproducible evidence. Use for MCP server architecture, JSON-RPC or Streamable HTTP bugs, security hardening, protocol-version migration, MCP Apps widget boundaries, review reconciliation, test planning, and public engineering evidence.

日本語の概要は準備中です。原文の説明を表示しています。

Codex adapter for Garry Tan's full gstack methodology across CEO/product pressure, CTO architecture, design, engineering, QA, security, shipping, documentation, and retrospectives. Use when the 总控/CEO or 架构/CTO role needs gstack method routing, implementation-plan hardening, or the user says gstack should help a role.

日本語の概要は準備中です。原文の説明を表示しています。

Use for security review, audit, hardening, compliance, DevSecOps, network, infrastructure, or application security with focused references.

日本語の概要は準備中です。原文の説明を表示しています。