CloudFlare Node

Once a Connection Manager has been set up, you can add nodes for Agentless scanning and monitoring. Cloudhouse Guardian (Guardian) supports CloudFlare nodes for Agentless scanning. The following topic describes how to add a CloudFlare node to your instance for monitoring.

Dependencies

To add a CloudFlare node, the following dependencies must be met:

  • Linux Connection Manager – Set up in Guardian. For more information, see Linux Connection Manager.

  • Cloudflare Account – Account set up, with the correct permissions.

  • Web API – Exposed and scoped according to requirements.

Add a CloudFlare Node

Adding a CloudFlare node to your Guardian instance lets you monitor and track the configuration of a CloudFlare service.

To add a CloudFlare node for Agentless scanning, complete the following steps:

  1. In the Guardian web application, navigate to the Add Nodes tab (Inventory > Add Nodes). The Add Nodes page is displayed.

  2. Select 'CloudFlare' from the list of node types and click the Go Agentless button to proceed. The Connect Agentlessly to [Node Type] page is displayed.

  3. Here, complete the following options:

    Option

    Description
    Connection Manager group drop-down list

    The Connection Manager group that is responsible for scanning your CloudFlare node. Select a Connection Manager group from the drop-down list.
    Email address field

    The email address associated with the API key.
    Website field

    The domain (website) you want to monitor. In CloudFlare, the domain is listed on the My Websites page (Dashboard > Websites > My websites). Enter the domain as it appears in CloudFlare, without any protocol fixes. For example, 'mywebsite.com'.

    Note: If you want to add multiple websites to Guardian, you need to add each website as an individual node.
    API key field

    The API key required to authenticate calls to the CloudFlare API. In CloudFlare, the API key is listed on the API Tokens page (Dashboard > User Profile > API Tokens > API Keys section > Global API Key > click View).

    Note: All calls to the CloudFlare API are rate-limited to 1,200 every 5 minutes.

  4. Once you've completed the above options click Scan Node to add the CloudFlare node to your Guardian instance.

Now, Guardian performs an initial scan of the node. You can wait on this page for the scan to finish, at which point you will see a View Scan button. To view the results of this initial scan, click View Scan. However, you can also navigate elsewhere while Guardian performs its initial scan of the node. You can then view the status of the scan on the Job History page (Inventory > Job History). For more information on what to do next after adding a node, see below.

Troubleshooting

Once you've scanned the CloudFlare node, if you receive an error in the Scan Report, you may want to troubleshoot the node's configuration. The following section describes how to troubleshoot the node parameters via cURL.

CloudFlare cURL

The following table describes the CloudFlare cURL values.

cURL Guardian Field
email Email address
a Website
tkn API key

Retrieve the List of Domains

To retrieve the list of domains, run the following script in a terminal window on the node.

Note: '-d' sets the POST parameter. The backslashes are only used to continue the command over multiple lines.

Copy 
curl https://www.cloudflare.com/api_json.html \
-d 'a=zone_load_multi' \
-d 'tkn=8afbe6dea02407989af4dd4c97bb6e25' \
-d 'email=sample@example.com' \

Retrieve DNS Records of a Given Domain

To retrieve the DNS records of the CloudFlare node's domain, run the following script in a terminal window on the node.

Note: '-d' sets the POST parameter. The backslashes are only used to continue the command over multiple lines.

Copy 
curl https://www.cloudflare.com/api_json.html \
-d 'a=rec_load_all' \
-d 'tkn=8afbe6dea02407989af4dd4c97bb6e25' \
-d 'email=sample@example.com' \
-d 'z=example.com'

Next Steps

Once you've added nodes to Guardian, there are a few next steps you can take to get the most out of Guardian and the data it collects. Refer to the topics below for more information on where to go from here.

  • Node Scan Results – View and filter the data collected by Guardian every time a node is scanned.

  • Node Groups – Group nodes together based on similar properties like node type, location, and more.

  • Scan Options – Customize what is scanned on a given node during a node scan.

  • Configuration Differencing – View differences between two nodes, a group of nodes, two scans of the same node, and more.

  • Policies – Define expected configuration states and apply them to nodes or node groups.

  • Integrations – Bring together different systems, applications, or components to work as a unified view and perform different tasks.