08/11

Project 08 · of 11

Securing an information system

SAÉ 4.01 · BUT2 · Cybersecurity · team of 3 Completed
ProxmoxFirewallLDAP / LDAPSPKI / TLSOpenVPNDNS BIND9NFSApache GuacamolePostfix / DovecotCeph
The project

SAÉ 4.01, “Securing an information system”, is the major project of the cybersecurity track in semester 4. The goal is to build, from the WAN to the client workstation, the complete information system of a fictional company, then to secure it layer by layer. The work is done in a team of 3, with a lot of freedom in technical choices as long as the specification is met.

The target architecture starts from a client and a WAN link protected by a firewall, behind which the internal services are organised: DNS, LDAP directory, NFS file sharing, email (Postfix SMTP / Dovecot IMAP), a load-balanced web service, OpenVPN access for remote workstations and an Apache Guacamole administration bastion. Security is built around an in-house public key infrastructure (PKI): root certificate, server and client certificates to encrypt protocols with TLS (LDAPS, HTTPS, SMTPS, IMAPS) and authenticate remote workstations.

The whole lab runs on the Proxmox virtualisation platform: IP addressing plan, network creation (LAN without DHCP, NAT network), VM provisioning through linked clones and snapshots from a template, Ceph (RBD) storage with quotas. Part of the SAÉ is also to put Proxmox to the test and produce a report on its usability, bugs and suggestions.

The project is completed: the services were deployed and configured one by one (DNS BIND9, PKI, LDAP with LDIF and TLS, OpenVPN, NFS authenticated through LDAP/PAM, high-availability web, email). It ended with a 20-minute technical presentation focused on the chosen solution, the reasoning behind the choices, a close look at the security measures and a risk assessment.

Goal

Create and secure a company's information system end to end: a network virtualised on Proxmox with a firewall, LDAP directory, NFS sharing, email, remote VPN access and a bastion, relying on a public key infrastructure (PKI) to encrypt protocols with TLS and authenticate workstations.

Approach
  • Define an IP addressing plan, routing and filtering rules.
  • Build the lab on Proxmox: networks (LAN without DHCP, NAT), VMs through linked clones and snapshots, Ceph (RBD) storage.
  • Set up the firewall and an Apache Guacamole administration bastion (LDAP authentication, logging).
  • Deploy a DNS service with BIND9 (forward and reverse zones).
  • Build a PKI: root certificate, server certificate and client certificate.
  • Create an LDAP directory (LDIF, accounts, passwords) secured with LDAPS/TLS.
  • Deploy an OpenVPN server for remote workstations and an NFS server authenticated through LDAP/PAM.
  • Set up email (Postfix SMTP, Dovecot IMAP) backed by LDAP and secured with TLS, plus a high-availability web service.
  • Prepare the final presentation (video demo, reasoning behind the choices, risk assessment).
Technical challenges
  • Designing a consistent PKI to secure all services with TLS (LDAPS, HTTPS, SMTPS, IMAPS) and authenticate remote workstations.
  • Integrating centralised LDAP authentication on the Linux side (PAM) for NFS, email and the bastion.
  • Mastering Proxmox: linked clones, snapshots, Ceph storage with quotas.
Deliverables
  • Working lab of the secured infrastructure on Proxmox.
  • Report on using the Proxmox platform (usability, difficulties, suggestions).
  • 20-minute technical presentation with a video demo, reasoning behind the choices and risk assessment.

Interactive demo · defence in depth

Pick a scenario to follow a flow through the infrastructure, or click a service to see its role.

The interactive demo needs JavaScript.