• We just launched and are currently in beta. Join us as we build and grow the community.

hierarchical http logger explaination **draft**

DIMASIK1502

Network Manager
D Rep
0
0
0
Rep
0
D Vouches
0
0
0
Vouches
0
Posts
141
Likes
36
Bits
2 MONTHS
2 2 MONTHS OF SERVICE
LEVEL 1 300 XP
Loggers when staged onto a computer.
Have one goal, which is to test for as much data as possible, gather the data found
and call-back to your endpoint. Here's a modern day example of how this is done.
## Endpoints
A Endpoint is a service on the public internet
Strickly made for storing data sent to it. Examples
Of a endpoint can be things like, Virtualized Ftp Server's or,
Discord Webhook's
Its very important as a Threat Actor to embed Well writen
Filtering on these endpoints to only let certain requests
through. You can do this by adding tokens or creating a
storage algorithm.
- **Example Scenario:**
- You have an HTTP Webhook that requires a **connection token** for validation.
- To control access, store the token and only allow requests containing the correct token.
- For Data to be seen as storable mac address must be set in place
- **Example Implementation:**
- **Define Token:**
Store your connection token securely in the HTTP backend
Avoid putting your token in place text try to encode it:
`Token = "HelloWorld"`
- **Structure Data:**
Create a data object with the token and other necessary information.
For this example the only two Needed information is the macaddr & token
Value. Then the data is stored accordingly in the Server.
```
data = {
"token": "HelloWorld",
"macaddr": "11:22:33:44:55:66",
"device_info": {
"hostname": "Device-002",
"os": "Ubuntu 20.04"
},
"data": [
{
"chrome": {
"browsing_history": [
{
"url": "http://example.com",
"comments": ["Nice!", "Great site."]
}
]
}
},
{
"network": {
"ip": "192.168.1.10",
"mac": "11:22:33:44:55:66"
}
}
]
}
```
- **Webhook URL:**
Send the data to your designated webhook endpoint.
### Data Structure:
The data in this presentation is ordered hierarchically (in a tree-like structure), where each node represents an entity (e.g., MAC address, data type, request metadata). Below is a structured example.
---
```
{
"mac_addresses": {
"00:1A:2B:3C:4D:5E": {
"device_info": {
"hostname": "Device-001",
"os": "Windows 10"
},
"data": [
{
"chrome": {
"browsing_history": [
{
"url": "http://reddit.com",
"comments": ["Garcia", "lmao"]
}
]
}
},
{
"network": {
"ip": "192.168.1.5",
"mac": "00:1A:2B:3C:4D:5E"
}
}
]
},
"11:22:33:44:55:66": {
"device_info": {
"hostname": "Device-002",
"os": "Ubuntu 20.04"
},
"data": [
{
"chrome": {
"browsing_history": [
{
"url": "http://example.com",
"comments": ["Nice!", "Great site."]
}
]
}
},
{
"network": {
"ip": "192.168.1.10",
"mac": "11:22:33:44:55:66"
}
}
]
}
}
}
```
### Data Filtering
After all this is complete
And you successfully creating a sorting algorithm for
Your log data. and a Token to create storage authorization
all You need to do is to store the data accordingly.
so everything looks nice. Goodluck :3
This is js a draft i didnt feel like finishing do whatever with this...
 

442,401

317,942

317,951

Top