You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+33-7Lines changed: 33 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,14 +3,18 @@ Sentrius
3
3

4
4
5
5
Sentrius is zero trust (and if you want AI assisted) management system. to protect your infrastructure. It is split
6
-
into
7
-
two primary Maven. Currently we only support SSH, but RDP is in the works.
6
+
into several maven projects. Currently we only support SSH, but RDP is in the works. Agents can be leveraged to monitor and control SSH sessions, ensuring that all connections are secure and compliant with your organization's policies.
8
7
sub-projects:
9
8
10
9
core – Handles the core functionalities (e.g., SSH session management, RDP, zero trust policy enforcement).
11
10
api – Provides a RESTful API layer to interface with the core module.
12
-
java-agent -- java based agent to monitor and control the ssh sessions.
13
-
python-agent -- python based agent to monitor and control the ssh sessions.
11
+
dataplane -- offers dataplane functionality for secure data transfer and processing.
12
+
llm-proxy -- A proxy service that integrates with large language models (LLMs) to enhance security and compliance in SSH sessions.
13
+
llm-dataplane -- A data processing layer that leverages LLMs for advanced analysis and decision-making in SSH
14
+
sessions.
15
+
ops-scripts -- Contains operational scripts for deployment and management tasks.
16
+
ai-agent -- java based agent to monitor and control the ssh sessions.
17
+
python-agent -- python based agent to monitor and control the ssh sessions and act on behalf of user (TBD).
14
18
15
19
Internally, Sentrius may still be referenced by its former name, SSO (SecureShellOps), in certain scripts or configurations.
16
20
Table of Contents
@@ -74,7 +78,7 @@ sentrius/
74
78
75
79
Prerequisites
76
80
77
-
Java 11 or later
81
+
Java 17 or later
78
82
Apache Maven 3.6+
79
83
Database (PostgreSQL, MySQL, etc.) for storing session and configuration data
80
84
Keycloak for user authentication and authorization
@@ -90,10 +94,32 @@ cd sentrius
90
94
91
95
Running Sentrius
92
96
93
-
For convenience the ops/local directory contains a "run-sentrius.sh" script which will start the core and api modules. You can run this script from the project root:
97
+
Build the projects from root ( mvn clean install ) to ensure all dependencies are resolved and the modules are compiled.
98
+
99
+
For convenience the ops/local directory contains a "run-sentrius.sh" script which will start the core and api
100
+
modules. You can run this script from the project root.
101
+
This assumes you have a database available, keycloak running, and the necessary configurations. We now require an
102
+
OTEL endpoint, along with neo4j and kafka (but these are optional).:
94
103
95
104
./ops/local/run-sentrius.sh
96
105
106
+
It is simpler to run a kubernetes deployment, which is described in the Deployment. To do this, build as you would
107
+
above.
108
+
109
+
Build the images in your local Docker registry (note this builds all images, including core, api, and any other modules):
110
+
111
+
/build-images-local.sh --all --no-cache
112
+
113
+
Run the Helm deployment script to deploy Sentrius to your local Kubernetes cluster:
114
+
115
+
./ops-scripts/local/deploy-helm.sh
116
+
117
+
There is a GCP deployment that is hasn't been tested in some time. You can find it in the ops-scripts/gcp directory.
118
+
119
+
You will need to ensure you link to your GKE cluster and have the necessary permissions to deploy resources.
0 commit comments