FAQ - Why Synchronize Cloud Resources to ServiceNow CMDB

Synopsis and Purpose

Most organisations now depend extensively on cloud native resources, in Azure, AWS, or GCP (or multiples of these) to underpin the delivery of key IT applications and services. The breadth and depth of the dependency has grown exponentially and many organizations struggle in two key areas:

  1. Where can I see a consolidated view of all cloud native resources (across my multiple cloud providers)?

  2. How can I except a level of management and control over these cloud native resources?

This FAQ explains the basis for assessing cloud reasons when deciding “should I sync cloud native resources into my CMDB”, and if so, should I sync them all or just a subset. The Cloud Assessment Matrix below provides guidance on this specific topic.

The FAQ also explains how CI Sync’s Tag Synchronization capability can deliver valuable metadata (in the form of Cloud Tags) into your CMDB, so these attributes can be leveraged for high value business functions.

What benefits can I obtain from Synchronizing Cloud Resources

  1. Significantly increase the coverage and accuracy of cloud resources as input to your company’s compliance framework/s (NIS2, ISO27001, SOC2, NIST CSF).

  2. Drive improvements in core Service Management Processes (incident management, change management, problem management and service configuration management).

  3. Illuminate the ownership of cloud resources, and by implication identify unowned resources. Having owners assigned to cloud resources supports all of the following:

    1. Opens up lifecycle management of cloud resources. Run automated workflows in ServiceNow to contact cloud resource owners and confirm if their resources are till required or can be de-provisioned.

    2. Opens up cost reduction opportunities. Run automated cost reduction campaigns to cloud resource owners.

    3. Opens up service and application dependencies (on cloud resources) and drives ongoing accuracy of these dependencies by engaging cloud resource owners. Run automated workflows to gather service and application dependencies and keep them up to date.

  4. Bring service and application dependencies to life by providing a simple yet effect “home” to show the linkage between cloud resources and business applications (and business services) within ServiceNow.

Use the matrix below to systematically assess the reasons for populating cloud resources into your CMDB the leverage for the use cases and benefits noted above.

Why Synchronize Cloud Resources - An Assessment Matrix and Decision Making Matrix

Use the links below to see a full list of cloud resource record sets currently available in CI Sync (i.e. for extra record sets in addition to the sample ones shown below).

Assessment Category

Assessment Criteria

Sample AWS Record Sets

Sample Azure Record Sets

Sample GCP Record Sets

Questions the data can answer

Framework and practice impacting

Ticketable

Could someone raise an Incident, Problem (including Root Cause Analysis), or Change Request against the Cloud Resource.

Sample of available record sets

  • EC2 Instances

  • RDS Instances

  • Elastic Load Balancer

  • Lambda Functions

  • EKS Cluster

  • And many more


Record sets coming soon

  • API Gateway

  • CloudFront

  • ElastiCache

  • Route 53 hosted zones

  • Redshift


Sample of available record sets

  • Virtual Machines

  • SQL Server

  • App Service

  • Application Gateways

  • Kubernetes Services

  • Firewall

  • And many more


Record sets coming soon

  • SQL Managed Instance

  • Azure Cache for Redis

  • Service Bus

  • Container Apps; Bastion

Sample of available record sets

  • VM Instances

  • Cloud SQL Database

  • Clusters

  • Cloud Functions

  • Storage Buckets

  • And many more


Record sets coming soon

  • Load balancers (forwarding rules / backend services)

  • Pub/Sub

  • Spanner / AlloyDB

  • Filestore

  1. Which resource is affected by this incident, and which support group owns it?

  2. Is this resource production, and what else touches it before we approve the change?

  3. Which resource types generate the most incidents and changes?

  • ITIL 4 – Incident Management, Change Enablement, Service Configuration Management

  • SOC 2 – CC7, CC8

  • ISO/IEC 27001 – A.8.32 Change management

  • NIS2 – Art.21(2)(b) incident handling; Art.23 reporting

Owned and costed

Should the Cloud Resource have an accountable owner (because it incurs costs beyond immaterial spend).

Sample of available record sets

  • EC2 Instances

  • RDS Instances

  • S3 Bucket

  • EKS Cluster

  • Workspaces

  • And many more


Record sets coming soon

  • AWS Accounts

  • Redshift

  • FSx

  • Unattached EBS volumes

  • NAT gateways


Sample of available record sets

  • Subscriptions

  • Resource Groups

  • Virtual Machines

  • SQL Server

  • Storage Accounts

  • Kubernetes Services

  • And many more


Record sets coming soon

  • Databricks

  • Synapse

  • NetApp Files

  • Azure Virtual Desktop host pools

Sample of available record sets

  • Projects

  • VM Instances

  • Cloud SQL Database

  • Big Query Datasets

  • Clusters

  • And many more


Record sets coming soon

  • Folders

  • Persistent disks

  • Spanner / AlloyDB

  1. Who owns this resource, and which cost centre pays for it?

  2. Which resources are missing Owner or CostCentre tags?

  3. How many resources does each business unit run on each cloud?

  • ITIL 4 – Service Financial Management, IT Asset Management

  • APQC PCF – 9.0 Financial Resources, 10.0 Assets

  • ISO 55000

  • MoP – Financial management

  • NIS2 – Art.20 governance; Art.21(2)(i) asset management

Application Dependency

Does the Cloud Resource contribute to a Business Application (and therefore a Business Service).

Sample of available record sets

  • EC2 VPC

  • Subnets

  • Elastic Load Balancer

  • EC2 Instances

  • ECS Service

  • RDS Instances

  • SQS Queue

  • And many more


Record sets coming soon

  • Route tables

  • Transit gateways

  • VPC endpoints

  • Route 53

  • EKS node groups

  • API Gateway

  • Step Functions

  • EventBridge

Sample of available record sets

  • Virtual Networks

  • Load Balancers

  • Application Gateways

  • Virtual Machines

  • App Service

  • Event Hubs

  • DNS Zones

  • And many more


Record sets coming soon

  • Standalone network interfaces

  • Route tables

  • Service Bus

  • Event Grid

  • Container Apps

  • App Configuration

Sample of available record sets

  • Networks

  • Clusters

  • Applications

  • Cloud SQL Database

  • Redis Instances

  • And many more


Record sets coming soon

  • Load balancers (forwarding rules, backend services)

  • Managed instance groups

  • Cloud DNS

  • Pub/Sub

  1. Which Application Services are impacted if this resource fails?

  2. What infrastructure underpins the Payroll application service?

  3. Which shared resources (databases, load balancers) are single points of failure across several services?

  • ITIL 4 – Service Configuration, Service Level, Incident Management

  • ISO/IEC 27001 – A.5.30 ICT readiness for business continuity

  • NIST CSF 2.0 – ID.AM-03

  • BIZBOK – Capabilities

  • eTOM – Resource domain

  • NIS2 – Art.21(2)(c) business continuity; Art.23 impact assessment

Audit-evidenced

Should the Cloud Resource be registered to support a compliance requirement.

Sample of available record sets

  • S3 Bucket

  • RDS Instances

  • DynamoDb Table

  • Keys

  • Compute Security Groups

  • CloudFormation Stack

  • And many more


Record sets coming soon

  • Accounts

  • Backup vaults

  • Secrets Manager

  • WAF web ACLs

  • Route 53

Sample of available record sets

  • Storage Accounts

  • SQL Server User Databases

  • CosmosDb for MongoDb

  • Key Vaults

  • Network Security Group

  • Recovery Services Vaults

  • And many more


Record sets coming soon

  • Backup vaults (Data Protection)

  • User-assigned managed identities

  • Log Analytics workspaces

  • SQL Managed Instance

Sample of available record sets

  • Storage Buckets

  • Cloud SQL Database

  • Big Query Datasets

  • Projects

  • And many more


Record sets coming soon

  • Folders

  • Cloud KMS keys

  • Secret Manager

  • Service accounts

  • Firestore / Spanner / AlloyDB

  1. Which databases and storage accounts are hosted within which regions?

  2. Which in-scope data stores are tagged as holding PCI or PII data?

  3. Which data stores are covered by a backup vault (Recovery Services Vaults on Azure)?

  • ISO/IEC 27001 – A.5.9 Inventory of assets, A.5.12 Classification

  • SOC 2 – CC6.1

  • NIST CSF 2.0 – ID.AM-01/02/07

  • COSO – Principle 11

  • ISO 31000

  • NIS2 – Art.21(2)(i) asset inventory (Implementing Regulation 2024/2690); Art.21(2)(f)

Security Use Cases

Does the Cloud Resource inform Security Uses Cases (risk assessment, security incident investigation, transacts or holds sensitive data).

Sample of available record sets

  • Compute Security Groups

  • Keys

  • Aliases

  • EC2 Internet Gateway

  • Elastic Load Balancer

  • And many more


Record sets coming soon

  • WAF web ACLs

  • Secrets Manager

  • IAM roles

  • VPC endpoints

  • Elastic IPs

  • NAT gateways

Sample of available record sets

  • Network Security Group

  • Firewall

  • Key Vaults

  • Public IP Address

  • Application Gateways

  • Private End Points

  • And many more


Record sets coming soon

  • Bastion

  • User-assigned managed identities

  • Role assignments

  • Standalone network interfaces

Sample of available record sets

  • Networks and Subnets

  • And many more


Record sets coming soon

  • Firewall rules

  • Cloud KMS keys

  • Secret Manager

  • Service accounts

  • External IP addresses

  • Load balancer front ends

  1. Which internet-facing resources (public IPs, internet gateways) sit in front of production workloads?

  2. Which security groups / NSGs protect critical workloads?

  3. Which key vaults and keys protect which data stores, and who owns them?

  • NIST CSF 2.0 – ID.RA, PR.PS, PR.DS

  • ISO/IEC 27001 – A.8 Technological controls

  • SOC 2 – CC6, CC7

  • ITIL 4 – Information Security Management

  • NIS2 – Art.21(2)(a) risk analysis, (h) cryptography, (j) MFA / secured communications

High Value Cloud Tags and How to Use with CI Sync and ServiceNow for Business Benefits

Many organisations have introduced Cloud Tagging Standards, and are investing considerable time and effort to populate high value tags with valuable organisational metadata. High value Cloud Tags include:

  1. Owned By - Who is accountable for the cloud resource?

  2. Cost Centre - Which cost centre incurs the cost of the Cloud resource?

  3. Environment - Does the cloud resource underpin production IT/business functions, or is it only used for development or testing purposes?

  4. Application Dependency - Which business application (or applications) depend upon the cloud resource?

  5. Service Dependency - Which business service (or services) depend upon the cloud resource (if this can’t be automatically determined via the business application)?

  6. Supported By - Who is responsible for monitoring and supporting the cloud resource?

As soon as some, or all, of the above cloud tags contain values the data can be made available in ServiceNow using CI Sync’s Tag Synchronisation capabilities. With the data resident in ServiceNow, reporting, dashboards and automations can be readily implemented to deliver significant business benefits (as noted earlier in this FAQ).

Not only will CI Sync deliver the data to ServiceNow, CI Sync tackles the key challenges organisations face when trying to leverage cloud tags.

  1. CI Sync deals with inconsistent tag names. CI Sync is easily configured to treat “owner”, “ownedby”, “owned_by”, “business owner” (and as many other variations as you like) all as the same “owner” attribute.

  2. CI Sync deals with inconsistent tag values (the content within each tag). CI Sync is easily configured to remove a “cc” prefix from a cost center code entered as “cc4879093” rather than just “4879093”. CI Sync can append a domain suffix if values should contain a domain name but do not.

  3. CI Sync resolves tag values to ServiceNow master and reference data tables. CI Sync automatically resolves user oriented tag values (e.g. the owner expressed as an email address) against the ServicNow user table when persisting to the Owned_By attribute of a Cloud Resource CI in the CMDB. CI Sync will do the same for group oriented tag values, cost centre tag values and tags containing values associated with ServiceNow choice lists.

  4. CI Sync will create application dependency records in ServiceNow to automatically link cloud resources to existing Business Application CIs (allowing customers to show application dependent cloud resources). The same can apply to Business Services (if not automatically determined within ServiceNow).

For detailed information on how CI Sync performs the above using Cloud Tags (or even with custom attributes in platorms such as VMware), please read the following Syncfish FAQ: FAQ - Overview of Cloud Tag, Cloud Label and VMware Custom Attribute Synchronization Capabilities of CI Sync.

For More Information

Contact Syncfish for more information on the benefits of synchronizing Cloud Resources to your CMDB, and how to take advantage of the data once delivered.

  1. FAQ - Overview of Cloud Tag, Cloud Label and VMware Custom Attribute Synchronization Capabilities of CI Sync

Control Information

Created

Reviewed

Data Classification

PUBLIC
Classified in accordance with the Syncfish Data Classification Framework