'audit' 검색 결과

Inspect Linux scheduled tasks, services, shell profiles, shared library settings, and SSH keys for mechanisms that maintain attacker access. Correlate findings with audit logs to produce a timeline, risk scores, and remediation commands.

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

• Investigating how attackers maintained access to a Linux host
• Hunting for suspicious scheduled tasks and services
• Building a timeline from persistence-related audit events

Analyze Kubernetes API server audit logs to identify pod access, secret reads, permission changes, privileged pods, and anonymous requests. Use the event patterns to reconstruct suspicious activity and develop detection rules for security monitoring systems.

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

• Tracing API activity during a suspected cluster compromise
• Reviewing access to Kubernetes secrets
• Investigating permission changes and privileged pods

Prepares medical device quality systems for ISO 13485 audits using six focused questions. Reviews design records, corrective actions, process validation, risk files, post-market monitoring, and management reviews, then summarizes readiness gaps and three priority actions.

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

• Check readiness before an ISO 13485 internal audit
• Review design history files before a product launch
• Check evidence that corrective actions were effective

Prepare for FDA medical device quality audits through six evidence-focused questions. Review complaints, adverse event reports, process validation, manufacturing records, corrective actions, labeling, and inspection history, then organize readiness gaps and three next actions with owners.

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

• Preparing for an annual internal quality audit
• Reviewing readiness before an FDA inspection
• Organizing evidence for a Form 483 response

Prepare a codebase for an external security review by defining goals, running static checks, improving test coverage, and removing unused code. Assemble the review scope, verified build instructions, diagrams, and documentation into a package for auditors.

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

• Preparing a codebase for an external security audit
• Organizing fixes and missing tests before review
• Defining the review scope and a stable code version

Review LinkedIn posts and comments for artificial wording and mechanical sentence patterns. Get proportionate edits with explanations, audit a finished draft without rewriting it, or build a voice profile from previous posts.

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

• Polish an AI-drafted post
• Audit a finished post before publishing
• Find why a comment sounds unnatural

Diagnostic-only test suite auditor. Classifies repo type, maps against 7-layer testing taxonomy (git hooks → static → unit → integration → system → E2E → acceptance), runs deterministic quality gates (coverage, mutation, CRAP, architecture, escape-scan), builds RTM / personas / journeys traceability, produces TEST_AUDIT.md, updates tests/TESTING.md, and mandatorily hands off to implement-tests when gaps are found. Use when auditing test quality, finding test gaps, or running the full 7-layer sweep. Trigger with "audit tests", "find gaps", "test audit", "check test quality", "full sweep", "7-layer audit", "rtm check".

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

Audit a Node.js project's installed npm dependency tree for known CVEs by wrapping the npm audit JSON output and emitting findings in the canonical penetration-tester schema. Detects direct AND transitive vulnerabilities, normalizes npm's severity scale (info/low/moderate/ high/critical) to the shared Severity enum, and parses both v1 and v2 audit output formats so the skill works against npm 6 and npm 7+ lockfiles. Use when: pre-merge gate on a Node project, post-incident sweep after a transitive package compromise (e.g. event-stream, ua-parser, node-ipc, color.js), SOC2 vendor-management evidence collection, or auditing an inherited or acquired Node codebase. Threshold: any HIGH or CRITICAL CVE in the resolved dependency tree. MODERATE / LOW reported informationally. Trigger with: "audit npm deps", "npm vulnerability scan", "check node packages for CVEs", "npm audit".

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

When the user wants to run an SEO audit, technical SEO audit, or site health check. Also use when the user mentions "SEO audit," "technical audit," "site audit," "crawl audit," "indexing audit," "SEO health," or "fix SEO issues." For prioritization and organic strategy, use seo-strategy. For GSC data analysis, use google-search-console.

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

Master orchestrator for a full SEO audit suite powered by the Ahrefs MCP. Use this skill when running a comprehensive SEO audit, scoping a quarterly health check, doing pre-acquisition SEO due diligence, or post-migration verification. Triggers on full SEO audit, comprehensive SEO review, SEO health check, audit my site, SEO due diligence, audit suite, comprehensive audit, end-to-end SEO. Also triggers when a stakeholder wants the complete picture rather than a single-dimension audit.

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

Audit de conformité RGPD complet d'un site internet. Réalise une observation systématique du site selon une checklist de 10 sections (mentions légales, hébergeur, formulaires, newsletter, politique de confidentialité, cookies et bandeau, mots de passe, trackers et mesure d'audience, sous-traitants et transferts hors UE, accessibilité du recueil des droits) plus une annexe 22 items reproduisant les exigences des articles 13 et 14 RGPD. Produit un rapport structuré avec niveau de conformité global, points bloquants (risque 3), points de vigilance (risque 2), recommandations prioritaires et notes techniques. Le skill est tool-agnostique : il fonctionne avec un outil de navigation automatique (Claude in Chrome, Cowork ou équivalent) ou en mode dégradé copier-coller. Triggers : "audit RGPD site", "audit site internet", "vérifie ce site", "scanne ce site", "audit conformité site", "audite la conformité de [URL]", "audit cookies site", "audit politique de confidentialité site".

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

An SEO agent skill for quick, lightweight, default single-page SEO audits. Performs basic on-page and site-level checks and outputs a structured basic SEO audit report. Use when the user asks for "SEO audit", "SEO check", "check my page SEO", "page analysis", or wants a first-pass review of a URL. If the user requests "deep audit", "full report", "technical SEO audit", or "advanced SEO", use seo-audit-full instead.

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

Guides privacy audit risk assessment including risk universe development, inherent and residual risk scoring, control effectiveness evaluation, risk-based audit planning, heat map generation, risk appetite alignment, and audit prioritization by risk exposure. Covers the full audit risk assessment cycle from scoping through ongoing monitoring. Keywords: audit risk assessment, risk universe, inherent risk, residual risk, control effectiveness, risk-based audit planning.

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

Two-layer funnel audit on collected data only — stress-test the awareness layer (hooks, messaging, proof placement, attention leaks on live pages and ads) and the lead-capture layer (opt-ins and lead magnets scored on the four Value Equation variables, friction findings, weakest-magnet rewrite), plus a phone-path check under the Phone Capture Fit Rule. Use when "funnel audit", "audit my funnel", "why is my funnel leaking", "top of funnel isn't converting", "audit our lead magnets", "opt-in audit", "awareness to lead audit", "where are we losing people", "lead capture audit", or any request to diagnose the full awareness-to-lead flow rather than one page.

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

Write a clear, reviewable audit workpaper documenting procedures, evidence, and conclusions. Use when an auditor says "write a workpaper", "document this audit procedure", "tick and tie this", "I need to document my testing", "substantive testing workpaper", "controls testing documentation", "audit evidence memo", "prepare the workpaper for this balance", "document the audit steps I performed", or needs to capture any audit work in a format that supports review and sign-off. Also trigger when someone has completed audit testing and needs to write it up even if they don't use the word "workpaper".

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

Use when setting up or auditing how compliance documentation is structured, collected, and preserved for regulatory audit in Salesforce FSC — covering KYC data collection workflows, AML screening integration setup, audit trail configuration, and regulatory reporting readiness. Triggers: KYC form setup, AML integration configuration, compliance data collection, audit trail setup, regulatory documentation workflow, Field Audit Trail configuration, Setup Audit Trail, Event Monitoring, Discovery Framework, FSC KYC objects, Identity Document setup, Party Identity Verification. NOT for security implementation, NOT for designing AML/KYC architecture (use architect/aml-kyc-process-architecture), NOT for configuring who can access deal or client data (use admin/compliant-data-sharing-setup).

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

Produces structured U.S. legal audit summaries that distill compliance findings into executive-ready risk prioritization and remediation plans, covering likelihood/impact scoring, consequence analysis, and corrective actions with timelines and owners. Use for legal audits, compliance audits, regulatory audits, compliance gap analyses, risk assessments, audit report summaries, or remediation roadmaps. Trigger keywords: audit summary, compliance findings, audit report, risk prioritization, remediation plan, regulatory exposure, corrective action plan.

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

Use this skill when an external audit, attestation examination or assessment is coming and the team wants populations and evidence ready for the samples the auditor will pull, or asks "prepare for audit sampling", "what samples will the auditor ask for", "get our populations ready", "the auditor wants a list of all changes in the period", "evidence for the leavers sample", "Type II sample prep" or "how do we prove completeness of the population". Lists the populations an auditor is likely to sample, builds each from the system of record with the query that produced it, checks completeness and the evidence behind a dry-run sample, and writes a readiness file per population plus a list of gaps to fix before fieldwork.

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

Use this skill when the user asks about DOT audits, FMCSA compliance reviews, new entrant safety audits (NESA), focused investigations, what auditors actually ask for, audit document checklists, common audit failures, the audit ratings (Satisfactory / Conditional / Unsatisfactory), or how to prepare for an upcoming audit. Cite 49 CFR 385.

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

여러 기술로 구성된 코드를 감사하기 위해 외부 `repo-scan`을 고정 커밋에서 설치하도록 안내합니다. 소스를 검토하고 설치하는 절차이며, 이 스킬 자체는 감사를 실행하지 않습니다.

• 기존 코드 감사용 스킬 설치
• 대규모 리팩터링 전 감사 준비
• 소스에 포함된 외부 코드 감사 준비

Audit project dependencies for known vulnerabilities and outdated packages. Organize findings by severity, review proposed package changes before optional automatic fixes, and rerun the audit to check whether the reported vulnerability count decreased.

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

• Auditing third-party packages before a release
• Checking dependencies after installation or lockfile changes
• Investigating reported CVE advisories

Check third-party packages for known security vulnerabilities, review dependency versions and lock files, and plan updates or replacements. The skill also guides automated scanning in CI, the pipeline that runs project checks.

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

• Checking dependencies before a production deployment
• Investigating a reported package vulnerability
• Adding automated dependency scanning to CI

Create product comparison and alternative pages that help buyers evaluate options. Organize pricing, features, use cases, and migration details, and audit existing competitive claims for outdated information, missing evidence, or wording that overstates the facts.

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

• Creating a page comparing your product with a competitor
• Planning a list of alternative products
• Checking existing comparison claims for accuracy

Audit AWS, Azure, and GCP configurations against CIS Benchmarks, security configuration guidelines. Use automated scan results to identify failed checks, prioritize fixes, report compliance by area, and establish ongoing monitoring for configuration changes.

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

• Running an initial cloud security configuration audit
• Preparing CIS-related evidence for SOC 2 or ISO 27001 audits
• Prioritizing fixes for failed security checks