Cloud Tenancy Status Reconciliation for Ghost Resource Detection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Cloud environments face the challenge of unaccounted or 'ghost' tenancies, where tenancies marked as terminated still have active cloud resources, leading to incorrect billing and security breaches due to unauthorized access.
Innovation Solution
A system that queries a tenancy status database and a cloud resource database using a multiple joins query to identify active cloud resources within terminated tenancies, tagging them as unaccounted and taking mitigating actions such as termination or status change.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If tenancies are marked as terminated to free up resources and simplify management, then resource allocation efficiency is improved, but security breaches and billing errors occur due to unaccounted active resources
Solution Approach 1:
The system implements a feedback mechanism by periodically querying both the cloud resource database and tenancy status database to verify whether terminated tenancies actually have active resources. This closed-loop verification process detects discrepancies between the expected state (terminated tenancy should have no active resources) and actual state, triggering appropriate corrective actions such as reactivation or termination of the tenancy record.
2Measurement precision
If comprehensive monitoring and verification of tenancy status is performed, then billing accuracy is improved, but system complexity increases due to multiple database queries and verification processes
Solution Approach 1:
The system performs preliminary actions by proactively querying and verifying tenancy status before billing cycles or security incidents occur. The periodic verification process is initiated in advance to identify and resolve unaccounted tenancies, preventing rather than reacting to billing errors and security breaches. This approach simplifies the overall system by preventing complex error handling scenarios.
3Object-affected harmful factors
If unaccounted tenancies are detected and terminated to maintain security, then security is improved, but loss of legitimate active resources occurs due to false positives
Solution Approach 1:
Instead of immediately terminating tenancies marked as terminated, the system inverts the conventional approach by first verifying whether active resources actually exist within those tenancies. Only after confirmation of unaccounted status does the system take termination or reactivation actions. This inverted verification-then-action approach prevents false positives by ensuring legitimate resources are protected before any corrective action is taken.
Data Source
AI summary
A method for detecting an unaccounted tenancy within a cloud environment is disclosed. The method includes storing, within a first database, (i) identifiers of a set of active cloud resources, and (ii) for each active cloud resource, an identifier of a corresponding tenancy; and storing, within a second database, (i) identifiers of a set of tenancies, and (ii) for each tenancy within the set of tenancies, a corresponding tenancy status. Within the second database, each of a first subset of the set of tenancies has an active status, and each of a second subset of the set of tenancies has a terminated status. The method includes querying the first and second databases to identify a first active cloud resource within a first tenancy, such that the first tenancy has a terminated tenancy status; tagging the first tenancy with an unaccounted tag; and undertaking mitigating actions for the unaccounted first tenancy.