LogoLogo
APISupportDashboard
  • Welcome
  • Platform
    • Platform Overview
    • Getting Started Guide
    • Discovery
      • Domain Discovery
      • Network Discovery
      • Discovered Assets
    • Targets
      • Scan Policies
      • Add-on Services
      • Tags & Filtering
        • Default Tags
      • Managing Targets
      • Scan Configuration
    • Issues
      • Vulnerability Management
      • Issue Settings
    • Risk
    • Technology
    • Firewalls
      • Ports
      • HTTP Servers
      • DNS Records
    • Websites
      • Certificates
      • Scripts
      • Cookies
      • Headers
      • Forms
      • Links
      • Downloads
      • Traffic Hosts
      • Meta Tags
      • Pages
    • Reports
    • Events
      • Event Rules
      • Event Types
    • PCI Compliance
    • Automations
      • Target Automations
      • Asset Automations
      • Target Issue Automations
    • Projects
      • Penetration Testing
      • Other Projects
  • Integrations
    • Discovery Integrations
      • Azure
      • Google Cloud
      • AWS
      • Cloudflare
      • Linode
      • Akamai
      • Oracle Cloud Infrastructure
      • F5
      • GoDaddy
      • Wiz
      • HTTP
    • Workflow Integrations
      • Slack
      • Google Chat
      • Jira
      • PagerDuty
      • Splunk
      • AWS
      • Vanta
      • Microsoft Teams
      • ArmorCode
      • Zapier
        • Slack (via Zapier)
        • Jira (via Zapier)
        • Service Now (via Zapier)
    • Feeds
      • Using Feeds with Google Sheets
    • API
    • Webhooks
  • Account
    • Account Overview
      • Account Security
    • Users
      • Roles & Permissions
Powered by GitBook

© 2024 Halo Security

On this page
  • Preparing an HTTP file
  • Add an HTTP integration
  • Settings

Was this helpful?

  1. Integrations
  2. Discovery Integrations

HTTP

PreviousWizNextWorkflow Integrations

Last updated 16 days ago

Was this helpful?

HTTP integrations enable you to automatically import assets from files hosted online. With HTTP integrations, you can dynamically generate a file to integrate any existing service with Halo Security and ensure an accurate and up-to-date asset inventory.

Preparing an HTTP file

Start by hosting an HTTP file on the internet.

  • The content type should be text/plain.

  • The file should list IPs and/or hostnames, with each entry on a separate line.

An example file would look like this:

www.example.com
www2.example.com
111.111.111.111

Add an HTTP integration

  1. Visit your Settings → Integrations → .

  2. Add the HTTP integration.

  3. Add a name for your integration.

  4. Configure the settings.

Settings

  • Name: An internal name for this integration. You can use multiple HTTP integrations for different URLs.

  • Auto Run: Determines the frequency of adding assets from the file to your asset list.

  • URL: The location of the file.

    • Example: https://www.example.com/assets-list.txt

  • Headers: Optional HTTP headers for authentication or tracking.

  • Username / Password: Optional basic HTTP authentication credentials for accessing the URL.

  • Ignored Assets: Optional list of assets to ignore when parsing the file.

Add