Mamori uses proxy technology to monitor, record and inject security workflows into standard communication protocols. Enabling enhanced security and access management without the need to deploy agents or requiring updates to servers, databases or endpoints.
ssh proxy: protects ssh & sftp traffic
database proxies: protects database wire-protocol traffic
http/s proxies: protects application and API http/s traffic
The mamori server is the main component of a mamori deployment. It contains the ssh proxies, database proxies and all services required to configure and monitor your mamori server and infrastructure
method: docker container
location: on a server near the databases and servers to be secured.
download: click here to access dockerhub repo
|Mamori Services||In Container||Min Version||Description|
|Mamori Core||Yes||-||Configuration Portal (nginx 1.20, phoenix/elixir 1.7.2)|
|Proxies||Yes||-||SSH, MySQL, SS, Oracle, Mongo, Postgres and other JDBC. HTTP/S Proxy (separately installed)|
|Wireguard||Yes||1.1||Remote Access Firewall Tunnelling service. product link|
|InfluxDB||Yes||1.8||Activity Instrumentation Store. product link|
|Grafana||Yes||8.1||Custom Dashboarding service. product link|
Application proxies are required to enable on-the-wire role based security and data privacy (masking) controls on applications and APIs without changes to the application. They are not required for 2FA SAML integration.
location: on a server near the applications to be secured.
download |ENTER LINK|
A set of JS bindings for the mamori API that can use used to script common tasks and integrate with 3rd party solutions.
method: git project
location: install where required
repository click to access repo