'alerting' 검색 결과

Use this skill when an auditor, customer or regulator will ask how security events are logged and watched, and someone says "prepare logging evidence", "show we monitor alerts", "what do we log and for how long", "who looks at the SIEM", "prove an alert was handled" or "our monitoring evidence is just dashboard screenshots". Maps log coverage and retention per system, lists the alert rules that matter and where they go, traces real alerts end to end with timestamps, and writes an evidence pack with the gaps stated plainly.

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

Design production-ready observability strategies combining metrics, logs, and traces. Includes SLI/SLO design, golden-signals monitoring, alert optimization. Use when adding observability to a new service, refactoring alerting that is too noisy, or designing an SLO program before scaling production load.

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

Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.

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

Detects ransomware encryption activity in real time using entropy analysis, file system I/O monitoring, and behavioral heuristics. Identifies mass file modification patterns, abnormal entropy spikes in written data, and suspicious process behavior characteristic of ransomware encryption routines. Activates for requests involving ransomware behavioral detection, entropy-based file monitoring, I/O anomaly detection, or real-time encryption activity alerting.

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

Configures Fail2ban with custom filters and actions to detect port scanning activity, SSH brute force attempts, and network reconnaissance, automatically banning offending IP addresses and alerting security teams to suspicious network probing.

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

Builds automated threat intelligence feed integration pipelines connecting STIX/TAXII feeds, open-source threat intel, and commercial TI platforms into SIEM and security tools for real-time IOC matching and alerting. Use when SOC teams need to operationalize threat intelligence by automating feed ingestion, normalization, scoring, and distribution to detection systems.

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

Builds a structured vulnerability scanning workflow using tools like Nessus, Qualys, and OpenVAS to discover, prioritize, and track remediation of security vulnerabilities across infrastructure. Use when SOC teams need to establish recurring vulnerability assessment processes, integrate scan results with SIEM alerting, and build remediation tracking dashboards.

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

Monitors Certificate Transparency (CT) logs to detect unauthorized certificate issuance, discover subdomains via CT data, and alert on suspicious certificate activity for owned domains. Uses the crt.sh API and direct CT log querying based on RFC 6962 to build continuous monitoring pipelines that catch rogue certificates, track CA behavior, and map the external attack surface. Activates for requests involving certificate transparency monitoring, CT log auditing, subdomain discovery via certificates, or certificate issuance alerting.

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

- End-to-end passive reconnaissance for a domain, website or IP — builds an asset inventory covering registration, DNS, subdomains, infrastructure, tech stack, history and ownership without sending a single packet to the target. Use when asked to research or profile a domain or website, map what an organisation runs, or investigate a suspicious site without alerting its operator

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

'Use for alerting: desktop, sound, log, webhook, daemon.'

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

Prometheus, Grafana, logging, alerting, and data pipeline observability

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

Ensure designs define operability basics: SLO/SLI, monitoring, alerting, on-call actions, and incident handling expectations.

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

Designs and reviews production observability for mobile apps on every stack — Flutter, native Android, native iOS, React Native and Kotlin Multiplatform. Covers crash and error reporting with usable context, breadcrumbs, structured logs, traces and custom metrics, release and cohort segmentation, correlation with backend requests, alerting thresholds, sampling and cost, and what must never be collected. Use when production problems cannot be explained from the available data, when setting up crash reporting or telemetry, or when defining release health alerts.

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

Define and implement Service Level Indicators (SLIs) and Service Level Objectives (SLOs) with error budgets and alerting. Use when establishing reliability targets, implementing SRE practices, or measuring service performance.

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

Set up Prometheus for comprehensive metric collection, storage, and monitoring of infrastructure and applications. Use when implementing metrics collection, setting up monitoring infrastructure, or configuring alerting systems.

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

Use when working with Coralogix — coralogix observability platform for log analytics, metrics, tracing, security, and alerting. Covers log querying with DataPrime, metric exploration, alert management, parsing rules, and data usage insights. Use when searching Coralogix logs, investigating application errors, managing alert rules, or analyzing log ingestion patterns.

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

Configures Fail2ban with custom filters and actions to detect port scanning activity, SSH brute force attempts, and network reconnaissance, automatically banning offending IP addresses and alerting security teams to suspicious network probing.

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

Detects ransomware encryption activity in real time using entropy analysis, file system I/O monitoring, and behavioral heuristics. Identifies mass file modification patterns, abnormal entropy spikes in written data, and suspicious process behavior characteristic of ransomware encryption routines. Activates for requests involving ransomware behavioral detection, entropy-based file monitoring, I/O anomaly detection, or real-time encryption activity alerting.

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

Builds a structured vulnerability scanning workflow using tools like Nessus, Qualys, and OpenVAS to discover, prioritize, and track remediation of security vulnerabilities across infrastructure. Use when SOC teams need to establish recurring vulnerability assessment processes, integrate scan results with SIEM alerting, and build remediation tracking dashboards.

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

Builds automated threat intelligence feed integration pipelines connecting STIX/TAXII feeds, open-source threat intel, and commercial TI platforms into SIEM and security tools for real-time IOC matching and alerting. Use when SOC teams need to operationalize threat intelligence by automating feed ingestion, normalization, scoring, and distribution to detection systems.

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

Monitors Certificate Transparency (CT) logs to detect unauthorized certificate issuance, discover subdomains via CT data, and alert on suspicious certificate activity for owned domains. Uses the crt.sh API and direct CT log querying based on RFC 6962 to build continuous monitoring pipelines that catch rogue certificates, track CA behavior, and map the external attack surface. Activates for requests involving certificate transparency monitoring, CT log auditing, subdomain discovery via certificates, or certificate issuance alerting.

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

Build AI crisis monitoring and alerting systems. TRIGGERS - Use when user needs help with ai-crisis-monitor related tasks.

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

Implement comprehensive monitoring, logging, metrics, tracing, and alerting for production applications to ensure reliability and quick incident response. Use when setting up application monitoring, implementing structured logging, creating metrics and dashboards, setting up alerts, implementing distributed tracing, monitoring performance, tracking errors, or building observability into applications.

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

Use when introducing a feature flag system, choosing between release flags / experiment flags / operational flags / kill switches / permission flags, designing percentage rollouts, building kill-switch + circuit-breaker patterns, structuring evaluation contexts (user IDs, plan tier, region), or building flag-cleanup discipline. Triggers: LaunchDarkly / GrowthBook / Unleash / Flagsmith / OpenFeature, percentage ramp, sticky bucketing, kill switch wired to alerting, "we still have flags from 2 years ago", flag debt, OpenFeature provider, evaluation context, default value on provider failure. NOT for A/B test statistical analysis (separate skill), traffic-split routing at the edge, build-time bundler defines, or environment-based config.

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