> For the complete documentation index, see [llms.txt](https://docs.enclaive.cloud/nitride/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enclaive.cloud/nitride/documentation/getting-started/remote-attestation.md). # Remote attestation Learn how to make a "remote" attestation workflow using the CLI commands. Remote attestation is the security process that allows the attester (or the "prover"), such as a VM or container to prove to another party (or the "verifier") it is running trusted software in a secure enclaved environment. This process is crucial in cloud, edge and AI confidential computing scenarios, where workloads need to prove their integrity and identity before being granted access to sensitive resources or secrets.


Step 1: Setup	Setup	green_settings_icon_16x9.png
Step 2: Generate a Nonce	Generate a Nonce	green_nonce_icon_16x9.png
Step 3: Generate a Report	Generate a Report	green_attestation_icon_16x9.png
Step 4: Verify the Report	Verify the report	green_verify_icon_16x9.png

Remote attestation typically involves four steps: * The verifier creates a policy defining when an attestation report is valid. * The verifier issues a [challenge](/nitride/documentation/getting-started/remote-attestation/generate-a-nonce.md), often a nonce to the attester. * The attester generates a cryptographically signed [report](/nitride/documentation/getting-started/remote-attestation/generate-a-report.md), including the nonce and measurements of its environment. * Implementing the security policy, the verifier [validates](/nitride/documentation/getting-started/remote-attestation/verify-the-report.md) the report to ensure the attester is genuine and uncompromised.