Enclaive WordPress – Confidential Compute Enterprise Enclave 4 SGX Protects User Data and enables cookieless eCommerce sites WordPress (WP, WordPress.org) is a free and open-source content management system (CMS) written in PHP[4] and paired with a MySQL or MariaDB database. Features include a plugin architecture and a template system, referred to within WordPress as Themes. WordPress was originally created as a blog-publishing system but has evolved to support other web content types including more traditional mailing lists and forums, media galleries, membership sites, learning management systems (LMS) and online stores. One of the most popular content management system solutions in use, WordPress is used by 42.8% of the top 10 million websites as of October 2021. Intel Security Guard Extension (SGX) delivers advanced hardware and RAM security encryption features, so called enclaves, in order to isolate code and data that are specific to each application. When data and application code run in an enclave additional security, privacy and trust guarantees are given, making the container an ideal choice for (untrusted) cloud environments. Overview of Intel SGX Application code executing within an Intel SGX enclave: Remains protected even when the BIOS, VMM, OS, and drivers are compromised, implying that an attacker with full execution control over the platform can be kept at bay Benefits from memory protections that thwart memory bus snooping, memory tampering and “cold boot” attacks on images retained in RAM At no moment in time data, program code and protocol messages are leaked or de-anonymized Reduces the trusted computing base of its parent application to the smallest possible footprint Why use WORDPRESS-SGX (instead of "vanilla" Wordpress) images? Following benefits come for free with WORDPRESS-SGX : WORDPRESS-SGX provides a significantly reduced attack surface thanks to hardware-based memory protection. At any moment in time, the microservices in the confindential containers processing the data, storing data in the SQL database and forwarding the data to other microservices are protected. Neither enclaive nor the hosting provider can inspect the data. Hardened security against kernel-space exploits, malicious and accidental privilege insider attacks, UEFI firmware exploits and other "root" attacks using the corruption of the application to infiltrate your network and system Run on any hosting environment irrespectivably of geo-location and comply with privacy export regulation, such as Schrems-II GDPR/CCPA compliant processing ("data in use") of user data in the cloud as data is anonymized thanks to the enclave Last, but not least "Small step for a dev, giant leap for a zero-trust infrastructure" *Any registered trademarks and rights therein are reserved to the respective owner. Any use by enclaive is for referential purposes only and does not indicate any sponsorship, endorsement or affiliation between the trademark owner and enclaive.