Back to glossary

CLI and PowerShell (Command-Line Cloud Changes)

Cloud command-line tools, such as the AWS CLI, the Azure CLI, Azure PowerShell and AWS Tools for PowerShell, let people and scripts create, change and delete cloud resources from a terminal, outside the web console and outside any infrastructure-as-code pipeline.

What are CLI and PowerShell cloud changes?

Command-Line Interface (CLI) and PowerShell cloud changes refer to the provisioning, configuration and management of cloud resources through command-line tools rather than graphical management consoles or declarative Infrastructure as Code (IaC).

Major cloud providers offer native command-line tools, including:

  • AWS CLI and AWS Tools for PowerShell
  • Azure CLI and Azure PowerShell
  • Google Cloud CLI (gcloud)
  • Oracle Cloud Infrastructure (OCI) CLI

‍

These tools interact with cloud provider APIs and can be used independently or as part of scripts, automation workflows and CI/CD pipelines.

Why organizations use CLI and PowerShell

Command-line tools are widely adopted by cloud engineers, developers, security teams and system administrators for activities such as:

  • Cloud resource provisioning and configuration
  • Administrative task automation
  • Emergency fixes and incident response
  • Infrastructure troubleshooting
  • Bulk resource management
  • Security and compliance operations

‍

These tools provide operational flexibility and are an essential component of modern cloud management.

Security risks associated with command-line cloud changes

When executed outside established deployment workflows, command-line changes can bypass version control, peer reviews, IaC scanning and approval processes.

This can introduce several security and governance challenges:

  • Cloud misconfigurations
  • Configuration and policy drift
  • Excessive identity permissions
  • Unauthorized resource exposures
  • Inconsistent security policy coverage
  • Gaps in change management

‍

Although these operations can be recorded in cloud-native audit logs, they may not be reflected in existing infrastructure definitions.

Command-line changes and source-agnostic risk

CLI and PowerShell represent additional paths through which cloud misconfigurations can be introduced, alongside ClickOps, IaC, direct API requests, automation scripts and AI agents.

Preventive cloud security addresses source-agnostic risk by enforcing security intent at the point of deployment, regardless of where a supported cloud operation originates, without modifying existing production resources. This enables organizations to maintain consistent security boundaries without requiring engineering teams to abandon their preferred tools or workflows.

Why it matters

Command-line tools are fundamental to modern cloud operations. Restricting their use is not necessarily a practical or scalable security strategy.

Instead, organizations should ensure that the same security requirements apply whether a resource is deployed through a Terraform configuration, a PowerShell script, a CLI command or a cloud management console.

Ready to take your first proactive step?