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:
-
Where can I see a consolidated view of all cloud native resources (across my multiple cloud providers)?
-
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
-
Significantly increase the coverage and accuracy of cloud resources as input to your company’s compliance framework/s (NIS2, ISO27001, SOC2, NIST CSF).
-
Drive improvements in core Service Management Processes (incident management, change management, problem management and service configuration management).
-
Illuminate the ownership of cloud resources, and by implication identify unowned resources. Having owners assigned to cloud resources supports all of the following:
-
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.
-
Opens up cost reduction opportunities. Run automated cost reduction campaigns to cloud resource owners.
-
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.
-
-
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).
-
For Azure: Rule 1 - Azure Record Sets for Resources and Related Child Records
-
For AWS: Rule 1 - AWS Record Sets for Assets and Related Child Records
-
For GCP: Rule 1 - GCP Record Sets for Assets and Related Child Records
|
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
Record sets coming soon
|
Sample of available record sets
Record sets coming soon
|
Sample of available record sets
Record sets coming soon
|
|
|
|
Owned and costed |
Should the Cloud Resource have an accountable owner (because it incurs costs beyond immaterial spend). |
Sample of available record sets
Record sets coming soon
|
Sample of available record sets
Record sets coming soon
|
Sample of available record sets
Record sets coming soon
|
|
|
|
Application Dependency |
Does the Cloud Resource contribute to a Business Application (and therefore a Business Service). |
Sample of available record sets
Record sets coming soon
|
Sample of available record sets
Record sets coming soon
|
Sample of available record sets
Record sets coming soon
|
|
|
|
Audit-evidenced |
Should the Cloud Resource be registered to support a compliance requirement. |
Sample of available record sets
Record sets coming soon
|
Sample of available record sets
Record sets coming soon
|
Sample of available record sets
Record sets coming soon
|
|
|
|
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
Record sets coming soon
|
Sample of available record sets
Record sets coming soon
|
Sample of available record sets
Record sets coming soon
|
|
|
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:
-
Owned By - Who is accountable for the cloud resource?
-
Cost Centre - Which cost centre incurs the cost of the Cloud resource?
-
Environment - Does the cloud resource underpin production IT/business functions, or is it only used for development or testing purposes?
-
Application Dependency - Which business application (or applications) depend upon the cloud resource?
-
Service Dependency - Which business service (or services) depend upon the cloud resource (if this can’t be automatically determined via the business application)?
-
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.
-
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.
-
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.
-
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.
-
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.
Related Articles
Control Information
|
Created |
|
|---|---|
|
Reviewed |
|
|
Data Classification |
PUBLIC
|