> For the complete documentation index, see [llms.txt](https://docs.reveald.com/technical-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reveald.com/technical-documentation/admin-guides/epiphany-validation-engine-users-guide/chapter-1-architecture-of-eve.md).

# Chapter 1: Architecture of EVE

At the network architecture level, the EVE Platform is installed on AWS in the cloud and given access to an EndPoint within the organization behind security controls (Golden image).

EVE emulates real scenarios and cyber-attacks targeting an organization from the cloud console/instance.

This is the flow that artifacts follow once sent in a corporate environment:

<figure><img src="/files/SPPYAriO9rviqPfL3IbI" alt=""><figcaption></figcaption></figure>

The E.V.E. artifacts, samples and scripts are contained in emulation packages that are sent over the network and executed on the virtual machine (Endpoint) with the customer's golden image. The E.V.E. Agent applies control mechanisms and sends the response to the Orchestrator with the obtained results