ASM Q&A

Dears, I am actively seeing Censys actively scanning my Org’s environment. Useragent string from raw log :  mozilla/5.0 (compatible; censysinspect/1.1; +https://about.censys.io/) IP hitted so far : 66.132.195.34 & 66.132.186.188.Kindly please share what’s the next procedure as i wana exclude Censys to scan my Org’s data.. Regards

I’ve looked over the API docs https://app.censys.io/api-docs for ASM, but I am not sure what endpoint is used or if there is one to exclude assets from ASM. Is there an ability to do that from the API?I am trying to use Torq to set a quick action from their case management tool so that if we verify it no longer belongs to use, we can exclude the address or domain from Censys ASM.

What is the daily Censys scan time for ASM module of Censys?

I didn’t find a Integrations part. Kindly help me to find out

Has anyone found a way to filter, using queries or API, for assets that were found through Certificates?The only point I see in common is the source as “Censys Scan” but I need to narrow it down further.

This is a question we’ve received from a few customers and I wanted to share the info here for folks to use.Total number of assets (can be broken down by type by adding query=type%3AHOST, for example):curl -X GET "https://app.in.corp.censys.io/api/inventory/v1?workspaces=<INSERT WORKSPACE_ID>&query=%2A&pageSize=100&fields=type" -H "accept: application/json" -H "Censys-Api-Key: <INSERT ASM_API_KEY>"Total number of new assets (can be broken down by asset type as described above, edit the association_date as needed:curl -X GET "https://app.in.corp.censys.io/api/inventory/v1?workspaces=<INSERT WORKSPACE_ID>&query=association_date%3A%20%5Bnow-24h%20TO%20now%5D&pageSize=100&fields=type" -H "accept: application/json" -H "Censys-Api-Key: <INSERT ASM_API_KEY>"

Censys’s integration with Qualys VMDR Automatically add new hosts to your Qualys VMDR environment for vulnerability scans. With this connection, you can view and add Censys-discovered unknown hosts to Qualys asset groups.Below are sample API calls and links back to the Qualys API docs that are used in the integration. Please note that the calls differ based on Qualys User Permissions:If the user is a Unit Manager, the call to add IP to a subscription must include ag_title (Asset group title) and the actions of “Add IP to subscription” and “Add IP to asset group” will happen in one request. If the user is a Manager, the call to add IP to a subscription does not include ag_title, and the actions of “Add IP to subscription” and “Add IP to asset group” will happen in two requests.For all requests use header Accept: application/xmlUnit Manager:Add IP to subscription and asset group:https://<USERNAME>:<PASSWORD>@qualysapi.qg2.apps.qualys.com/api/2.0/fo/asset/ip/?action=add&ag

An easy way to accomplish this is using our new Saved Query Automation functionality in tandem with a saved query. For example, you could save the following query and use Saved Query Automation to receive an alert whenever assets are added that have critical risks or are removed:risks.severity="critical"This could just function as a starting point, however, and you might decided you want to target your query a bit. To make this more targeted, you could use the following query:tags: "critical-infrastructure" and risks.severity = *This would only return assets that you have applied the “critical-infrastructure” tag to and that have any risk associated with them. You could limit the severity to critical or high to narrow it further.

Censys ASM has built-in integrations with AWS, GCP, and Azure called Cloud Connectors. Each of these integrations can be set up in under 15 minutes using our in-app self-service wizard. Once you connect these CSPs with ASM, their attendant assets will be updated very frequently--in some cases, every 4 hours. A walkthrough of the setup process for our AWS Cloud Connector is available in our Censys Academy online courses.

Censys Attack Surface Management offers several ways to keep your monitored attack surface up-to-date. ASM users can input attack surface seed information like domains and CIDR blocks manually, utilize our programmatic seed discovery process, and connect their cloud services with ASM.The short answer to this question is to use all of the features available to you in ASM to maintain an accurate, up-to-date attack surface. Cloud Connectors and Censys seed discovery are particularly important to this end.ASM Enterprise customers can utilize automatic seed refresh in tandem with our programmatic seed discovery process. This daily search enables security teams to proactively manage changes from day-to-day adjustments in their digital footprint as well as more substantial moves like mergers and acquisitions.More info about how to seed your attack surface is available in our Knowledge Base and in our online courses on the Censys Academy.