1. Censys
  2. Censys Attack Surface Management
  3. Security Integrations

Other Articles In This Section

In this article:

Censys ASM Integration Proxy Setup

  • Updated

Integrate data from the Censys ASM platform with the rest of your security tool chain securely and safely by running a proxy server for credential management.

With the Censys Proxy, your organization has complete control over access to your downstream security-related applications.

Integrations Supported by the Censys Proxy:

  • Service Now

  • Jira (Jira Software Cloud or Jira Server 8)

  • Tenable.sc version 5.18.0

Set Up the Proxy

To configure the proxy’s connection to your integrated apps, you need account credentials for each integration you wish to use, and the URLs of your application instances.

Provide Environment Variables

Provide the following environment variables to the Docker image via your preferred method (e.g., a .env file or a Helm template):

  • Integration Key

    Visit the Integration Proxy Configuration Page to obtain your integration key.

    Proxy configuration page

  • ASM Secrets

    A map containing the credentials of the applications to be integrated. Learn more here.

  • Base URLs

    The URLs of the applications to connect to.

Environment Variables Template

ASM_INTEGRATION_KEY=<Integration Key from Censys ASM>
ASM_SECRETS=<JSON Object>
ASM_BASE_URLS=<JSON Object>

Environment Variables Example

ASM_INTEGRATION_KEY=5692f45a-XXXX-XXXX-XXXX-29k177445e12
ASM_SECRETS={"JIRA_USERNAME":"example@censys.io","JIRA_API_KEY":"jira-key","SERVICENOW_USERNAME":"example@censys.io","SERVICENOW_PASSWORD":"randomlyGeneratedPassword","TENABLE_ACCESS_KEY":"tenable-key","TENABLE_SECRET_KEY":"tenable-secret"}
ASM_BASE_URLS={"jira":"https://example.atlassian.net","servicenow":"https://venXXXX.service-now.net","tenable":"https://sc.tenalab.online"}

Pull and Run the Image

With your environment variables configured to be provided to the Docker image, deploy the proxy with the following command:

docker run --rm --name censys-asm-proxy gcr.io/censys-io/asm-proxy:latest

Confirm Connection on the Integrations Page

Refresh the Integrations page to confirm that the proxy can successfully reach the Censys ASM platform and that your applications are connected.

Proxy connected

Now you’re ready to begin using your integration!

Appendix: Integration Permissions, Credentials, & URLs

Look up the permissions required for each integration to work and review the information that must be supplied to the proxy to properly connect the application to the Censys ASM platform.

Jira

In order to take securely leverage the Jira ticketing workflow in the ASM app, Censys recommends creating a dedicated Jira user with the following permissions.

Permissions

Permissions required for the Jira integration to work are marked with an asterisk (*):

  • BROWSE_PROJECTS* — Allows Censys to display a list of projects to choose from during issue creation.

  • CREATE_ISSUES* — Allows Censys to create a Jira issue.

  • VIEW_ISSUES* — Allows Censys to display and refresh issues created through the integration.

  • ASSIGN_ISSUES – Allows assigning of issues to Jira users through the integration.

  • MODIFY_REPORTERS — Allows the issue reporter to be set through the integration.

Credentials

Authentication credentials for Jira include a username and API key and are provided to the proxy in a JSON object labeled ASM_SECRETS.

  • JIRA_USERNAME - An email address for the user account

  • JIRA_API_KEY - A base64-encoded string generated for programmatic access

URL

The URL of your organization’s Jira instance is provided as a key-value pair in a JSON object labeled BASE_URLS.

Jira URLs are commonly formatted like this: yourcompany.atlassian.net

Service Now

In order to use the Service Now ticketing workflow in the ASM app, Censys recommends creating a dedicated Service Now user with appropriate permissions.

Permissions

Roles required for the ServiceNow integration to work are listed below:

  • import_transformer

  • incident_manager

  • itil

  • rest_service

  • snc_platform_rest_api_access

Credentials

Authentication credentials for a Service Now user include a username and password and are provided to the proxy in a JSON object labeled ASM_SECRETS.

  • SERVICENOW_USERNAME - An email address for the user account

  • SERVICENOW_PASSWORD - A password for the user account

URL

The URL of your organization’s SNow instance is provided as a key-value pair in a JSON object labeled BASE_URLS.

Service Now URLs are sometimes formatted like this: venXXXX.service-now.net

Tenable.sc

In order to securely leverage the Tenable workflow in the ASM app, Censys recommends creating a dedicated Tenable user for the integration and supplying those credentials to the proxy.

Permissions

Permissions required for the Tenable.sc integration to work are listed below:

  • Group: All Access (default) - Allows the account to view all hosts in the Tenable instance.

  • Permissions: Security Analyst - Allows the account to read, create, and manage asset lists and view scan results.

Credentials

  • TENABLE_ACCESS_KEY - A randomly generated identifier associated to a Tenable account

  • TENABLE_SECRET_KEY - String generated to authenticate programmatic access

URL

The URL of your organization’s Tenable.sc instance is provided as a key-value pair in a JSON object labeled BASE_URLS.

Tenable.sc URLs are sometimes formatted like this: tenable.example.com

Related articles

Comments

0 comments

Article is closed for comments.