'security' 검색 결과

Create or review SECURITY.md guidance so Codex Security understands what to examine, which protections must hold, and what is excluded. Compare existing policies with repository evidence and preview proposed changes before writing.

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

• Define security review scope for a repository
• Document required security protections
• Check whether existing guidance matches the code

Security-Scanner Agent fuer fabrikIQ und andere Projekte. Fuehrt umfassende Sicherheitspruefungen durch. Trigger bei: (1) Pre-commit Validation, (2) PR-Creation, (3) Weekly Security Audits, (4) Nach Dependency-Updates, (5) Vor Production Deployments. <example> Context: User moechte vor einem Commit sicherstellen, dass keine Secrets committed werden. user: "Ich will gleich committen. Pruefe mal auf Secrets." assistant: "Ich starte den security-scanner Agent, um den Code auf API Keys, Tokens und andere Secrets zu pruefen." <Task tool call to security-scanner agent> </example> <example> Context: Weekly Security Audit des fabrikIQ-Projekts. user: "Fuehre den woechentlichen Security-Scan durch." assistant: "Ich fuehre einen vollstaendigen Security-Scan durch: Secret Detection, Dependency Audit, OWASP Patterns, Security Headers und Rate Limiting." <Task tool call to security-scanner agent> </example> <example> Context: User hat Dependencies aktualisiert und will Vulnerabilities pruefen. user: "Ich habe npm update und pip install -U gemacht. Gibt es Sicherheitsprobleme?" assistant: "Ich scanne die aktualisierten Dependencies auf bekannte Vulnerabilities mit dem security-scanner Agent." <Task tool call to security-scanner agent> </example> <example> Context: PR-Review mit Security-Fokus. user: "Review den PR #42 auf Security-Probleme." assistant: "Ich analysiere die geaenderten Dateien im PR auf Security-Patterns: SQL Injection, XSS, Hardcoded Credentials und fehlende Input-Validation." <Task tool call to security-scanner agent> </example>

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

Audit and strengthen security for applications running on GKE. Configure pod traffic restrictions, sandbox isolation, namespace security standards, and Secret Manager volume mounts to protect workloads at the application and namespace level.

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

• Auditing GKE security settings
• Restricting communication within a namespace
• Isolating risky pods and applying security standards

Research cybersecurity companies, investors, funding, and acquisitions using Return on Security's Signal data. Results retain source freshness and distinguish recorded deals from analytical estimates, helping you examine market trends and company profiles.

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

• Track quarterly funding trends in cloud security
• Research a security company's funding and investors
• Map acquisitions in identity security

Assess iOS and Android app security using OWASP MASTG, a mobile security testing guide. Examine app files, runtime behavior, stored data, authentication, and API traffic, then document vulnerabilities, their impact, and suggested fixes.

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

• Assess mobile app security before release
• Check sensitive data storage and network traffic
• Test authentication and resistance to runtime manipulation

Review an AI agent codebase against ten OWASP ASI security risk areas. Examine tool permissions, input validation, identity checks, audit logs, and other controls, then summarize coverage, gaps, and recommended improvements in a report.

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

• Reviewing agent security before production deployment
• Mapping existing controls to ten security risk areas
• Preparing findings for a security review or audit

Support information security management for healthcare and medical technology companies. Structure an ISO 27001 management system, assess risks, review security controls, and prepare audit evidence, gap reports, and incident response procedures.

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

• Planning an information security management system
• Assessing risks to patient data and medical devices
• Finding gaps in security control implementation

Plan security programs for growing companies by estimating financial risk and prioritizing controls. Produce compliance roadmaps, budget justifications, incident response plans, vendor assessments, and board reports that connect security decisions to business impact.

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

• Justify security budgets with estimated financial losses
• Plan SOC 2 or ISO 27001 compliance work
• Prepare incident coordination and communication plans

Review threat mitigations after a development phase is complete and update SECURITY.md with verification results. Use an existing security record or a threat model in the phase plan to guide the review.

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

• Check security mitigations after completing a development phase
• Audit mitigations documented in SECURITY.md
• Verify completed work against a threat model in PLAN.md

AWS security service suitability, coverage and cost recommendations: WAF/origin overlap, AWS Network Firewall inspection coverage and policy review, VPC endpoint, Transit Gateway/Cloud WAN segmentation and DNS Firewall security-control suitability, certificate renewal ownership and monitoring, incident response triage ownership, centralized security log store (CloudWatch or Security Lake). Also factual configuration, findings, data sources and severity scoring for GuardDuty, Inspector, Security Hub V2/OCSF (Exposure, connectors, automation), Security Hub CSPM/ASFF (standards, controls), Macie, Detective, Security Lake, AWS Security Incident Response membership and case coverage, and Organizations security policies. Applies to advisory security-service choices even when one service is named. Implementation, rule or code authoring, deployment, scans and troubleshooting outside these factual procedures belong to specialist skills. Supports local AWS CLI and AWS MCP.

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

Audit a codebase with three vulnerability hunters and two engineers who build small demonstrations of suspected flaws. Verify attack paths, assess severity from demonstrated impact, and report evidence, targeted fixes, and checks to prevent recurrence.

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

• Review security before a release
• Audit security risks in a pull request
• Verify whether a suspected flaw is exploitable

Plan and coordinate Strix security assessments across source code, running applications, APIs, and continuous integration pipelines. Combine findings into one prioritized remediation plan based on demonstrated impact, removing duplicates and documenting gaps in test coverage.

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

• Choosing suitable security tests for a product
• Planning a security assessment before launch
• Combining findings into a prioritized remediation plan

Assess REST, GraphQL, and gRPC APIs for authentication, access control, input validation, and business logic weaknesses. Use OWASP API Security Top 10, a framework of common API risks, to organize testing and document findings with reproduction steps and remediation.

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

• Comparing API access across user roles
• Checking token handling and request rate limits
• Assessing GraphQL access control and data exposure

Review Google Cloud workloads against the security principles of the Well-Architected Framework. Identify gaps in access control, network protection, data handling, and security operations, then receive prioritized recommendations linked to relevant Google Cloud products.

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

• Reviewing security during Google Cloud architecture design
• Checking access permissions and network defenses
• Identifying gaps in data protection and security monitoring

Review source code, dependencies, and infrastructure settings for security issues. Find exposed credentials, unsafe input handling, and access control gaps, then organize findings into a report with severity levels, affected locations, and recommended fixes.

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

• Review code security before deployment
• Find API keys and passwords embedded in files
• Check dependencies for known vulnerabilities

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

Turn validated Codex Security findings into tracked work in Linear, Jira, GitHub issues, or draft GitHub security advisories. Check for duplicates, preview exact content and audience, and record approved creations, updates, or reuse.

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

• Create issues from validated security findings
• Find and reuse existing issues for the same finding
• Register a reviewed batch of security issues

Audit an entire repository or a selected folder, package, or path in one review pass. Produce a security report with source evidence, severity assessments, and clear coverage limits, including unresolved questions that need further investigation.

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

• Run a standard security audit of a repository
• Review a selected folder or package
• Check findings alongside evidence and coverage gaps

Audit container images, Dockerfiles, and Kubernetes manifests for misconfigurations, excessive privileges, exposed secrets, and runtime risks. Use when the user mentions 'container security,' 'Docker security,' 'Dockerfile audit,' 'Kubernetes security,' 'K8s security,' 'pod security,' 'container hardening,' 'kubectl audit,' 'image scanning,' 'distroless,' 'rootless containers,' 'pod security policy,' 'pod security standards,' 'PSS,' 'network policy,' 'OPA Gatekeeper,' 'Kyverno,' 'runtime security,' or needs to review container or orchestration security.

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

Uses Postman to perform structured API security testing by building collections that test for OWASP API Security Top 10 vulnerabilities including authentication bypass, authorization flaws, injection, and data exposure. The tester creates environments with multiple user roles, writes test scripts for automated security validation, and integrates Postman with OWASP ZAP and Newman for CI/CD security testing. Activates for requests involving Postman security testing, API security collection, aut...

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

Review security measures in Java Spring Boot services, including identity checks, access permissions, input validation, and secret storage. Provides configuration examples and a release checklist covering API request limits, browser protections, logging, and dependency vulnerabilities.

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

• Adding authentication and access permissions
• Reviewing API input validation and SQL queries
• Checking browser protections such as CSRF and CORS

Check a codebase for known dependency vulnerabilities, hard-coded secrets, and risky code patterns using Ruflo security tools. Choose a scan depth, inspect matching lines, and report verified concerns with a clear account of what was checked.

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

• Checking pull requests for security regressions
• Inspecting authentication and input-handling code for risky patterns
• Running security checks before production deployment

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