Skip to content

Latest commit

 

History

History
53 lines (35 loc) · 2.19 KB

examples.md

File metadata and controls

53 lines (35 loc) · 2.19 KB

Example Images

GHOSTS API Server after boot

GHOSTS API

GHOSTS Grafana Dashboard after boot

GHOSTS API

On Win1 Client, monitoring the bootstrap powershell script logfile

GHOSTS API

Run the npc.sh script to sync a new NPC with registered GHOSTS machines

SSH into the GHOSTS Linux server and run the script: /home/ubuntu/npc.sh GHOSTS API

Run the remote npc.sh script to sync a new NPC with registered GHOSTS machines

Run the rendered script from the output directory. This script makes an API connection to the remote public IP address of GHOSTS server. GHOSTS API

On the DC, showing the Domain Join of Win1

GHOSTS API

On the DC, the ad_users.csv loads all Domain Users, OUs, and Groups. This shows the Engineering OU and one of the users who is added through ad_users.csv

You can edit and customize the ad_users.csv. It is uploaded to S3 bucket and then downloaded and processed through ad_install.ps1 script on the DC. GHOSTS API

Kibana Server: Showing the Symon logs

GHOSTS API

Kibana Server: Showing the Winlogbeat Overview dashboard that is automatically created

GHOSTS API

On Win1 Client, launching ghosts.exe manually

GHOSTS API

On Win1 Client, ghosts is starting

GHOSTS API

On Win1 Client, ghosts connects to the API server

It connects to the API server and streams its timeline logs as controlled by configuration GHOSTS API

A view of the GHOSTS API Server after the machine has registered

The NPC count has incremented by 1. The API change now synchronizes new NPCs with registered machines. GHOSTS API

GHOSTS Grafana dashboard after the machine has registered

The machine starts to send timeline data showing application usage. GHOSTS API