Configure ChainPatrol security services for your organization
ChainPatrol offers multiple security services that can be configured based on your organization’s needs. Each service can be enabled independently and requires specific permissions and approvals before activation.
Where to find Services: Navigate to your organization settings → Services
The Detection service automatically scans various sources across the internet to identify potentially malicious assets targeting your brand or organization. This includes monitoring domain registrations, social media platforms, and other channels where threats commonly appear.
Ideal for:
Organizations that want proactive monitoring for brand impersonation
Teams looking to identify threats before they reach end users
Companies with significant online presence susceptible to phishing attacks
Prerequisites:
Complete your organization profile
Define your tracked assets (domains, social media handles, brand identifiers)
Ensure your team is ready to receive detection alerts
Required Approvals:
Organization Owner approval (if requested by a member)
This service continuously monitors the web for new threats to your brand, including phishing sites, scams, and impersonation attempts. When potential threats are detected, they’re automatically reported to ChainPatrol’s review system for validation and action.
The Reviewing service ensures that ChainPatrol’s security experts manually review all detected threats for your organization. This adds a layer of human validation to confirm threats are genuine and not false positives.
Ideal for:
Organizations that prioritize accuracy over speed
Companies concerned about false positives
Teams new to threat detection who want expert validation
Prerequisites:
Can be enabled immediately, alongside Detection and Monitoring services
Enable when you want ChainPatrol experts to validate all threats before action
Required Approvals:
Organization Owner approval (if requested by a member)
This service requires your organization’s administrators to review and approve all threats validated by ChainPatrol staff before they’re added to your organization’s blocklist. You can configure which types of assets (social media, domains, wallets, etc.) require this approval.
Ideal for:
Organizations with strict internal compliance requirements
Companies that want final oversight on all blocked content
Teams with industry-specific regulations requiring manual approval
Organizations that prefer to have control over what gets blocked
Prerequisites:
Enable after Reviewing service
Have designated administrators available to review proposals regularly
Enable before Wallet Blocking if you want approval control
Required Approvals:
None (can be configured directly by organization admins)
Required Legal Docs:
None
Configuration Options:
Enable/disable the approval requirement
Select specific asset types that require approval:
Domains
Social media accounts
Messaging apps
Crypto addresses
And more
If no specific types are selected, all asset types will require approval
Approved threats are added to ChainPatrol’s global blocklist, which is consumed by major cryptocurrency wallets and platforms, including Coinbase, MetaMask, and others. This prevents users from interacting with malicious addresses, domains, or contracts in real-time.
Ideal for:
Cryptocurrency projects and protocols
DeFi platforms
NFT projects
Web3 organizations
Any company whose users interact with blockchain wallets
Prerequisites:
1
Complete Organization Profile
Ensure all organization details are accurate
2
Configure Tracked Assets
Set up all assets you want to protect
3
Enable Core Services
Detection, Monitoring, and Reviewing must be active
4
Verify Configuration
Confirm organization assets and tracked asset scans are correct
Required Approvals:
Organization Owner approval (required)
Acknowledgment that organization assets and tracked assets are correctly configured
Required Legal Docs:
None
Important: Enabling Wallet Blocking has immediate impact on end-users. Organizations must verify their asset configuration is accurate before enabling this service.
For approved threats, ChainPatrol submits professional takedown requests to hosting providers, domain registrars, and platform administrators on your behalf. Our team handles the entire takedown process, including follow-ups and documentation.
Ideal for:
Organizations that want active threat removal, not just detection
Companies lacking in-house expertise for filing takedown requests
Teams that need to enforce intellectual property and trademark protection
Brands experiencing high volumes of impersonation or phishing
Prerequisites:
Enable Detection, Monitoring, and Reviewing services
Verify your organization has proper brand protection policies in place
Be ready for ChainPatrol to represent your organization in takedown communications
Required Approvals:
Organization Owner approval (if requested by a member)
Takedown requests are submitted automatically to hosting providers immediately after a threat is approved by ChainPatrol staff (and your organization, if Obligatory Organization Admin Approval is enabled). This provides the fastest possible response time for threat removal.
Ideal for:
Organizations experiencing high volumes of threats requiring rapid response
Companies with mature threat detection processes
Teams that trust ChainPatrol’s review process completely
Brands in high-risk industries (cryptocurrency, finance, e-commerce)
Prerequisites:
1
Enable All Other Services
All services must be enabled and functioning properly
2
Upload Power of Attorney
Valid POA document must be uploaded
3
Configure Website URL
Organization’s main website URL must be set
4
Validate Detection
Have confidence in the accuracy of your threat detection
Required Approvals:
Organization Owner approval (required)
ChainPatrol legal team approval
Required Legal Docs:
Power of Attorney (POA) document - Authorizes ChainPatrol to submit takedown requests on your behalf
Main website URL for your organization
Trademark registration documents
Authorized signatory information
Important: Automated Takedowns cannot be enabled without these prerequisites. The service will remain disabled until both the POA document and website URL are provided.
