Skip to content
Cloud Security DeskSearch
Menu

Evidence search

Search

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

Results for “NIST”

129 publications
Technical guideSource-based analysis

Make secret rotation reach every running application

Secret managers, mounted files, application memory and connection pools can disagree about the active credential. Test each stage before calling rotation complete.

Workload security · Kubernetes / AWS / Azure / Google Cloud · By Cloud Security Desk
Research noteSource-based analysis

What coding benchmarks can prove about a model

A coding benchmark result depends on its tasks, harness and tests. A reproducible count of SWE-bench Verified shows why the denominator belongs beside every comparison.

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

Rotate Entra application certificates with proof of adoption

A renewed certificate can exist in Key Vault while a running client still uses the old key. Define the evidence that makes application rotation complete.

Identity & access · Microsoft Entra / Azure Key Vault · By Cloud Security Desk
Technical guideSource-based analysis

Testing Sigma detections before a backend change

Keep rule structure, field transformations, query conversion and event matching as separate checks when changing a Sigma detection backend.

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

Design an outbound fetch service that contains SSRF

A URL check is only the first decision. The fetch worker must contact the approved destination, recheck redirects and limit the authority of every request.

Workload security · OWASP / IANA · By Cloud Security Desk
Technical guideSource-based analysis

Where fine tuning data needs a trust boundary

A training dataset can preserve its checksum and still teach the wrong behavior. Admission controls need to separate origin, transformation, approved use and the model change they produce.

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

Error budgets for controlled service degradation

Protect essential work under load while counting rejected and degraded requests against the service promise that users were actually given.

Resilience · Google / Envoy · By Cloud Security Desk
Technical guideSource-based analysis

Short SSH certificates still need explicit access boundaries

An SSH certificate supplies bounded identity claims. The issuer, server, client and incident operator still make separate access decisions.

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

Cloud incident severity needs a service impact model

Connect incident priority to service consequences, scope and time criticality while preserving evidence confidence and the authority to revise the decision.

Detection & response · NIST / FIRST · By Cloud Security Desk
Technical guideSource-based analysis

A budget model for bounded AI inference

Request throttles, token quotas and billing alerts control different things. An inference service needs an admission decision that reserves bounded work and reconciles what actually ran.

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

Certificate renewal under shorter validity limits

Use the public TLS issuance schedule to review authorization, renewal, deployment and independent verification of the certificate an endpoint actually serves.

Resilience · CA/Browser Forum / Let's Encrypt / AWS · By Cloud Security Desk
Technical guideSource-based analysis

Measure SCIM offboarding at the application

A successful provisioning update proves a directory action, not the end of every application session. Define and test the application's offboarding contract.

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

Prepare cloud workloads for hybrid post-quantum TLS

Hybrid support in a library is not proof that every TLS hop uses it. Verify negotiation, compatibility and fallback while keeping certificate authentication separate.

Workload security · IETF / NIST / OpenSSL / Cloudflare · By Cloud Security Desk
Technical guideSource-based analysis

An evidence plan for AI incident response

An AI incident record needs to connect the system version, context, output, downstream action and observed consequence. A saved prompt or a public report is only part of that evidence.

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

Cloud detection coverage after the ATT&CK data model change

Connect current ATT&CK strategies and analytics to available events, implemented rules and test evidence, while keeping taxonomy counts separate from protection.

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

Keep database changes compatible with application rollback

Preserve an explicit relationship between old code and migrated state through additive changes, safe backfills, and a defined rollback window.

Resilience · Kubernetes / GitLab · By Cloud Security Desk
Technical guideSource-based analysis

Map every connection beyond the private AI endpoint

Trace inference, retrieval, tools, administration, and telemetry separately before describing an AI application as private.

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

Build an Azure change record that survives the portal window

Activity Log records and resource logs answer different questions. Preserve the operation outcome, resource context and export scope needed for a later investigation.

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

Trace Google service account impersonation across every hop

A short-lived token can carry a broad identity. Review who can mint it, which account it represents and whether the original caller remains visible.

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

Keep encryption keys recoverable with the data they protect

Trace each encrypted recovery point to its required key, usable lifecycle state, and restore permissions before retiring cryptographic dependencies.

Resilience · AWS / Azure · By Cloud Security Desk
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
Research noteSource-based analysis

Find the Google audit logs missing from your evidence window

Audit category, inherited configuration, destination and reader permissions all affect what an investigator can retrieve. Retention is only one part of the record.

Detection & response · Google Cloud · 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

Make regional failover work without new infrastructure

Prepare capacity, dependencies, and the routing control path before an incident, then measure when clients reach an accepted recovery service.

Resilience · AWS · By Cloud Security Desk