'data leak' 검색 결과

Assess potential data breach impact by reviewing sensitive data and its movement through a codebase. Produce an inventory, exposure rankings, financial estimates, and prioritized safeguards, distinguishing legal source figures from planning estimates.

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

• Inventory sensitive data before a security review
• Trace where customer data could leak
• Estimate breach impact and costs for planning

의료 앱의 환자·직원·재무 기밀 정보를 분류하고, 의료기관별 접근 제어와 감사 기록을 설계하며 로그·주소·브라우저 저장소의 정보 유출을 점검합니다.

• 환자 기록을 다루는 코드를 점검합니다
• 의료기관 간 접근 제어를 설계합니다
• 기밀 정보의 조회와 변경을 기록합니다

Collect and organize victim postings from ransomware data leak sites through tracking feeds. Analyze group activity over time, compare sector and country patterns, and produce threat reports with risk assessments and defensive recommendations.

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

• Track monthly activity across ransomware groups
• Assess ransomware exposure by sector or country
• Identify newly observed ransomware groups

Marketing analytics and data-driven optimization for B2B SaaS campaigns. Use this skill when analyzing marketing performance, optimizing conversion rates, running A/B tests, conducting customer research, creating marketing dashboards, building attribution models, analyzing funnel metrics, or storytelling with data. Also triggers on: marketing ops, performance analytics, CRO, A/B testing, data storytelling, customer insights, tracking plan, event taxonomy, UTM taxonomy, GA4 audit, consent mode, instrumentation contract, sample size calculation, minimum detectable effect, test duration, not enough traffic to A/B test, statistical significance, Bayesian vs frequentist, sample ratio mismatch, experiment feasibility, martech stack, marketing tech stack audit, tool consolidation, build vs buy, vendor evaluation, shadow IT tools, ESP/CRM/platform migration, switching cost, cutover plan, suppression list migration, data portability, customer interviews, survey design, sampling frame, non-response bias, how many people should I interview, thematic saturation, voice of customer, jobs-to-be-done, buyer persona research, is this finding real, data enrichment, which enrichment provider should we buy, waterfall enrichment, contact data quality, match rate, our list data is bad, email verification, catch-all domain, accept-all, bounce rate from bad data, B2B data decay, how often should we re-verify contacts, ZoomInfo vs Apollo vs Clearbit evaluation, cost per usable record, where did this list come from, GDPR Article 14 notice, purchased list compliance, suppression screening, TAM list building, demand planning, marketing plan, how many leads do we need, what pipeline target should marketing carry, funnel model, top-down vs bottom-up plan, plan of record, annual marketing planning, quarterly planning, pipeline coverage we have to create, sales cycle lag, our leads cannot close this quarter, carry-in pipeline, scenario planning, conservative moderate aggressive forecast, stretch target, reforecast, re-forecast triggers, assumption register, capacity ceiling, addressable audience ceiling, marginal cost per lead, blended CPL is wrong, we missed plan and nobody knows why, AI policy for the marketing team, AI governance, AI acceptable use policy, which AI tools are we allowed to use, can I paste customer data into ChatGPT, shadow AI, AI use register, human review of AI output, when can we stop reviewing every AI draft, can the agent send on its own, the AI made a mistake now what, pull back AI autonomy, AI evals, our AI vendor changed the model, AI output went out wrong, prompt injection, can our AI read prospect replies safely, lethal trifecta, the AI leaked internal notes, turn off auto-generated ad assets, auto-applied recommendations, AI literacy training, EU AI Act Article 4, duplicate records in the CRM, dedupe before import, which value wins in a merge, CRM cleanup.

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

Test chatbots and AI agents for injected instructions, data leaks, and unauthorized access across accounts. It emphasizes reproducible evidence, verified external requests, and real data access rather than trusting the model's claims.

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

• Test document-based prompt injection
• Verify data leaks through tools or rendered images
• Check data isolation between accounts

Tests APIs for excessive data exposure where endpoints return more data than the client application needs, relying on the frontend to filter sensitive fields. The tester intercepts API responses and analyzes them for leaked PII, internal identifiers, debug information, or sensitive business data that the UI does not display but the API transmits. This maps to OWASP API3:2023 Broken Object Property Level Authorization. Activates for requests involving API data leakage testing, excessive data e...

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

Tests APIs for excessive data exposure where endpoints return more data than the client application needs, relying on the frontend to filter sensitive fields. The tester intercepts API responses and analyzes them for leaked PII, internal identifiers, debug information, or sensitive business data that the UI does not display but the API transmits. This maps to OWASP API3:2023 Broken Object Property Level Authorization. Activates for requests involving API data leakage testing, excessive data exposure, response filtering bypass, or API over-fetching.

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

Create, edit, and clean spreadsheet files, including Excel workbooks and CSV data. Add formulas, formatting, and charts, preserve existing workbook conventions, and recalculate formulas with error checks before delivering the spreadsheet.

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

• Clean messy CSV data into a spreadsheet
• Edit an Excel workbook while preserving its formatting
• Create a financial model with recalculating formulas

Create and update dashboards with charts, metrics, and tables drawn from connected data sources or attached files. Link displayed values to their sources so readers can inspect queries, calculations, and freshness while reviewing business indicators or recurring reports.

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

• Track KPIs and progress toward targets
• Visualize CSV, TSV, or JSON data
• Build recurring reports from connected data

Create charts and dashboards with a consistent approach to chart selection, color validation, labels, and interaction. Includes a palette checker and accessibility rules for readable visualizations in both light and dark modes.

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

• Choose a chart type that fits the data
• Validate chart colors for color vision differences
• Build charts for light and dark modes

Inspect supported local scientific files before modeling, summarize structure and missing values, and flag possible data leakage or outlier effects. Produces bounded aggregate reports with identifiers obscured and provides a structured analysis report template.

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

• Check local CSV or TSV data before modeling
• Audit missing values and overlap between data splits
• Compare outlier influence and transformation sensitivity

⚠️ CRITICAL USER EXPERIENCE-BASED SKILL - ALWAYS CONSULT BEFORE DATA PREPROCESSING ⚠️ Prevents catastrophic errors (88.9% error rate in V1.0 case study) through multi-level feature analysis, data leakage detection, and semantic validation. MANDATORY for: data preprocessing, feature engineering, standardization, normalization, interpolation, missing value handling, feature selection, or ANY data transformation task. Covers grouped time-series, cross-sectional, panel data. Detects: time travel leakage, causal inversion, ID misuse, semantic-numeric fallacies, distribution blindness. User's hard-won lessons from real project failures.

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

Identifies and exploits insecure local data storage vulnerabilities in Android and iOS mobile applications including unencrypted databases, world-readable files, insecure SharedPreferences, plaintext credential storage, and improper keychain/keystore usage. Use when performing mobile penetration testing focused on OWASP M9 (Insecure Data Storage) or assessing compliance with MASVS-STORAGE requirements. Activates for requests involving mobile data storage security, local storage exploitation, SharedPreferences analysis, or mobile data leakage assessment.

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

Assess the security of RAG systems, which retrieve documents to support AI answers. Test whether stored vectors expose source text, leak documents between tenants, or allow inserted content to dominate search results, then document findings and controls.

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

• Assessing source-text exposure from stored vectors
• Checking data isolation between tenants
• Testing retrieval manipulation in a test collection

Elite incident response and legal compliance guidance for data breaches under GDPR Articles 33 & 34. Use when: (1) User reports a data breach or security incident — including "is this even a personal data breach?" triage, (2) User asks about breach notification obligations or deadlines, (3) User mentions "72 hours", Art. 33, Art. 34, or notification requirements, (4) Discussion involves security incidents affecting personal data, (5) User needs breach risk assessment using ENISA methodology, (6) User mentions "Data Breach" or "Incident" or "Data Leakage" or "Ransomware" or "Exfiltration", (7) User needs to determine Controller vs Processor obligations, (8) Cross-border breach scenarios requiring Lead SA determination, (9) User needs a mitigation playbook or immediate response recommendations, (10) User needs audit-ready breach documentation (.docx) or an EDPB-template-aligned breach notification / evidence file — including follow-up and withdrawal notifications, (11) Breach involves an AI system requiring AI Act Art. 73 serious incident screening.

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

Assessing privacy risks in large language model outputs including training data memorisation, PII leakage in generated text, prompt injection leading to data extraction, and hallucinated personal data. Covers output filtering, guardrails, and monitoring. Keywords: LLM privacy, output risk, memorisation, PII leakage, prompt injection, hallucinated PII.

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

Audit whether a paper's EVALUATION DESIGN actually measures what it claims and whether its reporting is complete — the validity layer family D (experiment-forensics) cannot reach. Three patterns: train/test leakage means the reported score may not measure generalization (HP-EVAL-LEAKAGE — adopts the Kapoor & Narayanan 8-type / 3-category leakage taxonomy; the illegitimate-proxy / sampling-bias / pretraining-contamination subtypes hand off as needs_external_check, naming but NEVER running Oren-2023 exchangeability / Shi-2023 Min-K% / Golchin-2023 Time-Travel / BIG-bench canary); a load-bearing LLM judge is conflicted (same model/family as a compared system) or unvalidated (no human-agreement, no bias control) (HP-JUDGE-VALIDITY); a declared condition/metric is dropped or switched to favor the method, or 'best' is chosen with no held-out set (HP-SELECTIVE-REPORTING). Verdict-bearing at L0/L1 from the DESCRIBED protocol — NOT repo-gated like experiment-forensics; L2 only CONFIRMS against split/preprocessing/result files. A fresh cross-model reviewer (gpt-5.6-sol xhigh, read-only, fresh thread per pass) PROPOSES findings, each span-anchored to a ledger claim_id; tools/adjudicate_findings.py DECIDES the verdict. Leakage and under-reporting are usually HONEST methodological errors — every finding describes a discrepancy to CHECK, never an accusation. An LLM generating GROUND-TRUTH labels is HP-FAKE-GT (experiment-forensics) — routed there, not here. Emits eval-design-forensics.findings.json; computes NO verdict. Detect-only. Triggers: "eval design audit", "evaluation validity", "train/test leakage", "data leakage", "is the score measuring generalization", "LLM judge bias", "is the judge validated", "selective reporting", "cherry-picked results", "评估设计审计", "评测有效性", "数据泄漏", "训练测试集泄漏", "裁判模型有没有验证", "选择性报告".

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

Review a data analysis for quality, correctness, and reproducibility. Covers data quality assessment, assumption checking, model validation, data leakage detection, and reproducibility verification. Use when reviewing a colleague's analysis before publication, validating an ML pipeline before production deployment, auditing a report for regulatory or business decision-making, or performing a second-analyst review in a regulated environment.

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

Extract sensitive training data and internal capabilities from AI models through repeated programmatic querying. Use this skill when testing LLMs and ML models for data privacy leaks, intellectual property exposure, or unintended memorization. Covers membership inference, prompt extraction, training data reconstruction, and API boundary testing.

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

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.

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

Review AI skills and bundles without running their code. Checks for data leaks, suspicious permissions, hidden code, and system changes across desktop and mobile platforms, then reports flagged actions, risk scores, and suggested mitigations.

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

• Review an AI skill before installing it
• Check a skill bundle for data leaks and suspicious actions
• Inspect Android and iOS threats in skill files

Assess Bluetooth Low Energy devices by capturing wireless traffic, inspecting available data services, and checking pairing security. Identify signs of interception, reused commands, and data access that lacks authentication.

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

• Assess BLE security on IoT devices
• Check whether devices accept replayed commands
• Investigate suspicious pairing and device impersonation

Audit Python SDK logs, exceptions, and telemetry for sensitive data exposure. Trace values to their sources, fix confirmed leaks, and test that redaction hides sensitive information while preserving the caller's expected behavior.

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

• Audit logs and exceptions for sensitive data exposure
• Fix leaks involving model or tool data
• Test redaction and caller behavior

Test whether an AI agent reveals sensitive information through progressively stronger dialogue prompts. Check API keys, personal data, system instructions, and internal settings, then report findings only when sensitive content is actually accessible.

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

• Check for API key and credential leaks
• Test exposure of system instructions
• Inspect personal data and internal settings