# US 12,603,890 B2 · Method for sensitive infrastructure protection > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,603,890 B2 - Document ID: US12603890B2 - Status: Granted - Kind: B2 - Application number: 18/539,881 - Filed: 2023-12-14 - Published: 2025-06-19 - Granted: 2026-04-14 - Earliest claimed: 2023-12-14 - Assignees: International Business Machines Corporation - Applicants: International Business Machines Corporation - Inventors: Arn Hyndman; Nicholas Sauriol - Web page: https://patentgrep.com/patent/US12603890B2 ## CPC - H04L 63/102: {Entity profiles} - G06F 8/71: Version control (security arrangements therefor G06F21/57); Configuration management - G06F 8/77: Software metrics - H04L 63/108: {when the policy decisions are valid for a limited amount of time} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract Managing access to computing environments is provided. A number of infrastructure as code (IAC) configurations are configured, wherein the IAC configurations are related to a same project. The IAC configurations are grouped into a number of environments, wherein the environments represent project stages or deployment situations, and wherein the environments have respective access privileges and allowed modifications for the respective IAC configurations within each environment. A number of user trusted profiles are automatically created that are linked to the access privileges and allowed modifications for the environments, wherein each trusted profile is specific to one of the environments. Modification are be deployed in an environment only after those modifications have been successfully deployed in a prerequisite environment. ## Claims ### Claim 1 A computer-implemented method of managing access to computing environments, the method comprising: using a number of processors to perform: configuring a number of infrastructure as code (IAC) configurations, wherein the IAC configurations are related to a same project; grouping the IAC configurations into a number of environments, wherein the environments represent project stages or deployment situations, and wherein the environments have respective access privileges and allowed modifications for the respective IAC configurations within each environment, and wherein the IAC configuration has no prerequisite environment, or the IAC configuration has been successfully deployed in a prerequisite environment; and automatically creating a number of user trusted profiles that are linked to the access privileges and allowed modifications for the environments, wherein each trusted profile is specific to one of the environments. ### Claim 2 (depends on 1) The method of claim 1, wherein a modification cannot be deployed in an environment unless that modification has been successfully deployed in a prerequisite environment. ### Claim 3 (depends on 1) The method of claim 1, further comprising searching all IAC configurations in a prerequisite environment for a match of a target IAC configuration version with a successful deployment. ### Claim 4 (depends on 1) The method of claim 1, wherein the project development stages comprise at least one of: development; testing; or production. ### Claim 5 (depends on 1) The method of claim 1, wherein the access privileges specify session time duration limits. ### Claim 6 (depends on 1) The method of claim 1, wherein the access privileges limit access to the specific environment to which access privileges and allowed modifications are linked. ### Claim 7 (depends on 1) The method of claim 1, wherein a deployment of the IAC configuration to a selected environment is denied unless a user has assumed a trusted profile corresponding to the selected environment prior to the deployment. ### Claim 8 A system for managing access to computing environments, the system comprising: a storage device that stores program instructions; one or more processors operably connected to the storage device and configured to execute the program instructions to cause the system to: configure a number of infrastructure as code (IAC) configurations, wherein the IAC configurations are related to a same project; group the IAC configurations into a number of environments, wherein the environments represent project stages or deployment situations, and wherein the environments have respective access privileges and allowed modifications for the respective IAC configurations within each environment, and wherein the IAC configuration has no prerequisite environment, or the IAC configuration has been successfully deployed in a prerequisite environment; and automatically create a number of user trusted profiles that are linked to the access privileges and allowed modifications for the environments, wherein each trusted profile is specific to one of the environments. ### Claim 9 (depends on 8) The system of claim 8, wherein a modification cannot be deployed in an environment unless that modification has been successfully deployed in a prerequisite environment. ### Claim 10 (depends on 8) The system of claim 8, wherein the program instructions further cause the system to search all IAC configurations in a prerequisite environment for a match of a target IAC configuration version with a successful deployment. ### Claim 11 (depends on 8) The system of claim 8, wherein the project development stages comprise at least one of: development; testing; or production. ### Claim 12 (depends on 8) The system of claim 8, wherein the access privileges specify session time duration limits. ### Claim 13 (depends on 8) The system of claim 8, wherein the access privileges limit access to the specific environment to which access privileges and allowed modifications are linked. ### Claim 14 (depends on 8) The system of claim 8, wherein a deployment of the IAC configuration to a selected environment is denied unless a user has assumed a trusted profile corresponding to the selected environment prior to the deployment. ### Claim 15 A computer program product for managing access to computing environments, the computer program product comprising: a computer readable storage medium having program instructions configured to cause one or more processors to: configure a number of infrastructure as code (IAC) configurations, wherein the IAC configurations are related to a same project; group the IAC configurations into a number of environments, wherein the environments represent project stages or deployment situations, and wherein the environments have respective access privileges and allowed modifications for the respective IAC configurations within each environment, and wherein the IAC configuration has no prerequisite environment, or the IAC configuration has been successfully deployed in a prerequisite environment; and automatically create a number of user trusted profiles that are linked to the access privileges and allowed modifications for the environments, wherein each trusted profile is specific to one of the environments. ### Claim 16 (depends on 15) The computer program product of claim 15, wherein a modification cannot be deployed in an environment unless that modification has been successfully deployed in a prerequisite environment. ### Claim 17 (depends on 15) The computer program product of claim 15, further comprising instructions for searching all IAC configurations in a prerequisite environment for a match of a target IAC configuration version with a successful deployment. ### Claim 18 (depends on 15) The computer program product of claim 15, wherein the access privileges specify session time duration limits. ### Claim 19 (depends on 15) The computer program product of claim 15, wherein the access privileges limit access to the specific environment to which access privileges and allowed modifications are linked. ### Claim 20 (depends on 15) The computer program product of claim 15, wherein a deployment of the IAC configuration to a selected environment is denied unless a user has assumed a trusted profile corresponding to the selected environment prior to the deployment.