Blog

Our existing customers have had early access to the first version of our cloud integrations feature for a while now. We're pleased to announce our next iteration of cloud integration monitoring that provides seamless monitoring of all public cloud resources.

The attack surface is increasing at an incredible rate due to the adoption of cloud. This means that organizations need more and more cloud resources. The adoption of multi cloud continues to surge, and more and more SaaS applications are being used in every department.

This makes it essential to have an inventory of all cloud assets. You must have visibility of all your unpatchable assets—the domains, hosts, resources, and IP addresses—that exist in your cloud accounts, and this inventory must be kept up to date.

And the Hardenize of today is already used to automatically and continuously keep inventory of your attack surface. We discover hostnames, certificates and IP addresses from a number of different sources including Certificate Transparency (CT logs), passive DNS, WHOIS records, certificates, host monitoring, DNS records, web page HTML, zone transfers, zone file uploads, and more.

Existing Hardenize customers had further visibility as our first cloud integrations release could import domain names and DNS zones from their cloud accounts, and certain certificate authorities, domain registrars, DNS providers and content delivery networks. This helped, but our customers wanted visibility of everything with a hostname and an IP address that was in their cloud environments.

We decided to build the following features to enable seamless monitoring of all exposed cloud resources in your AWS, GCP, and Azure cloud environments.

• Discover hostnames, even if they don’t correspond to your domain names. Even if cloud assets were public-facing, they couldn’t always be discovered. Many cloud resources still use the default hostnames assigned by cloud providers rather than custom names. So we needed to be able to identify hostnames or IP addresses of the resources used by interfacing directly with the cloud accounts.
• Add and remove dynamic cloud network assets. Hostnames and IP addresses created for cloud services are often ephemeral. Multiple assets are created, updated, and deleted every day. We needed to be able to reflect those changes to your inventory in Hardenize.
• Identify the type of resource provided by the asset. Understanding what the resource is that’s provided by the asset is useful for you to know in a number of scenarios. For example, some vulnerabilities can be particular to certain resource types only.

So now, when a cloud integration is configured, Hardenize will:

• On a daily basis, check for different types of assets including domain names, DNS zones, and cloud resources-compute instances, load balancers, storage, and more—in each cloud account configured.
• Import any new assets that are found in your cloud accounts to Hardenize and begin monitoring the configuration of the asset. Assets are monitored in the same way as all other assets including host assessment and network scanning.
• Remove any resources from Hardenize that no longer exist in your cloud account.
• Provide you with information to help understand where the assets have originated from and what type of resource the asset is.

Beta customers that used the new cloud integration discovered 6 times the assets compared to traditional ASM methods.

If you have a Business or Enterprise plan, then Cloud Integrations is available now. Visit the Docs section in Hardenize to get started. If you are on a Starter or Teams plan and would like to add Cloud Integrations to your plan, get in touch with your Customer Success Manager.

If you’re not a Hardenize customer, request a demo and a trial account here.