This site presents the internal services and their configurations provided by T8G1-Skylab group, the cluster’s
network topology and documentation for users and administrators along
with the security implemented within the network.
[See the public repository for this site here]
Make it possible that all traffic originating from GroupVM should pass through squid and firewall is
adjusted accordingly See Squid in section: Group-vm
Analyze the pros/cons of using proxy for all traffic
originating from individual VMs in the group and decide on it.
Document your resons and choice and do the needful depending on
the decision. See Proxy in section: Group-vm
Make it possible for all individual members of the group to be able to share documents in a common folder
where they will update logs of what change they have made to the Group VM and only the owner of the file is
able to modify/delete the file. Rest should be able to read all
information in the file. So, each member should have his own file
See NFS in section: #2: Group-vm
[optional] place log files in a container separate container. How does it affect security
Install a service in docker of your choosing as group which
you think will need to share amongst the group,
for example authentication server, DNS server etc. Create a DMZ(a separate subnet –maybe a 10 subnet with your
group number as subnet such as t1g1 is 10.11 and t1g2 is 10.12
and so on ) See Custom ingress in section: Group-vm
Discuss the security and other networking considerations for keeping containers isolated from local
network and making them available over the local network See Security in section: nikolaj-vm
Design a network topology (not configure) for the whole group
Decide where in the topology will you place the various servers.
Setting up lxd on GroupVM is not a trivial task
so anything there has to docker but in the documentation you can
argue if you would rather used lxd and why? See Containers in section:
Topology
Talk about strength and vulnerabilities of your infrastructure
Launch attacks like DDOS on other servers, use various tools to check
vulnerabilities in the server setup of other groups
You can reconfigure your switch(just add the vlan of the group
so that you can get ip from their dhcp) to access other groups local network in the class
Then you can run these vulnerability scanners like nmap and nikto to find out more about their network,
services etc.
Document your findings, vulnerabilities and suggest way to protect/attack the vulnerabilities
62501 Linux Server and Network Course at DTU, spring 2022 edition.
T8G1-Skylab
Host cards
This configuration contains four docker worker nodes with two of them
assigned the swarm managing role.