'exploit' 검색 결과

Audit Kubernetes access rules to find excessive permissions and service account token abuse paths. Trace which users or workloads could gain cluster administrator access, then produce prioritized findings and recommendations for reducing permissions.

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

• Reviewing Kubernetes privilege escalation paths
• Checking permissions after an RBAC change
• Tracing workloads with overprivileged service accounts

Investigate captured network traffic and connection records with Wireshark, Zeek, and NetFlow analysis. Identify communications with attacker infrastructure, trace movement between internal systems, estimate data transfers, and produce findings linked to packet evidence and timestamps.

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

• Investigating suspicious periodic connections
• Measuring the volume and destination of data transfers
• Tracing attacker movement between internal systems

Assess exposure of Windows secrets protected by DPAPI, the operating system’s data protection service, during authorized security tests. Guide examination and decryption of saved credentials and browser data using available user sessions, credentials, or backup keys.

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

• Assessing saved credential exposure in authorized tests
• Examining collected DPAPI files offline
• Reviewing protected browser and RDP credentials

Review code for security vulnerabilities using a checklist covering unsafe input, authentication, access permissions, secrets, and data exposure. Classify findings into four severity levels to distinguish exploitable flaws, issues needing investigation, and smaller improvements.

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

• Review SQL, shell commands, and HTML for unsafe input
• Check authentication and access permissions
• Find exposed credentials and sensitive log data

Compare documented permissions and data boundaries with actual code to find meaningful gaps. Produce findings that connect each documented rule to implementation evidence, identify who could exploit it and who is affected, and propose a concrete fix.

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

• Auditing code built by AI agents
• Checking access controls against documented permissions
• Finding gaps between documentation and code

Audit game code for save tampering, cheating, network weaknesses, input validation gaps, exposed data, and dependency risks. Produce a report with severity ratings, repair priorities, release recommendations, and explicit notes about areas that could not be assessed.

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

• Auditing game security before a public release
• Checking risks before enabling online or multiplayer features
• Reviewing save loading and external input handling

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

Map sensitive data across the systems you manage, explore what a compromised asset could expose, and maintain a risk register. Record likelihood, impact, owners, mitigations, and review dates to support ongoing security planning.

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

• Locating sensitive data across managed systems
• Assessing the impact of a compromised server or worker
• Recording risk owners, mitigations, and review dates

Trace a security finding from an attacker’s entry point to its impact using repository evidence. Examine access, permissions, existing defenses, and counterevidence to assess severity and decide whether the finding warrants reporting.

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

• Trace how an attacker could exploit a finding
• Reassess severity against existing defenses
• Check counterevidence before reporting

Evaluate supplied security findings against repository code and security policy without running the software. Classify each claim as confirmed, not actionable, or needing review, then rank relevant findings by exploitability and explain evidence gaps and next steps.

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

• Assess findings from a vulnerability scanner
• Review security tickets from Jira or Linear
• Evaluate GitHub alerts and security advisories

Assess smart-home and commercial mesh networks, where devices relay communications. Covers Zigbee, Thread, and Matter, with methods for observing radio traffic, reviewing device setup and key handling, and testing exposure of lighting, locks, and sensors.

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

• Planning a smart-home mesh security assessment
• Reviewing Zigbee lighting and lock controls
• Checking Thread network credential handling

Assess web applications and APIs for SQL injection, where input changes database queries. The skill covers finding vulnerable inputs, testing different database systems, automating checks, and documenting findings with remediation suggestions.

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

• Assessing web application inputs for SQL injection
• Reviewing GraphQL and WebSocket injection risks
• Combining SQLmap automation with manual verification

Plan and configure command and control (C2) systems for red team exercises. Covers major frameworks, communication methods, relay servers, certificate management, and the network or endpoint signals defenders use to detect these systems.

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

• Compare C2 frameworks for a red team exercise
• Plan communication methods and relay infrastructure
• Review C2 detection signals from a defender's perspective

Supports authorized security exercises that test data transfer outside a network. Organizes channel choices, compression, encryption, splitting, and receipt verification, alongside the monitoring signals defenders can use to identify different transfer methods.

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

• Comparing data transfer channels for an authorized exercise
• Planning compression, encryption, and file splitting
• Verifying received files against SHA-256 records

Investigate insecure deserialization, where restoring objects from stored or transmitted data can execute unwanted code. Covers multiple languages, input format recognition, vulnerable processing points, verification methods, and documentation of affected libraries and entry points.

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

• Reviewing code that restores objects from external data
• Identifying serialized data in cookies and request bodies
• Assessing message consumers and admission webhooks

Organize authorized phishing exercises from sending infrastructure and email scenarios to landing pages and reporting. Uses GoPhish campaign tracking to review opens, clicks, and submissions while assessing employee awareness and email security controls.

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

• Planning an authorized phishing exercise
• Preparing sending infrastructure and landing pages
• Reviewing email, QR code, and callback scenarios

Plan security testing for IoT and embedded devices, from circuit board inspection and firmware analysis to wireless links, companion apps, and cloud APIs. Includes tools, investigation checklists, and guidance for documenting findings.

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

• Planning smart home device security tests
• Analyzing firmware for embedded secrets
• Assessing industrial device communications

Test REST, gRPC, and WebSocket APIs for weaknesses in authentication, access controls, input handling, and configuration. Provides protocol-specific checks, tool guidance, and detection indicators to help document reproducible findings and severity during authorized assessments.

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

• Check access controls across users and roles
• Review token lifecycles and request limits
• Assess gRPC and WebSocket security

Assess weaknesses in the software supply chain, from dependency packages to build pipelines and distributed artifacts. Covers authorized proof-of-concept testing, package confusion, container image risks, signing abuse, and defensive checks for tampering.

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

• Assess dependency confusion risks in package registry settings
• Review tampering risks in CI/CD artifacts and container images
• Plan a non-destructive proof of concept and remediation report

Hunt for signs of compromise in web and application logs without an initial alert. Establish normal activity, record investigative hypotheses, check source code, and reproduce issues locally before producing incident records and a report.

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

• Hunting for compromise without an initial alert
• Tracing related activity across application logs
• Distinguishing attack attempts from successful exploitation

Evaluate supplied security findings against repository code and security policy without running the software. Classify each claim as confirmed, not actionable, or needing review, then rank relevant findings by exploitability and explain evidence gaps and next steps.

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

• Assess findings from a vulnerability scanner
• Review security tickets from Jira or Linear
• Evaluate GitHub alerts and security advisories

Trace a security finding from an attacker’s entry point to its impact using repository evidence. Examine access, permissions, existing defenses, and counterevidence to assess severity and decide whether the finding warrants reporting.

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

• Trace how an attacker could exploit a finding
• Reassess severity against existing defenses
• Check counterevidence before reporting

Test whether an agent misuses user trust by requesting secrets, making false safety guarantees, recommending unsafe actions, or impersonating authority. Confirmed issues are recorded with dialogue evidence, potential impact, and suggested improvements.

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

• Testing whether an agent requests passwords or private keys
• Checking for misleading safety guarantees
• Reviewing advice that could lead to unsafe operations

Explore web application vulnerabilities by class, including access control failures, XSS, and SQL injection. Use root causes, testing checklists, and examples to plan investigations and distinguish observable security impact from an initial warning sign.

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

• Study root causes of common web vulnerabilities
• Plan checks for cross-user access control failures
• Investigate upload and authentication weaknesses