Skip to content
Cloud Security DeskSearch
Menu

Evidence search

Search

Search titles, summaries, topics, providers, authors, and the full open-access corpus.

Results for “RPO”

36 publications
Technical guideSource-based analysis

Put enforceable boundaries around agent tool calls

Treat model proposals as requests for authority, then check the operation, resource, recipient, and approval at the point where a tool can create a side effect.

AI systems · AWS · By Cloud Security Desk
Technical guideSource-based analysis

Verify container provenance before admitting a pinned image

Use the digest to identify the artifact, then check who signed it, which builder produced it, and which evidence survived promotion into the deployment registry.

Workload security · Kubernetes / Docker / Sigstore · By Cloud Security Desk
Technical guideSource-based analysis

Review the authority behind every Entra app consent

The permission name is only part of the decision. Review the access mode, resource scope, consenting authority and people who can change the application.

Identity & access · Microsoft Entra · By Cloud Security Desk
Technical guideSource-based analysis

Treat model downloads as software supply chain changes

Review weights, custom code, dependencies, and runtime authority as separate decisions before promoting a downloaded model into a trusted environment.

AI systems · Hugging Face · By Cloud Security Desk
Technical guideSource-based analysis

Require EC2 IMDSv2 without breaking container credentials

Separate metadata token requirements from response hop limits, then verify both existing instances and future launches before declaring the migration complete.

Workload security · AWS · By Cloud Security Desk
Technical guideSource-based analysis

Measure recovery by the service you can restore

Define application acceptance, recoverable data, and a complete timeline before treating a completed restore job as proof of recovery.

Resilience · AWS / PostgreSQL · By Cloud Security Desk
Technical guideSource-based analysis

Verify the CloudTrail files behind an incident timeline

Digest delivery and successful validation are different evidence states. Preserve the files, metadata and validation result needed to distinguish them.

Detection & response · AWS · By Cloud Security Desk
Technical guideSource-based analysis

Close the AWS sessions that survive identity shutdown

Removing a login does not by itself establish that issued AWS credentials have lost their authority. Build a revocation procedure that accounts for both.

Identity & access · AWS · By Cloud Security Desk
Technical guideSource-based analysis

Roll out Kubernetes Pod Security Admission without surprises

Stage namespace enforcement around the Pods a controller will create next, with explicit policy versions, runtime checks, and narrowly owned exceptions.

Workload security · Kubernetes · By Cloud Security Desk
Technical guideSource-based analysis

Choose the S3 object events your investigation will need

CloudTrail event history is not an object-access ledger. Build selectors around the questions an investigation must answer, then test the exclusions.

Detection & response · AWS · By Cloud Security Desk
Visual briefIllustrative analysis

Cloud logs that never reach the SIEM

A dashboard can be healthy while the evidence behind it is incomplete. Coverage needs to be tested from event creation to searchable record.

Detection & response · AWS / Azure / Google Cloud · By Umair Akbar and Ahmed Elshekh
Research noteIllustrative analysis

Threat-model the system around the model

The model endpoint is one component. The consequential paths often run through retrieval stores, orchestration identities, evaluation data, and operator tools.

AI systems · AWS / Azure / Google Cloud · By Umair Akbar and Ahmed Elshekh