Overview 💥
To maintain a secure and reliable integration between Liongard and your systems, you may need to allowlist certain endpoints, IPs, or URLs in your firewall, proxy, or network security tools.
Allowlisting is critical if you experience:
Connectivity issues with your Liongard instance
Integrations failing to authenticate or pull data
Agents unable to communicate with Liongard cloud services
⚠️ Important
This article focuses on network allowlisting for secure platform and integration communication. It does not modify inspector behavior unless specified.
Why Allowlisting Is Needed 🤔
Liongard uses secure HTTPS connections (TCP/443) to communicate between:
The Liongard platform (UI)
Cloud integrations (e.g., Microsoft 365, AWS, etc.)
Roar Agents installed on local systems
Network restrictions, strict firewalls, or geo-restrictions may block these connections, preventing proper alerting, data collection, or integration functionality.
Common Items to Allowlist 🛡️
Item | Purpose | Notes |
Application IP Address | Used to access your Liongard instance | In some cases, both the IP address and URL must be permitted for outbound HTTPS traffic (TCP/443). |
Platform URL(s) | Access Liongard UI and APIs | Include |
Integration IP Addresses | Cloud IPs used by Liongard to access integrations | Check integration-specific documentation for latest IPs or CIDR ranges. |
Agent Communication | Outbound communication from Roar Agents | Agents require connectivity to Liongard’s cloud endpoints for scanning and alerting. |
AWS Region | Geo-restricted access for cloud services | Most Liongard instances are hosted in US East (N. Virginia). Allow traffic to this region. |
Service Provider Name | For specific integrations or support cases | Contact Liongard Support to update or verify your service provider name if needed. |
ℹ️ Tip
Only allowlist the minimum required endpoints to maintain a secure network posture.
How to Configure 📝
Identify blocked endpoints
Check firewall or proxy logs for failed connections to Liongard platform URLs or cloud IPs.
Add allowlist entries
For IPs: Add Liongard’s platform, integration, and agent IP addresses to your allowlist.
For URLs: Allow outbound HTTPS (TCP/443) to Liongard platform URLs.
Verify connectivity
Log in to the Liongard platform to confirm access.
Run test scans via agents if applicable.
Confirm integrations (e.g., Microsoft 365, AWS) are successfully syncing.
Document changes
Keep a record of IPs, URLs, and firewall rules added for auditing and troubleshooting.
Best Practices ✅
Regularly review and update your allowlist as Liongard publishes new IPs or endpoints
Subscribe to Liongard Release Notes or Status Page for updates
Allowlist only what’s necessary to reduce security exposure
Use dedicated service accounts for integrations where possible
Monitor connectivity logs periodically to catch new blocks early
When to Contact Support 🫡
Reach out to Liongard Support if:
You’re unsure which endpoints/IPs to allowlist
You experience failed connections despite allowlisting
Integrations or agents are not functioning correctly
You need assistance updating your service provider name
💡 Tip: Include the blocked IPs, URLs, or error logs when submitting a support request to speed up resolution.
References 📚
