Your Accounts Only

Your accounts only means YOUR personal free-tier or course sandbox under $CLOUD_LAB — document account IDs in notes before any console or CLI work.

Your Accounts Only• Audio Walkthrough

00:00/03:45

Visual · t31_your_accounts_only

Account scope literacy. $CLOUD_LAB only. Original Cyberlium.

The subscription ID is part of scope — Cyberlium refuses cloud work on tenants and accounts you do not own or lack written permission to assess.

Your cloud lab account is a personal AWS/Azure/GCP sandbox YOU created, a courseware tenant labeled for training, or a Cyberlium sample scope shipped for Topic 31. Intentional misconfig drills live in $CLOUD_LAB only — never copied from employer exports or stranger recon lists. Cyberlium maps allowed accounts on YOUR $CLOUD_LAB inventory — provider, account or subscription ID, owner — never 'borrowed' employer subscriptions or scraped victim tenant IDs. Next: No Stranger Tenants.

1. Allowed lab surfaces (named)

Personal AWS account with free-tier guardrails. Personal Azure subscription with spending caps. Courseware cloud lab pack with explicit training labels. Cyberlium t31-cloud sample policy snippets with fictional resource names.

On $CLOUD_LAB, list provider, account or subscription ID, and owner — fictional resource names OK if labeled sample.

Command guide

Try these commands — Allowed lab surfaces (named)

═══ DOCKER & CONTAINER AUDIT ═══

Check container running state and port bindings

Command — copy this

docker ps --format "table {{.ID}}	{{.Image}}	{{.Status}}	{{.Ports}}" 2>/dev/null || echo "docker ps"

Inspect container for elevated capabilities and root user

Command — copy this

docker inspect --format '{{json .HostConfig.Privileged}}' <container_id> 2>/dev/null || true

Run security vulnerability scan on container image using Trivy

Command — copy this

trivy image --severity HIGH,CRITICAL alpine:3.19 2>/dev/null || echo "trivy image alpine:3.19"

═══ KUBERNETES RBAC AUDIT ═══ Check current permissions in namespace

Command — copy this

kubectl auth can-i --list 2>/dev/null || echo "kubectl auth can-i"

Primary tools to practice this lesson: grep, curl. Reference sites: AWS security best practices (https://docs.aws.amazon.com/security/); Azure security baseline (https://learn.microsoft.com/en-us/security/benchmark/azure/); Shared responsibility (https://aws.amazon.com/compliance/shared-responsibility-model/). Run every command in the box — install first, then the usage lines — only on YOUR lab / program scope.

2. Why account scope matters before cloud work

AWS CLI, Azure CLI, and CSPM tools are powerful on any tenant — scope is what keeps practice legal and ethical. Employer production subscriptions, stranger accounts, and scraped breach keys are out of scope.

If you cannot answer 'who owns this account and who approved this assessment?', pause and fix scope notes before running cloud commands.

3. Account inventory habit

Forbidden: using a trending leaked key dump because it 'looks like training.' Allowed: account card — provider, ID, owner, allowed operations (read IAM policy in YOUR sandbox, review S3 block public access only).

Ship: account inventory row for one $CLOUD_LAB provider. Next: No Stranger Tenants.

4. What you ship: cloud account inventory row for $CLOUD_LAB

Provider, account ID, owner, allowed ops. $CLOUD_LAB named. NEVER stranger tenants. chmod 600.

5. What you record before the next lesson

Date. Account inventory row. $CLOUD_LAB named. File t31-m01-l02-your-accounts-only.txt chmod 600.

6. Wrong vs right: stranger tenants vs YOUR cloud accounts

Worked failure — same MSF word, opposite target. Right never needs a café Wi-Fi or classmate laptop.

Wrong: Import employer subscription because lab account is boring. Skip account card because 'it's just the CLI.'
Right: Write account inventory row for YOUR $CLOUD_LAB provider. Next: No Stranger Tenants.

Hands-on Exercise

Mission: document YOUR cloud lab account

1) Name one personal or course sandbox account. 2) Record provider and account or subscription ID. 3) List two allowed operations on that account. 4) chmod 600.

Pro Tip

Stuck? Ask Cyberlium AI Mentor

Personal free-tier sandboxes beat irreversible mistakes on employer production subscriptions.

Practice QuizQuestion 1

Multiple choice

APPLY: Your accounts only on Cyberlium means:

Practice QuizQuestion 2

True or False

APPLY: True or False: Reviewing IAM policies in an account YOU created is acceptable lab practice.

Practice QuizQuestion 3

Multiple choice

APPLY: Before running cloud CLI commands you should: