Cloud Agent Scanning

Data storage continues to make a heavy migration to the cloud and file storage is no exception. Most organizations have made cloud-based file storage a fundamental part of their infrastructure. This includes cloud-based services such as Microsoft OneDrive, Google Drive, Microsoft SharePoint and even email storage.

This file data can contain sensitive information and understanding the scope of sensitive data storage is important when assessing the overall risk that cloud storage represents to the organization.

CYRISMA data sensitivity scanning offers the ability to scan this data for specific sensitive data and rate the level of risk based on the type of data and volume of sensitive information.

To perform the scan, a CYRISMA agent must be designated as a Cloud Scanning agent. Any Cyrisma agent version 1.3.12.422 or higher can be designated and perform as the cloud scanning agent for that Cyrisma instance. In order to assign an agent to the cloud scanning role, no other agent may be already assigned that role. In such a case, the first assigned agent must be unassigned before a different agent can be assigned as cloud scanning agent.

Cyrisma also offers one cloud scanning agent within the Cyrisma cloud infrastructure per Cyrisma instance. Both the Cyrisma-hosted agent and the local cloud agent can perform scans of cloud based resources.

Assigning the Local Cloud Scanning Agent

Within the instance, go to Admin -> Scan Agents and Edit the agent to be assigned the role of Cloud Scanning Agent.

In the update Agent settings, Select LOCAL CLOUD from the Type dropdown.

Agents must be successfully provisioned before they can be assigned. If another agent is already assigned, the LOCAL CLOUD option is greyed out. In that case, the other agent must be unassigned before proceeding.

Once assigned, scans of cloud resources can be performed using either a Cyrisma Cloud agent or a local cloud agent:

As in the case of any agent, if there are scans in progress, new scans will be launched once the agent completes any previous scan activities.

Since the LOCAL_CLOUD agent is local to the instance environment, it may also participate in normal, local scan activity such as Vulnerability or configuration Baseline scanning.

How to Set Up a Local Agent for Cloud Scans

For detailed instructions on how to configure your local agent to perform cloud scans, please refer to the comprehensive guide linked below: