This page provides a glossary of terminology with definitions for DivvyCloud-specific terminology as well as some useful cloud-based terms.
“Application program interface, a set of functions and procedures allowing the creation of applications that access the features or data of an operating system, application, or other service.”
DivvyCloud’s API can be used to create insights and bots, modify compliance packs,and perform other functions outside of the DivvyCloud user interface. See the API documentation for details.
Amazon Web Services, Amazon’s cloud platform
A User with the highest level of privileges or authorizations. Admins generally will retain all permissions to read/view, write/edit, delete, etc. There are two types of Admins, Domain Admins and Org Admins. A Domain Admin can do everything in the tool. An Org Admin can do everything operational in their organization in the tool.
See also Domain Admin and Org Admin.
External Active Directory/LDAP (lightweight directory access protocol) servers for user authentication.
These servers can be connected and managed from the Authentication Servers tab of the Identity Management page.
Background Jobs are worker processes that run on a schedule to keep DivvyCloud current (e.g., harvesting Insights) and optimized (e.g., OrphanedResourceCleanup). Background Jobs are distinct from OnDemand jobs in that they are not run immediately. Resource harvest jobs, which can be accessed via the Cloud details section, can be thought of as specialized Background Jobs.
A DivvyCloud internal ID for clouds. Badges are similar to Tags (key/value pairs applied to individual resources), but applied to entire cloud accounts.
Badges are used in DivvyCloud to scope bot actions, report on compliance, bound searches, and otherwise customize the organization of cloud accounts.
An Insight pack used as the basis for creating a customized pack.
Bot (short for ‘robot’) is an automated program that executes user-defined actions on resources according to user-defined conditions. Bots are composed of scope (bounds for which resources the Bot acts upon), filters (conditions upon which the Bot will act), and actions (what the Bot does).
The DivvyCloud feature where the user creates bots, defining the bots’ scope, conditions, and actions.
The combined practices of continuous integration (CI) and continuous deployment (CD) for developing software in a sustainable way.
A cloud, or cloud account, is an account for cloud services (storage, compute, etc.) from a cloud services provider (Cloud Provider), such as AWS, GCP, Azure, and other. You can have multiple accounts (‘clouds’) from a single provider; you can use multiple providers to create your overall cloud infrastructure.
Conformity with industry requirements and standards for cloud-related security, cost, and other controls. Compliance across multiple cloud providers is a major focus of DivvyCloud.
Compliance packs are collections of related insights pertinent to a specific compliance standard. Compliance packs may focus on security, costs, governance, or combinations of these across a variety of frameworks. Examples are NIST 800-53, ISO 27001, HIPAA, and PCI DSS. Compliance packs are accessed from the Compliance Packs tab on the Insights main page.
A DivvyCloud feature that visually summarizes cloud accounts’ adherence to specific rules or conditions of an Industry Standard, e.g., NIST 800-53 or ISO 27001. This summary is presented as a heat-map type visual; the Compliance Scorecard also provides guidance concerning actions to take on specific resources to mitigate failing issues. Check out more information - Compliance Scorecard.
Relative to EDH, a central account that ingests events from one or more Producers. See also Event-Driven Harvesting (AWS).
A Compliance Pack, customized for specific uses. Custom packs can be created from existing--or base--packs, and adding or removing specific Insights as desired. Custom Packs are found on the Custom Packs tab of the Insights main page.
A collection of strings of data definitions that can be used (and reused) in creating and updating Filters, Insights, and Bots.
A disabled resource is a resource that is not harvested. As such, DivvyCloud will not surface permissions errors related to harvesting disabled resources.
DivvyCloud is a Cloud Security Posture Management (CSPM) platform that provides real time analysis and automated remediation across leading cloud and container technologies, including AWS, Azure, GCP, Alibaba, and Kubernetes. DivvyCloud protects cloud and container environments from misconfigurations, policy violations, threats, and IAM challenges.
Once installed, connected to your clouds, and configured, DivvyCloud discovers your infrastructure resources across all clouds and distills this information into a normalized database. This database is then used to analyze cloud operations, identify risks, and take action—again, according to user-defined policies and rules—to alert, mitigate, or remediate problems.
A User with the highest level of privileges or authorizations. A Domain Admin can do everything in the tool. There are also Read-only Domain Admins who are able to view all resource data among all DivvyCloud organizations, yet as the name implies, they are not able to make changes to DivvyCloud, but are read-only. See also Admin and Domain Admin.
Entitlements, or Permissions Entitlements, give domain users control over basic users' and organization admins' permissions to access certain parts of the tool. As of v19.2, these entitlements are available for BotFactory, Tag Explorer, Insights, and Scheduled Events. The four possible permissions levels are "disabled", "viewer", "editor", and "admin". Entitlements are assigned independently to features, e.g., a basic user might be "disabled" for BotFactory, but have "editor" permissions for Tag Explorer.
Event-Driven Harvesting (EDH)
Event-driven harvesting (EDH) is a data collection mechanism where events are pushed to DivvyCloud instead of being collected via polling. AWS EDH leverages CloudTrail and CloudWatch events for collection. GCP EDH leverages StackDriver and Pub/Sub events for collection.
Relative to AWS EDH, event-driven roles are either Consumer or Producer.
A Resource Group that defines a collection of resources that are not evaluated against a specific Insight. For example, S3 buckets configured to host websites can be placed in a Resource Group called “Websites” that is then exempted from the Insight “Storage Container Exposed To The Public”.
An Insight that matched a scoped resource. In other words, a resource met the conditions of this Insight when a query was run.
Filters specify conditions DivvyCloud searches for in identifying matching resources. An example filter: ‘Resource is not encrypted’.
Filters are used in Insights and Bots. Insights combine filters, scope, and reporting. Bots take action based on the output filters, scope, and insights.
Google Cloud Platform
Harvesting describes how DivvyCloud collects data from the cloud providers:
A resource within the specified scope that matches a designated (searched-on) Insight. Impacted resources indicate violations on an Insight.
With respect to cloud computing, infrastructure refers to an enterprise's entire cloud-based or local collection of resources and services. This term is used synonymously with ‘cloud footprint’.
An Insight describes a specific behavior, condition, or characteristic of a cloud resource. Insights are the checks—built on a combination of one or more filters and scopes—that are run on your infrastructure. They can be used to report on resources, or to instruct Bots as to which resources require actions. Some examples of common insights include:
Insights can be used individually or in packs.
A collection of Insights, usually focused on the same type of issue, e.g., security, compliance, governance.
A user-defined designation for the severity of an Insight. Severity levels are: Moderate, Major, Severe, and Critical.
Refers to a virtual server instance from a public or private cloud network.
External systems with which DivvyCloud is designed to interface for both inbound (data aggregation, data collection) and outbound (notifications, ticketing) actions.
The number of harvest jobs that are enqueued and waiting on a worker node to process. Job backlogs can rise and fall. For example, adding clouds will cause the job backlog to rise as the initial cloud harvests are scheduled. The number of harvest jobs feeding into the job backlog can be greatly influenced by the cloud harvesting strategy selected; more aggressive strategies lead to more jobs.
The process responsible for scheduling jobs performed by the workers. The scheduler will schedule regular cadence jobs, such as harvesting, as well as on-demand jobs. It maintains different priority queues to help surface high priority jobs.
A Google-based, portable, extensible open-source platform for managing containerized workloads and services.
Multifactor authentication (MFA)--also known as two-factor authentication (2FA or TFA)--enhances security by verifying a user's identity using multiple methods of authentication from independent categories of credentials.
A User with the highest level of privileges or authorizations. Admins generally will retain all permissions to read/view, write/edit, delete, etc. An Org Admin can do everything operational in their organization in the tool. See also Admin and Domain Admin.
In DivvyCloud, organizations allow for complete isolation between cloud accounts, resources, and users on an installation. Cloud accounts and their resources can only belong to one Organization and cannot be modified or viewed from another Organization.
Note: GCP uses ‘Organization’ to refer to a collection of projects.
Refers to Owners of resources. Can only be set by Admins. Ownership can be used to set scope on resource searches, making it easier for the user to focus on the resources they care about.
The cloud provider-defined permissions granted to DivvyCloud to enable harvesting resource information and allowing DivvyCloud to take resource management actions. These permissions can be read-only, admin, or some combination of the two. With each release, DivvyCloud expands its supported resources and correspondingly requires additional permissions to harvest those resources.
An element of a software program that can be added to provide support for specific features or functionality.
Collections of permissions that provide DivvyCloud user-defined access to connected accounts. Policies can range from Standard User Policy, containing read-only permissions, to a Power User Policy, allowing DivvyCloud to execute user-defined actions within accounts.
Relative to EDH, a Producer is an AWS account that is configured to forward cloud events to another account. See also Event-Driven Harvesting (AWS).
The allocation of a cloud provider's resources and services to a customer; such services include IaaS, PaaS, or SaaS. In DivvyCloud, ‘Provisioning’ can also refer to the permission that a user has been given to acquire or add such services to their cloud account.
A geographic location in which public cloud service providers' data centers reside.
A virtual (cloud-hosted) service, utility, or function. Cloud accounts are made up of resources; while different providers use different names in referring to their specific offerings, DivvyCloud uses normalized names throughout the tool for these resources. For example, AWS’ S3 Bucket, GCP’s Cloud Storage, Azure’s Blob Storage Container, and Alibaba’s Object Storage Bucket all refer to storage resources; DivvyCloud refers to all of these as Storage Container.
Check out more under Resources.
Collections of resources; can be used to apply granular permissions to a subset of a cloud footprint, to improve visibility or to apply custom policy.
Resource Type Categories
Categories of resources by type. DivvyCloud uses five normalized categories: Compute, Containers, Storage, Network, and Identity & Management.
Roles are used to manage the permissions of basic users. They can be customized to permit read, manage, and delete privileges. They can be customized to view all resources or resources defined by Cloud account, Resource Group, or Badge. (Note: while roles relate to users generally, entitlements relate to a users' ability to interact with specific portions of the tool, e.g., Tag Explorer or BotFactory.)
Scopes define the domain (limits or bounds) on clouds and resource groups in searches, displays, and bot actions.
Two-factor authentication (also 2FA or MFA)--enhances security by verifying a user's identity using multiple methods of authentication from independent categories of credentials.
A key/value pair used for identifying and labelling resources.
DivvyCloud users are distinguished by type: Basic User or Organization Admin (Org Admin). Basic Users can be assigned various roles and permissions or privileges. These characteristics are established in the Identity Management portion of the tool. Org Admins have all privileges confined to a single DivvyCloud organization.
See also Roles, Domain Admin.
A list of users linked to a list of Roles. User Groups are leveraged in conjunction with Roles to grant permissions to Basic Users.
A generic term for a process that does something other than serve web requests. It may process a queue, run scheduled jobs using process files, or any number of other support-type activities. It generally does not interface with users.
Updated 2 months ago