0.3.0c
123
README.md
@@ -13,9 +13,8 @@
|
||||
<p><strong>Zero Trust Privileged Access Management</strong></p>
|
||||
<p>🔐 Zero Trust | 🎥 Session Recording | 🌐 Multi-Protocol | 🔒 ABAC Security | 🎨 Beautiful UI</p>
|
||||
<p>
|
||||
<img src="https://img.shields.io/badge/version-0.2.0c-blue.svg" alt="Version 0.2.0c">
|
||||
<img src="https://img.shields.io/badge/version-0.3.0c-blue.svg" alt="Version 0.2.0c">
|
||||
<img src="https://img.shields.io/badge/platform-linux%20%7C%20macos-brightgreen.svg" alt="Platform Support">
|
||||
<img src="https://img.shields.io/badge/license-GPLv3-green.svg" alt="License">
|
||||
</p>
|
||||
</div>
|
||||
|
||||
@@ -23,6 +22,12 @@ CyberPAM is a comprehensive Zero Trust Privileged Access Management solution des
|
||||
|
||||
I made CyberPAM for my own use, but I'm happy to share it with the community. I've been working with PAM products for years and CyberPAM is the culmination of my experience. Session recording is a must have for any PAM product, and CyberPAM is the best I've seen from an Admin perspective, and user experience. Often implementations of PAM products take a long time to get to production, but not CyberPAM.
|
||||
|
||||
<p align="center">
|
||||
<a href="ZEROTRUST.md"><b> ⚡️ v0.3.0c Setup Zero Trust Network Access for CyberPAM Targets/Hosts ⚡️</b></a>
|
||||
</p>
|
||||
|
||||

|
||||
|
||||

|
||||
|
||||
What is PAM? <a href="https://en.wikipedia.org/wiki/Privileged_access_management">PAM</a> is the process of managing access to resources. It is a critical component of any security architecture.
|
||||
@@ -30,6 +35,49 @@ What is PAM? <a href="https://en.wikipedia.org/wiki/Privileged_access_management
|
||||
<p align="center"> <b>⚡️ This is a SINGLE CONTAINER (Docker or Kubernetes) and can go from pull to production in 5 minutes and is PERFECT for a SaaS Product 🚀</b> </p>
|
||||
|
||||
|
||||
## 🚀 Quick Start
|
||||
|
||||
CyberPAM is distributed as a Docker container for easy deployment and a 5 minute setup:
|
||||
|
||||
### Docker
|
||||
*You can just copy paste this into your terminal 🖥️ to deploy or upgrade*
|
||||
```bash
|
||||
# Pull the latest image
|
||||
docker pull mattrogers/cyberpam:latest
|
||||
|
||||
docker stop cyberpam
|
||||
docker rm cyberpam
|
||||
|
||||
# Run with basic configuration
|
||||
docker run -d \
|
||||
--name cyberpam \
|
||||
-v cyberpamdb:/data \
|
||||
-v cyberpamrecordings:/recordings \
|
||||
-p 8080:8080 \
|
||||
mattrogers/cyberpam:latest
|
||||
|
||||
docker logs cyberpam
|
||||
```
|
||||
|
||||
### Kubernetes
|
||||
|
||||
```bash
|
||||
kubectl apply -f kubernetes/deployment-cyberpam.yaml
|
||||
```
|
||||
|
||||
## ⚡️NOTICE - GET YOUR ADMIN PASSWORD👋
|
||||
|
||||
Access the web interface at `http://localhost:8080` after starting the container. The initial admin credentials will be displayed in the container logs:
|
||||
|
||||
```bash
|
||||
# View initial admin credentials
|
||||
docker logs cyberpam
|
||||
```
|
||||
|
||||

|
||||
|
||||
|
||||
|
||||
## 🌟 Features
|
||||
|
||||
<table style="width:100%; border-collapse: collapse;">
|
||||
@@ -105,69 +153,6 @@ What is PAM? <a href="https://en.wikipedia.org/wiki/Privileged_access_management
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
## 🚀 Quick Start
|
||||
|
||||
CyberPAM is distributed as a Docker container for easy deployment and a 5 minute setup:
|
||||
|
||||
### Docker
|
||||
*You can just copy paste this into your terminal 🖥️ to deploy or upgrade*
|
||||
```bash
|
||||
# Pull the latest image
|
||||
docker pull mattrogers/cyberpam:latest
|
||||
|
||||
docker stop cyberpam
|
||||
docker rm cyberpam
|
||||
|
||||
# Run with basic configuration
|
||||
docker run -d \
|
||||
--name cyberpam \
|
||||
-v cyberpamdb:/data \
|
||||
-v cyberpamrecordings:/recordings \
|
||||
-p 8080:8080 \
|
||||
mattrogers/cyberpam:latest
|
||||
|
||||
docker logs cyberpam
|
||||
```
|
||||
|
||||
### Kubernetes
|
||||
|
||||
```bash
|
||||
kubectl apply -f kubernetes/deployment-cyberpam.yaml
|
||||
```
|
||||
|
||||
> *As of 0.1.1c, the container was designed to user docker volumes for persistence. You could also use a bind mount to the same effect.*
|
||||
|
||||
## ⚡️NOTICE - GET YOUR ADMIN PASSWORD👋
|
||||
|
||||
Access the web interface at `http://localhost:8080` after starting the container. The initial admin credentials will be displayed in the container logs:
|
||||
|
||||
```bash
|
||||
# View initial admin credentials
|
||||
docker logs cyberpam
|
||||
```
|
||||
|
||||

|
||||
|
||||
|
||||
### 📂 External Recordings Storage
|
||||
|
||||
```
|
||||
# Run with external recordings storage
|
||||
docker run -d \
|
||||
--name cyberpam \
|
||||
-p 8080:8080 \
|
||||
-v /your/local/path:/recordings \
|
||||
mattrogers/cyberpam:latest
|
||||
```
|
||||
|
||||
The `/recordings` volume binding is optional but recommended for:
|
||||
- Persistent storage of session recordings outside the container
|
||||
- Easy access to recording files for backup
|
||||
- Sharing recordings between container recreations
|
||||
- Integration with external video processing tools
|
||||
|
||||
|
||||
|
||||
## 🔧️ Security Notice
|
||||
|
||||
CyberPAM is designed to be deployed behind a reverse proxy that handles SSL/TLS termination and additional security controls. We recommend:
|
||||
@@ -182,9 +167,9 @@ cyberpam.yourdomain.com {
|
||||
}
|
||||
```
|
||||
|
||||
### Zero Trust Network Access
|
||||
### Zero Trust Network Access INTO CyberPAM
|
||||
|
||||
It's easy to setup a tunnel with Cloudflare Zero Trust.
|
||||
It's easy to setup a tunnel with Cloudflare Zero Trust into CyberPAM.
|
||||
|
||||
<table style="width:100%; border-collapse: collapse;">
|
||||
<tr>
|
||||
@@ -290,6 +275,10 @@ Internet -> Cloudflare Zero Trust -> Reverse Proxy (TLS/Cloudflared) -> CyberPAM
|
||||
</table>
|
||||
</div>
|
||||
|
||||
## Version CyberPam 0.3.0c
|
||||
- ***Added Zero Trust Network Access from Cloudflare Support***
|
||||
- Added ZTNA Agent https://github.com/RamboRogers/cyberpamagent
|
||||
- GUI Refactoring and improvements
|
||||
|
||||
## Version CyberPam 0.2.0c
|
||||
- Added Zero Trust Network Access from Cloudflare Support
|
||||
|
||||
115
ZEROTRUST.md
Normal file
@@ -0,0 +1,115 @@
|
||||
# CyberPAMZero Trust Network Access
|
||||
|
||||
TLDR: No more VPNs, just use Cloudflare Access to access your CyberPAM instance. Hosts no longer need to be in the same network, or have <b>any open ports.</b>
|
||||
|
||||
> Yes, CyberPAM and the host do NOT need to be in the same network.
|
||||
|
||||

|
||||
|
||||
|
||||
## Setup Requirements
|
||||
|
||||
- Assumes you have a CyberPAM instance running already.
|
||||
- Assumes you have a Cloudflare account and a domain. (free tier is fine)
|
||||
|
||||
## Settings Panel Fully Configured
|
||||
|
||||
When you having it it all setup, you should see something like this, notice the green globes. This setup takes less than 15 minutes to complete.
|
||||
|
||||
> 💣 Notice red panel, once you set your domain, if you change it you will need to re-register the agents.
|
||||
|
||||

|
||||
|
||||
|
||||
|
||||
## Cloudflare ZTNA
|
||||
|
||||
|
||||
|
||||
>*The ZTNA module here works amazing well, however the setup isn't foolproof. Fill in the values and press save, then enable and the engine will start.*
|
||||
|
||||
|
||||
### Add Catchall Policy
|
||||
|
||||
You need this policy to secure your hosts, and allow access to your CyberPAM instance.
|
||||
|
||||

|
||||

|
||||

|
||||

|
||||

|
||||
|
||||
### Get your Service Token
|
||||
|
||||
You'll need to strip off the CF-Header and CF-Key from the token, and then paste it into the CyberPAM settings panel.
|
||||
|
||||

|
||||
|
||||
### Setup API Access
|
||||
Take note of the API key, account id, and email, you'll need to paste them into the CyberPAM settings panel. Your permissions should match these here.
|
||||
|
||||

|
||||
|
||||
You'll know its working when you see the green globe and your domains populate.
|
||||
|
||||
> If you don't see the green globes or the domains don't populate, you'll need to check your API key, account id, and email.
|
||||
|
||||

|
||||
|
||||

|
||||
|
||||
|
||||
## Add Hosts
|
||||
|
||||
Lets add a host to our CyberPAM instance.
|
||||
|
||||

|
||||
|
||||

|
||||
|
||||
Run the CyberPAM agent on the host, and provide this token. Within a few minutes you should see the host will be added to the list and the tunnel will show it's health under "expanded" view.
|
||||
|
||||
https://github.com/RamboRogers/cyberpamagent
|
||||
|
||||
### 🐧 Linux & 🍎 macOS
|
||||
|
||||
```bash
|
||||
curl -L https://raw.githubusercontent.com/RamboRogers/cyberpamagent/main/install.sh | sh
|
||||
```
|
||||
|
||||
### 🪟 Windows PowerShell
|
||||
> *Admin Powershell*
|
||||
```powershell
|
||||
iwr -useb https://raw.githubusercontent.com/RamboRogers/cyberpamagent/main/install.ps1 | iex
|
||||
```
|
||||
|
||||

|
||||
|
||||
That's it, the agent will install and run as a service. You can uninstall it with `cyberpamagent -uninstall`.
|
||||
|
||||
## Lots of Hosts
|
||||
|
||||
A example instance with some hosts added.
|
||||
|
||||

|
||||
|
||||
|
||||
<div align="center">
|
||||
|
||||
## ⚖️ License
|
||||
|
||||
<p>
|
||||
CyberPAM is licensed under a restricted license.<p><i> (c)Matthew Rogers 2024. All rights reserved. No Warranty. No Support. No Liability. No Refunds.</p<br>
|
||||
</i><p>
|
||||
<em>Free Demo Software</em>
|
||||
</p>
|
||||
|
||||
### Connect With Me 🤝
|
||||
|
||||
[](https://github.com/matthewrogers)
|
||||
[](https://x.com/rogerscissp)
|
||||
[](https://matthewrogers.org)
|
||||
|
||||

|
||||
|
||||
</div>
|
||||
BIN
media/drawing.png
Normal file
|
After Width: | Height: | Size: 235 KiB |
BIN
media/home.png
Normal file
|
After Width: | Height: | Size: 2.2 MiB |
BIN
media/systoken.png
Normal file
|
After Width: | Height: | Size: 217 KiB |
BIN
media/zt-catchall.png
Normal file
|
After Width: | Height: | Size: 81 KiB |
BIN
media/ztadd.png
Normal file
|
After Width: | Height: | Size: 299 KiB |
BIN
media/ztaddapp.png
Normal file
|
After Width: | Height: | Size: 333 KiB |
BIN
media/ztapi.png
Normal file
|
After Width: | Height: | Size: 909 KiB |
BIN
media/ztdomain.png
Normal file
|
After Width: | Height: | Size: 48 KiB |
BIN
media/ztinstall.png
Normal file
|
After Width: | Height: | Size: 264 KiB |
BIN
media/ztlist.png
Normal file
|
After Width: | Height: | Size: 87 KiB |
BIN
media/ztself.png
Normal file
|
After Width: | Height: | Size: 356 KiB |
BIN
media/ztservice.png
Normal file
|
After Width: | Height: | Size: 168 KiB |
BIN
media/ztsettings.png
Normal file
|
After Width: | Height: | Size: 712 KiB |
BIN
media/zttoken.png
Normal file
|
After Width: | Height: | Size: 309 KiB |
BIN
media/ztverifyapi.png
Normal file
|
After Width: | Height: | Size: 94 KiB |