「escalation」の検索結果

Use when hunting Broken Object Level Authorization (BOLA) or Insecure Direct Object Reference (IDOR) vulnerabilities in APIs or web applications. Trigger on: "BOLA", "IDOR", "broken object level", "access other users", "object reference", numeric or UUID IDs in URLs or request bodies, user-scoped resources, horizontal privilege escalation, "change the ID in the request", second-order IDOR, blind IDOR, indirect reference, encoded ID, deprecated API version, JSON globbing.

日本語の概要は準備中です。原文の説明を表示しています。

AD Certificate Services attack playbook. Use when targeting misconfigured AD CS for privilege escalation via ESC1-ESC13 template abuse, NTLM relay to enrollment, CA officer abuse, and certificate-based persistence.

日本語の概要は準備中です。原文の説明を表示しています。

Exploit Active Directory replication privileges (DS-Replication-Get-Changes) to perform a DCSync attack, allowing an attacker to impersonate a Domain Controller and extract password hashes (like the krbtgt hash for Golden Tickets) without code execution on a DC.

日本語の概要は準備中です。原文の説明を表示しています。

Deep API security assessment beyond surface scanning. Covers the full OWASP API Security Top 10 (2023): Broken Object Level Authorization (BOLA / IDOR), Broken Authentication, Broken Object Property Level Authorization (mass assignment + excessive data exposure), Unrestricted Resource Consumption, Broken Function Level Authorization (BFLA / vertical privilege escalation), Unrestricted Access to Sensitive Business Flows, Server-Side Request Forgery via API parameters, Security Misconfiguration, Improper Inventory Management (shadow/zombie/deprecated endpoints, v1/v2 drift), and Unsafe Consumption of third-party APIs. Works across REST, GraphQL, gRPC, SOAP, and MCP servers. Discovers APIs from OpenAPI/Swagger specs, GraphQL introspection, gRPC reflection, .well-known endpoints, JS bundles, and traffic capture. Uses kiterunner, ffuf, schemathesis, restler-fuzzer, openapi-fuzzer, graphql-cop, clairvoyance, batchql, inql, jwt_tool, postman, mitmproxy, and manual http(action="request", ...) payloads. Every technique includes actual payloads, commands, and verification logic. Chains from /pentester or /codebase when API endpoints are discovered, chains into /web-exploit when classic injection points are found in API parameters, chains into /post-exploit when RCE is achieved, and chains into /ai-redteam when an LLM/AI endpoint is discovered (chat APIs, completion endpoints, RAG search, agentic tool-use, MCP servers).

日本語の概要は準備中です。原文の説明を表示しています。

Exploit Active Directory environments using Pass-the-Hash (PtH). This skill details how to authenticate to remote systems using the NTLM hash of a user's password instead of the plaintext password, enabling lateral movement and privilege escalation without cracking hashes.

日本語の概要は準備中です。原文の説明を表示しています。

Exploit Active Directory Certificate Services (AD CS) misconfigurations, specifically ESC1. By requesting a certificate based on a overly permissive template that allows the enrollee to supply a Subject Alternative Name (SAN), an attacker can impersonate highly privileged users (like Domain Admins) and seamlessly escalate privileges across the entire AD environment.

日本語の概要は準備中です。原文の説明を表示しています。

Identify and exploit Mass Assignment vulnerabilities in APIs. Use this skill when testing REST APIs or application forms that directly map user-supplied JSON or POST input to internal database objects. An attacker can inject undocumented variables (e.g., `is_admin`, `verified`) to illegally modify restricted properties.

日本語の概要は準備中です。原文の説明を表示しています。

Security Operations Center skill for alert triage, detection engineering, incident response, log analysis, threat hunting, SIEM queries, EDR investigation, timeline building, IOC handling, escalation notes, containment recommendations, and analyst-ready reporting. Use for blue-team operations, suspicious event analysis, and defensive cybersecurity workflows.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a Nutrition and Dietetics Technician, Registered (NDTR/DTR) — translating a physician's diet order into a texture/therapeutic tray specification, triaging a nutrition-screening or intake-decline signal for RDN escalation, auditing a tray line or food-safety log against a threshold, or drawing the line between routine dietetics work and a nutrition-diagnosis call that belongs to the supervising RDN.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a dental hygienist — full-mouth periodontal charting and staging, sequencing scaling and root planing across quadrants, deciding whether a finding needs escalation back to the dentist, or building a home-care compliance plan for a patient with active periodontal disease.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a Correspondence Clerk — selecting and customizing a template response to a standardized written inquiry, triaging a correspondence queue against SLA deadlines, deciding when a form letter suffices versus needs escalation, or auditing a response-template library for staleness.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a Computer User Support Specialist — triaging an inbound ticket's severity and SLA clock before troubleshooting it, verifying a caller's identity before any password/MFA/account-state change, walking a live incident through a structured troubleshooting sequence instead of guessing at a fix, deciding whether a request is an incident, a service request, or the underlying problem behind a string of incidents, or judging whether a ticket should resolve at tier 1 or genuinely needs escalation.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of an Acute Care Nurse — tracking early warning score trends across a higher patient ratio than ICU to catch silent deterioration before crisis, distinguishing expected post-operative recovery variation from a true complication requiring escalation, triaging competing needs across multiple simultaneous patients, balancing analgesia against oversedation risk by real-time response rather than fixed dosing, and verifying genuine discharge readiness rather than checking a form.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a Certified Anesthesiologist Assistant (CAA) working inside an Anesthesia Care Team — building and executing an intraoperative anesthetic plan under a directing anesthesiologist, reading a vital-sign trend for anesthesia-specific emergencies (malignant hyperthermia, local anesthetic systemic toxicity, awareness), deciding when a deviation is an immediate-escalation trigger versus an independently correctable event, or navigating the jurisdiction/concurrency limits of CAA practice.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of an Animal Caretaker — triaging daily husbandry when kennel census exceeds staffing capacity, reading a Fear-Anxiety-Stress (FAS) score change or appetite/output drop against an escalation threshold, deciding brush-out vs. shave-down on a matted coat, or setting isolation and vaccination-lead-time protocol for a new intake or boarding admission.

日本語の概要は準備中です。原文の説明を表示しています。

Build SaaS customer support — tiered support models, SLAs, macros, escalation, and support-driven product feedback.

日本語の概要は準備中です。原文の説明を表示しています。

Build AI chatbots end to end — conversation design, persona, retrieval grounding, escalation, and deployment. Use when creating a chatbot for support, sales, or internal assistance.

日本語の概要は準備中です。原文の説明を表示しています。

Extract a structured abstract from a commercial lease PDF — tenant/landlord identification, premises description + RSF/USF, lease term + commencement/expiration, renewal options (count, notice windows, fair-market rent reset), base rent schedule + escalations (fixed %, CPI-linked.

日本語の概要は準備中です。原文の説明を表示しています。

Audit mental health crisis monitoring systems for risk signal detection accuracy, escalation protocol completeness, safety planning integration, crisis team coordination, and ethical guardrail enforcement..

日本語の概要は準備中です。原文の説明を表示しています。

Assess team health using Patrick Lencioni's Five Dysfunctions of a Team model. Use when a leader says "my team feels off", "we have trust issues", "people aren't speaking up in meetings", "accountability is a problem", "we keep missing commitments", "the team is siloed", "we're not working well together", or "I want to do a team health check". Also trigger when someone describes symptoms like passive agreement in meetings, blame culture, missed deadlines without escalation, or people optimizing for their own metrics over team goals.

日本語の概要は準備中です。原文の説明を表示しています。

Run the current session as a senior developer (Opus) leading a configurable junior fleet. Decomposes requests into scoped tasks, dispatches junior-developer subagents in parallel, optionally runs an architect plan-review gate before dispatch, autonomously resolves escalations, optionally dispatches a doc-writer second wave after juniors complete, then integrates and gates with /test + /governance. Use when the user says "/dev-team", "run the dev team", "delegate this to the juniors", "act as the senior dev", or wants a task built by a senior-led fleet.

日本語の概要は準備中です。原文の説明を表示しています。

Use when defining or refining the tone, voice, and behavioral personality of an Agentforce agent: system instruction encoding, brand voice alignment, adaptive response formats, multi-persona strategies. NOT for writing the actual conversational copy — utterances, fallback messages, escalation phrasing — use admin/agent-conversation-design. NOT for topic scope design — use agentforce/agent-topic-design.

日本語の概要は準備中です。原文の説明を表示しています。

Use when testing, evaluating, or building regression suites for Agentforce agents: conversation testing in Agent Builder, topic (now subagent) coverage and utterance testing, Testing API and AiEvaluationDefinition metadata, Agentforce DX CLI test runs (sf agent generate test-spec, sf agent test create/run/resume/results/list), evaluation metrics (containment rate, escalation rate, CSAT, topic activation accuracy), and post-deploy analytics via Enhanced Event Logs. Triggers: 'how do I test my Agentforce agent', 'agent routes to wrong subagent', 'write utterance tests', 'regression test after topic change', 'measure agent quality', 'agent containment rate', 'run agent tests from the CLI'. NOT for agent creation, topic design, or action contract design — use agentforce/agentforce-agent-creation, agentforce/agent-topic-design, or agentforce/agent-actions respectively.

日本語の概要は準備中です。原文の説明を表示しています。

Configuring Salesforce Email-to-Case: Standard vs On-Demand mode selection, routing address setup, email threading via Lightning tokens, auto-response rules, attachment limits, and per-address case field defaults. Trigger keywords: email-to-case, routing address, on-demand email-to-case, email threading, case from email, email agent, routing address setup, Case.settings-meta.xml, EmailToCaseRoutingAddress, emailServicesAddress, isVerified, caseOrigin, enableThreadTokenInBody, useEmailHeadersForThreading, overEmailLimitAction, unauthorizedSenderAction, enableE2CAttachmentAsFile, saveEmailHeaders, newEntityRecordType, casePriority, EmailMessage.EmailRoutingAddressId, auto-response loop. NOT for the wider case layer (queues, escalation rules, case teams, entitlements) - use admin/case-management-setup. NOT for routing case work items to agents after creation - use admin/omni-channel-routing-setup. NOT for the email templates or letterheads themselves - use admin/email-templates-and-alerts.

日本語の概要は準備中です。原文の説明を表示しています。