Author: admin

Thanks to morrolinux 

docker compose up -d
docker ps

docker exec -it headscale headscale users create msolci
https://tailscale.com/kb/1031/install-linux
— sul client linux
curl -fsSL https://tailscale.com/install.sh | sh
tailscale up –login-server http://mail.saic.it:8585
— su server headscale
docker exec -it headscale headscale nodes register –user usolci –key [chiave macchina ottenuta prima]
docker exec -it headscale headscale nodes list

 

services:
headscale:
image: docker.io/headscale/headscale:latest
restart: unless-stopped
container_name: headscale
ports:
– “0.0.0.0:8585:8080”
– “0.0.0.0:9191:9090”
volumes:
– ./config:/etc/headscale
– ./lib:/var/lib/headscale
– ./run:/var/run/headscale
command: serve
heascale-ui:
image: ghcr/gurucomputing/headscale-ui:latest
container_name: headscale-ui
restart: unless-stopped
environment:
– HTTP_PORT=8080
ports:
– “8586:8080”

docker exec -it headscale headscale apikeys create

tailscale up –login-server http://headscale.saic.it:8585 –advertise-routes=192.168.X.0/24 –advertise-exit-node

docker stop $(docker ps -q)
docker compose stop
docker-compose down

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Step 1. – Dora requirements : here

from here

The main participants in a TIBER-EU test belong to one of five different teams, depending on their roles and responsibilities under the TIBER-EU framework:

 

• blue team – the people in the entity that is the subject of the test, whose prevention, detection and response capabilities are being tested without their foreknowledge
• threat intelligence provider – the team that looks at the range of possible threats and carries out reconnaissance on the entity
• red-team testers  – the team that carries out the simulated attack by attempting to compromise the critical functions of the entity, mimicking a cyber-attacker
• control team – a small team within the target entity whose members are the only ones there who know a test is happening and who lead and manage the test in collaboration with the TIBER cyber team
• TIBER cyber team – the team within the authority that is responsible for overseeing the test and making sure it meets the requirements of the TIBER-EU framework, thus enabling mutual recognition of the test by relevant authorities

 

🔍 1. Trova il PID (Process ID) del processo

Puoi usare lsof oppure netstat (se installato):

Con lsof:

Con netstat (se installato):

Con ss (più moderno):