---
description: >-
  Flows from our customers and research to best leverage Guardrail's
  capabilities
---

# Use Cases

For most teams with live products, monitoring on-chain contracts is an extension of monitoring other parts of their application stack (frontend, backend, api etc).

If you're interested in learning how to set up monitoring effectively, we have

* a monitoring 101 guide on our blog
* past hacks detailed with guards to detect them, and
* guides we share during onboarding to ensure maximum coverage and efficent set ups.

Every team on Guardrail has access to our suite of detection and response options. Teams can implement a **single guard and single response** or set up complete security workflows for **any scenario**.

### Detection <a href="#detection" id="detection"></a>

Guard categories and examples

<figure><img src="https://docs.guardrail.ai/~gitbook/image?url=https%3A%2F%2F3230447856-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FbQ5JZniHc3TOGfwx6gkt%252Fuploads%252FVByExAeXLsahHYaQ4S4c%252Fimage.png%3Falt%3Dmedia%26token%3D77fe59d5-e2f6-4783-8bc2-d790c6cf5378&#x26;width=768&#x26;dpr=4&#x26;quality=100&#x26;sign=47f20418&#x26;sv=2" alt=""><figcaption></figcaption></figure>

Guardrail supports different detection mechanisms, mostly covered by Invariants, Health Checks, or Suspicious Transactions. These are built using a team's experience in security and protocol design and our researched guards for every protocol component. More details in [_Creating Guards_](https://guardrail.gitbook.io/guardrail/Malu6yOPkyDb76ydUZ4I/core-features/markdown).

### Response <a href="#response" id="response"></a>

Guardrail acts as a workflow engine for executing response actions tied to each guard.

* **Critical Cases** (e.g., treasury drains, admin changes): Guardrail can page your team, adjust protocol settings, propose pauses, or trigger custom actions via webhook.
* **Operational Security** (e.g., token changes, governance approvals): Guardrail sends info alerts to community members or team members with relevant context for each trigger.
* **Unauthorized Protocol Activity**: Guardrail flags suspicious attempts, functioning like Two-Factor Authentication for critical protocol changes.
* **Monitoring Dependencies**: Guardrail triggers fallbacks and alerts for critical components when necessary.
* **User or Protocol Risk Workflows**: These alerts update protocol parameters or notify protocol users based on guards.
* Other supported security flows include: Rugpull Detection, Airdrop Security Scans, Off-Chain Security Checks; all these can be integrated into custom response flows tailored to your design.

**Guardrail's Success Criteria: Our platform is built around four key principles:**

1. **Consolidation**: Unify your security processes in one place.
2. **Simplification**: Streamline complex workflows.
3. **Standardization**: Apply consistent practices across your protocol.
4. **Automation**: Reduce manual intervention through automation
