ARANGO DB Con­fi­den­tial Container

ARANGO DB-SGX: ArangoDB Con­fi­den­tial Com­pute Container

enclaive deliv­ers a con­fi­den­tial com­pute vari­ant of Mran­goDB, called ARANGODB-SGX. This vari­ant runs in Intel SGX enclaves. Intel Secu­ri­ty Guard Exten­sion (SGX) deliv­ers advanced hard­ware and RAM secu­ri­ty encryp­tion fea­tures, so-called enclaves, to iso­late code and data that are spe­cif­ic to each appli­ca­tion. When data and appli­ca­tion code run in an enclave addi­tion­al secu­ri­ty, pri­va­cy, and trust guar­an­tees are giv­en, mak­ing the con­tain­er an ide­al choice for (untrust­ed) cloud environments.

Why ARANGODB-SGX images?

Fol­low­ing ben­e­fits come with ARANGODB-SGX :

  • con­fi­den­tial com­pute ready
  • con­tain­er escape pro­tec­tion through hard­ware-grad­ed security
  • con­tain­er images are released on a reg­u­lar basis with the lat­est dis­tri­b­u­tion pack­ages available
  • images use the same com­po­nents and con­fig­u­ra­tion approach — mak­ing it easy to switch between for­mats based on your project needs
  • com­pat­i­ble with DevOps best prac­tices (e.g., Dock­er, Dock­er Swarm, Kubernetes)

Fea­tures

  • con­tain­er-in-use encryp­tion and authentication
  • encrypt­ed and authen­ti­cat­ed volume/files
  • remote­ly authenticable
  • con­fi­den­tial key man­age­ment and provisioning

Pre­req­ui­sites

  • Dock­er Engine 20.1.0 or later
  • Dock­er com­pose plu­g­in is recommended
  • Intel SGXv2/x86 archi­tec­ture or later

C Con­fi­den­tial Container

C‑SGX: C Con­fi­den­tial Com­pute Container

enclaive deliv­ers a con­fi­den­tial com­pute vari­ant of C, called C‑SGX. This vari­ant runs in Intel SGX enclaves. Intel Secu­ri­ty Guard Exten­sion (SGX) deliv­ers advanced hard­ware and RAM secu­ri­ty encryp­tion fea­tures, so-called enclaves, to iso­late code and data that are spe­cif­ic to each appli­ca­tion. When data and appli­ca­tion code run in an enclave addi­tion­al secu­ri­ty, pri­va­cy, and trust guar­an­tees are giv­en, mak­ing the con­tain­er an ide­al choice for (untrust­ed) cloud environments.

Why C‑SGX images?

Fol­low­ing ben­e­fits come with C‑SGX :

  • con­fi­den­tial com­pute ready
  • con­tain­er escape pro­tec­tion through hard­ware-grad­ed security
  • con­tain­er images are released on a reg­u­lar basis with the lat­est dis­tri­b­u­tion pack­ages available
  • images use the same com­po­nents and con­fig­u­ra­tion approach — mak­ing it easy to switch between for­mats based on your project needs
  • com­pat­i­ble with DevOps best prac­tices (e.g., Dock­er, Dock­er Swarm, Kubernetes)

Fea­tures

  • con­tain­er-in-use encryp­tion and authentication
  • encrypt­ed and authen­ti­cat­ed volume/files
  • remote­ly authenticable
  • con­fi­den­tial key man­age­ment and provisioning

Pre­req­ui­sites

  • Dock­er Engine 20.1.0 or later
  • Dock­er com­pose plu­g­in is recommended
  • Intel SGXv2/x86 archi­tec­ture or later

 

C# Con­fi­den­tial Container

C#-SGX: C# Con­fi­den­tial Com­pute Container

enclaive deliv­ers a con­fi­den­tial com­pute vari­ant of C#, called CSHARP-SGX. This vari­ant runs in Intel SGX enclaves. Intel Secu­ri­ty Guard Exten­sion (SGX) deliv­ers advanced hard­ware and RAM secu­ri­ty encryp­tion fea­tures, so-called enclaves, to iso­late code and data that are spe­cif­ic to each appli­ca­tion. When data and appli­ca­tion code run in an enclave addi­tion­al secu­ri­ty, pri­va­cy, and trust guar­an­tees are giv­en, mak­ing the con­tain­er an ide­al choice for (untrust­ed) cloud environments.

Why C#-SGX images?

Fol­low­ing ben­e­fits come with C#-SGX :

  • con­fi­den­tial com­pute ready
  • con­tain­er escape pro­tec­tion through hard­ware-grad­ed security
  • con­tain­er images are released on a reg­u­lar basis with the lat­est dis­tri­b­u­tion pack­ages available
  • images use the same com­po­nents and con­fig­u­ra­tion approach — mak­ing it easy to switch between for­mats based on your project needs
  • com­pat­i­ble with DevOps best prac­tices (e.g., Dock­er, Dock­er Swarm, Kubernetes)

Fea­tures

  • con­tain­er-in-use encryp­tion and authentication
  • encrypt­ed and authen­ti­cat­ed volume/files
  • remote­ly authenticable
  • con­fi­den­tial key man­age­ment and provisioning

Pre­req­ui­sites

  • Dock­er Engine 20.1.0 or later
  • Dock­er com­pose plu­g­in is recommended
  • Intel SGXv2/x86 archi­tec­ture or later

 

C++ Con­fi­den­tial Container

C++-SGX: C++ Con­fi­den­tial Com­pute Container

enclaive deliv­ers a con­fi­den­tial com­pute vari­ant of C++, called C++-SGX. This vari­ant runs in Intel SGX enclaves. Intel Secu­ri­ty Guard Exten­sion (SGX) deliv­ers advanced hard­ware and RAM secu­ri­ty encryp­tion fea­tures, so-called enclaves, to iso­late code and data that are spe­cif­ic to each appli­ca­tion. When data and appli­ca­tion code run in an enclave addi­tion­al secu­ri­ty, pri­va­cy, and trust guar­an­tees are giv­en, mak­ing the con­tain­er an ide­al choice for (untrust­ed) cloud environments.

Why C++-SGX images?

Fol­low­ing ben­e­fits come with C++-SGX :

  • con­fi­den­tial com­pute ready
  • con­tain­er escape pro­tec­tion through hard­ware-grad­ed security
  • con­tain­er images are released on a reg­u­lar basis with the lat­est dis­tri­b­u­tion pack­ages available
  • images use the same com­po­nents and con­fig­u­ra­tion approach — mak­ing it easy to switch between for­mats based on your project needs
  • com­pat­i­ble with DevOps best prac­tices (e.g., Dock­er, Dock­er Swarm, Kubernetes)

Fea­tures

  • con­tain­er-in-use encryp­tion and authentication
  • encrypt­ed and authen­ti­cat­ed volume/files
  • remote­ly authenticable
  • con­fi­den­tial key man­age­ment and provisioning

Pre­req­ui­sites

  • Dock­er Engine 20.1.0 or later
  • Dock­er com­pose plu­g­in is recommended
  • Intel SGXv2/x86 archi­tec­ture or later

 

GO Con­fi­den­tial Container

GO-SGX: GO Con­fi­den­tial Com­pute Container

enclaive deliv­ers a con­fi­den­tial com­pute vari­ant of GO, called GO-SGX. This vari­ant runs in Intel SGX enclaves. Intel Secu­ri­ty Guard Exten­sion (SGX) deliv­ers advanced hard­ware and RAM secu­ri­ty encryp­tion fea­tures, so-called enclaves, to iso­late code and data that are spe­cif­ic to each appli­ca­tion. When data and appli­ca­tion code run in an enclave addi­tion­al secu­ri­ty, pri­va­cy, and trust guar­an­tees are giv­en, mak­ing the con­tain­er an ide­al choice for (untrust­ed) cloud environments.

Why GO-SGX images?

Fol­low­ing ben­e­fits come with GO-SGX :

  • con­fi­den­tial com­pute ready
  • con­tain­er escape pro­tec­tion through hard­ware-grad­ed security
  • con­tain­er images are released on a reg­u­lar basis with the lat­est dis­tri­b­u­tion pack­ages available
  • images use the same com­po­nents and con­fig­u­ra­tion approach — mak­ing it easy to switch between for­mats based on your project needs
  • com­pat­i­ble with DevOps best prac­tices (e.g., Dock­er, Dock­er Swarm, Kubernetes)

Fea­tures

  • con­tain­er-in-use encryp­tion and authentication
  • encrypt­ed and authen­ti­cat­ed volume/files
  • remote­ly authenticable
  • con­fi­den­tial key man­age­ment and provisioning

Pre­req­ui­sites

  • Dock­er Engine 20.1.0 or later
  • Dock­er com­pose plu­g­in is recommended
  • Intel SGXv2/x86 archi­tec­ture or later

 

Java Con­fi­den­tial Container

JAva-SGX: Java Con­fi­den­tial Com­pute Container

enclaive deliv­ers a con­fi­den­tial com­pute vari­ant of Java, called JAVA-SGX. This vari­ant runs in Intel SGX enclaves. Intel Secu­ri­ty Guard Exten­sion (SGX) deliv­ers advanced hard­ware and RAM secu­ri­ty encryp­tion fea­tures, so-called enclaves, to iso­late code and data that are spe­cif­ic to each appli­ca­tion. When data and appli­ca­tion code run in an enclave addi­tion­al secu­ri­ty, pri­va­cy, and trust guar­an­tees are giv­en, mak­ing the con­tain­er an ide­al choice for (untrust­ed) cloud environments.

Why Java-SGX images?

Fol­low­ing ben­e­fits come with Java-SGX :

  • con­fi­den­tial com­pute ready
  • con­tain­er escape pro­tec­tion through hard­ware-grad­ed security
  • con­tain­er images are released on a reg­u­lar basis with the lat­est dis­tri­b­u­tion pack­ages available
  • images use the same com­po­nents and con­fig­u­ra­tion approach — mak­ing it easy to switch between for­mats based on your project needs
  • com­pat­i­ble with DevOps best prac­tices (e.g., Dock­er, Dock­er Swarm, Kubernetes)

Fea­tures

  • con­tain­er-in-use encryp­tion and authentication
  • encrypt­ed and authen­ti­cat­ed volume/files
  • remote­ly authenticable
  • con­fi­den­tial key man­age­ment and provisioning

Pre­req­ui­sites

  • Dock­er Engine 20.1.0 or later
  • Dock­er com­pose plu­g­in is recommended
  • Intel SGXv2/x86 archi­tec­ture or later

 

MARIA DB Con­fi­den­tial Container

MARIA DB-SGX: Mari­aDB Con­fi­den­tial Com­pute Container

enclaive deliv­ers a con­fi­den­tial com­pute vari­ant of Mari­aDB, called MARIADB-SGX. This vari­ant runs in Intel SGX enclaves. Intel Secu­ri­ty Guard Exten­sion (SGX) deliv­ers advanced hard­ware and RAM secu­ri­ty encryp­tion fea­tures, so-called enclaves, to iso­late code and data that are spe­cif­ic to each appli­ca­tion. When data and appli­ca­tion code run in an enclave addi­tion­al secu­ri­ty, pri­va­cy, and trust guar­an­tees are giv­en, mak­ing the con­tain­er an ide­al choice for (untrust­ed) cloud environments.

Why MARIADB-SGX images?

Fol­low­ing ben­e­fits come with MARIADB-SGX :

  • con­fi­den­tial com­pute ready
  • con­tain­er escape pro­tec­tion through hard­ware-grad­ed security
  • con­tain­er images are released on a reg­u­lar basis with the lat­est dis­tri­b­u­tion pack­ages available
  • images use the same com­po­nents and con­fig­u­ra­tion approach — mak­ing it easy to switch between for­mats based on your project needs
  • com­pat­i­ble with DevOps best prac­tices (e.g., Dock­er, Dock­er Swarm, Kubernetes)

Fea­tures

  • con­tain­er-in-use encryp­tion and authentication
  • encrypt­ed and authen­ti­cat­ed volume/files
  • remote­ly authenticable
  • con­fi­den­tial key man­age­ment and provisioning

Pre­req­ui­sites

  • Dock­er Engine 20.1.0 or later
  • Dock­er com­pose plu­g­in is recommended
  • Intel SGXv2/x86 archi­tec­ture or later

MONGO DB Con­fi­den­tial Container

 

 DB-SGX: Mon­goDB Con­fi­den­tial Com­pute Container

enclaive deliv­ers a con­fi­den­tial com­pute vari­ant of Mon­goDB, called MONGO-SGX. This vari­ant runs in Intel SGX enclaves. Intel Secu­ri­ty Guard Exten­sion (SGX) deliv­ers advanced hard­ware and RAM secu­ri­ty encryp­tion fea­tures, so-called enclaves, to iso­late code and data that are spe­cif­ic to each appli­ca­tion. When data and appli­ca­tion code run in an enclave addi­tion­al secu­ri­ty, pri­va­cy, and trust guar­an­tees are giv­en, mak­ing the con­tain­er an ide­al choice for (untrust­ed) cloud environments.

Why MONGODB-SGX images?

Fol­low­ing ben­e­fits come with MONGODB-SGX :

  • con­fi­den­tial com­pute ready
  • con­tain­er escape pro­tec­tion through hard­ware-grad­ed security
  • con­tain­er images are released on a reg­u­lar basis with the lat­est dis­tri­b­u­tion pack­ages available
  • images use the same com­po­nents and con­fig­u­ra­tion approach — mak­ing it easy to switch between for­mats based on your project needs
  • com­pat­i­ble with DevOps best prac­tices (e.g., Dock­er, Dock­er Swarm, Kubernetes)

Fea­tures

  • con­tain­er-in-use encryp­tion and authentication
  • encrypt­ed and authen­ti­cat­ed volume/files
  • remote­ly authenticable
  • con­fi­den­tial key man­age­ment and provisioning

Pre­req­ui­sites

  • Dock­er Engine 20.1.0 or later
  • Dock­er com­pose plu­g­in is recommended
  • Intel SGXv2/x86 archi­tec­ture or later

MOSQUITTO Con­fi­den­tial Container

MOSQUITTO-SGX: MOSQUITTO MQTT Bro­ker Con­fi­den­tial Com­pute Container

enclaive deliv­ers a con­fi­den­tial com­pute vari­ant of Mos­qui­to, called MOSQUITO-SGX. This vari­ant runs in Intel SGX enclaves. Intel Secu­ri­ty Guard Exten­sion (SGX) deliv­ers advanced hard­ware and RAM secu­ri­ty encryp­tion fea­tures, so-called enclaves, to iso­late code and data that are spe­cif­ic to each appli­ca­tion. When data and appli­ca­tion code run in an enclave addi­tion­al secu­ri­ty, pri­va­cy, and trust guar­an­tees are giv­en, mak­ing the con­tain­er an ide­al choice for (untrust­ed) cloud environments.

Why Mosquiot-SGX images?

Fol­low­ing ben­e­fits come with NGINX-SGX :

  • con­fi­den­tial com­pute ready
  • con­tain­er escape pro­tec­tion through hard­ware-grad­ed security
  • con­tain­er images are released on a reg­u­lar basis with the lat­est dis­tri­b­u­tion pack­ages available
  • images use the same com­po­nents and con­fig­u­ra­tion approach — mak­ing it easy to switch between for­mats based on your project needs
  • com­pat­i­ble with DevOps best prac­tices (e.g., Dock­er, Dock­er Swarm, Kubernetes)

Fea­tures

  • con­tain­er-in-use encryp­tion and authentication
  • encrypt­ed and authen­ti­cat­ed volume/files
  • remote­ly authenticable
  • con­fi­den­tial key man­age­ment and provisioning

Pre­req­ui­sites

  • Dock­er Engine 20.1.0 or later
  • Dock­er com­pose plu­g­in is recommended
  • Intel SGXv2/x86 archi­tec­ture or later

 

NGINX Con­fi­den­tial Container

NGINX-SGX: NGINX Con­fi­den­tial Com­pute Container

enclaive deliv­ers a con­fi­den­tial com­pute vari­ant of NGINX, called NGINX-SGX. This vari­ant runs in Intel SGX enclaves. Intel Secu­ri­ty Guard Exten­sion (SGX) deliv­ers advanced hard­ware and RAM secu­ri­ty encryp­tion fea­tures, so-called enclaves, to iso­late code and data that are spe­cif­ic to each appli­ca­tion. When data and appli­ca­tion code run in an enclave addi­tion­al secu­ri­ty, pri­va­cy, and trust guar­an­tees are giv­en, mak­ing the con­tain­er an ide­al choice for (untrust­ed) cloud environments.

Why NGINX-SGX images?

Fol­low­ing ben­e­fits come with NGINX-SGX :

  • con­fi­den­tial com­pute ready
  • con­tain­er escape pro­tec­tion through hard­ware-grad­ed security
  • con­tain­er images are released on a reg­u­lar basis with the lat­est dis­tri­b­u­tion pack­ages available
  • images use the same com­po­nents and con­fig­u­ra­tion approach — mak­ing it easy to switch between for­mats based on your project needs
  • com­pat­i­ble with DevOps best prac­tices (e.g., Dock­er, Dock­er Swarm, Kubernetes)

Fea­tures

  • con­tain­er-in-use encryp­tion and authentication
  • encrypt­ed and authen­ti­cat­ed volume/files
  • remote­ly authenticable
  • con­fi­den­tial key man­age­ment and provisioning

Pre­req­ui­sites

  • Dock­er Engine 20.1.0 or later
  • Dock­er com­pose plu­g­in is recommended
  • Intel SGXv2/x86 archi­tec­ture or later

 

NODEJS Con­fi­den­tial Container

NODEJS-SGX: Node­JS Con­fi­den­tial Com­pute Container

enclaive deliv­ers a con­fi­den­tial com­pute vari­ant of Node­JS, called NODEJS-SGX. This vari­ant runs in Intel SGX enclaves. Intel Secu­ri­ty Guard Exten­sion (SGX) deliv­ers advanced hard­ware and RAM secu­ri­ty encryp­tion fea­tures, so-called enclaves, to iso­late code and data that are spe­cif­ic to each appli­ca­tion. When data and appli­ca­tion code run in an enclave addi­tion­al secu­ri­ty, pri­va­cy, and trust guar­an­tees are giv­en, mak­ing the con­tain­er an ide­al choice for (untrust­ed) cloud environments.

Why NODEJS-SGX images?

Fol­low­ing ben­e­fits come with NGINX-SGX :

  • con­fi­den­tial com­pute ready
  • con­tain­er escape pro­tec­tion through hard­ware-grad­ed security
  • con­tain­er images are released on a reg­u­lar basis with the lat­est dis­tri­b­u­tion pack­ages available
  • images use the same com­po­nents and con­fig­u­ra­tion approach — mak­ing it easy to switch between for­mats based on your project needs
  • com­pat­i­ble with DevOps best prac­tices (e.g., Dock­er, Dock­er Swarm, Kubernetes)

Fea­tures

  • con­tain­er-in-use encryp­tion and authentication
  • encrypt­ed and authen­ti­cat­ed volume/files
  • remote­ly authenticable
  • con­fi­den­tial key man­age­ment and provisioning

Pre­req­ui­sites

  • Dock­er Engine 20.1.0 or later
  • Dock­er com­pose plu­g­in is recommended
  • Intel SGXv2/x86 archi­tec­ture or later

 

PHP Con­fi­den­tial Container

PHP-SGX: PHP Con­fi­den­tial Com­pute Container

enclaive deliv­ers a con­fi­den­tial com­pute vari­ant of PHP, called PHP-SGX. This vari­ant runs in Intel SGX enclaves. Intel Secu­ri­ty Guard Exten­sion (SGX) deliv­ers advanced hard­ware and RAM secu­ri­ty encryp­tion fea­tures, so-called enclaves, to iso­late code and data that are spe­cif­ic to each appli­ca­tion. When data and appli­ca­tion code run in an enclave addi­tion­al secu­ri­ty, pri­va­cy, and trust guar­an­tees are giv­en, mak­ing the con­tain­er an ide­al choice for (untrust­ed) cloud environments.

Why PHP-SGX images?

Fol­low­ing ben­e­fits come with PHP-SGX :

  • con­fi­den­tial com­pute ready
  • con­tain­er escape pro­tec­tion through hard­ware-grad­ed security
  • con­tain­er images are released on a reg­u­lar basis with the lat­est dis­tri­b­u­tion pack­ages available
  • images use the same com­po­nents and con­fig­u­ra­tion approach — mak­ing it easy to switch between for­mats based on your project needs
  • com­pat­i­ble with DevOps best prac­tices (e.g., Dock­er, Dock­er Swarm, Kubernetes)

Fea­tures

  • con­tain­er-in-use encryp­tion and authentication
  • encrypt­ed and authen­ti­cat­ed volume/files
  • remote­ly authenticable
  • con­fi­den­tial key man­age­ment and provisioning

Pre­req­ui­sites

  • Dock­er Engine 20.1.0 or later
  • Dock­er com­pose plu­g­in is recommended
  • Intel SGXv2/x86 archi­tec­ture or later

 

Python Con­fi­den­tial Container

PYTHON-SGX: Python Con­fi­den­tial Com­pute Container

enclaive deliv­ers a con­fi­den­tial com­pute vari­ant of Python, called PYTHON-SGX. This vari­ant runs in Intel SGX enclaves. Intel Secu­ri­ty Guard Exten­sion (SGX) deliv­ers advanced hard­ware and RAM secu­ri­ty encryp­tion fea­tures, so-called enclaves, to iso­late code and data that are spe­cif­ic to each appli­ca­tion. When data and appli­ca­tion code run in an enclave addi­tion­al secu­ri­ty, pri­va­cy, and trust guar­an­tees are giv­en, mak­ing the con­tain­er an ide­al choice for (untrust­ed) cloud environments.

Why ‘Python-SGX images?

Fol­low­ing ben­e­fits come with NGINX-SGX :

  • con­fi­den­tial com­pute ready
  • con­tain­er escape pro­tec­tion through hard­ware-grad­ed security
  • con­tain­er images are released on a reg­u­lar basis with the lat­est dis­tri­b­u­tion pack­ages available
  • images use the same com­po­nents and con­fig­u­ra­tion approach — mak­ing it easy to switch between for­mats based on your project needs
  • com­pat­i­ble with DevOps best prac­tices (e.g., Dock­er, Dock­er Swarm, Kubernetes)

Fea­tures

  • con­tain­er-in-use encryp­tion and authentication
  • encrypt­ed and authen­ti­cat­ed volume/files
  • remote­ly authenticable
  • con­fi­den­tial key man­age­ment and provisioning

Pre­req­ui­sites

  • Dock­er Engine 20.1.0 or later
  • Dock­er com­pose plu­g­in is recommended
  • Intel SGXv2/x86 archi­tec­ture or later

 

Contact us

Cookie Consent with Real Cookie Banner