Auditing several sites
with the right tools.
For several client sites, I carried out security and infrastructure audits: assessing the current state, spotting risks and proposing a prioritised action plan. Each tool answers a specific question:
- Nmapmapping
- List the machines on the network, their open ports and exposed services, to spot what shouldn't be exposed.
- Wiresharktraffic analysis
- Capture and read network traffic: diagnose slowness, understand a flow, spot protocols travelling in clear text.
- NetSpotWiFi coverage
- Measure signal quality across the premises and produce coverage maps, to place access points in the right spots.
- Wazuhendpoint posture
- Check machine configuration against security best practices and list known vulnerabilities.
Deliverables: physical and logical network diagrams, a recommendations report and procedures for the technicians.
See what is happening,
block what shouldn't get through.
Beyond audits, I put security tools into production at client sites. Each one covers a different layer:
- WazuhSIEM · FIM
- Centralises machine logs, raises alerts on suspicious events and monitors the integrity of sensitive files (FIM): any unexpected change is reported.
- SuricataIDS / IPS
- Inspects network traffic using signatures and raises alerts on known malicious behaviour: scans, exploits, suspicious communications.
- AdGuard HomeDNS filtering
- Blocks malicious or inappropriate domains before any connection is made, an effective filter especially for pupils' networks.
- VPNremote access
- Client-to-site access with LDAP authentication and MFA, site-to-site IPsec links on OPNsense.
Solve methodically,
explain simply.
Day to day, I handled level 1 and 2 support tickets. For network issues, I work up the layers of the OSI model one at a time, from the cable to the application, instead of testing at random:
- PhysicalCable, wall socket, switch port, link lights: is the link up?
- Data linkIs the port in the right VLAN? Does the switch see the MAC address?
- NetworkIP address, DHCP lease, gateway: can the machine reach the rest of the network?
- TransportIs the service port open? Is a firewall or the VPN blocking it?
- ApplicationDNS resolution, access rights, software configuration.
Most of the users I supported were beginners: teachers and administrative staff. A large share of the support was application-level, especially on the Office suite. I learned to adapt how I explain things, to make the cause of a problem clear without jargon and to document the fix for next time.
I also worked on site: deploying workstations with WDS / PXE, configuring switches and WiFi controllers (Cisco, Ruckus).
Managing attendance
at the school library.
For the Sainte-Élisabeth school in Paris, I designed and built CDIstats, an application that tracks attendance at the school library: students scan their card on the way in and on the way out.
- Development: written entirely in Python, PEP 8-compliant code, then packaged with PyInstaller into a standalone Windows executable that runs on the library computers without installing Python.
- Card reading: the application reads the student's card and logs their entry and exit.
- Managing student flow: the library team follows arrivals and departures and can organise supervision around busy periods.
- Supervision dashboard: peak hours, attendance by class and trends over time, at a glance.
- GDPR-compliant: only the data that is needed is collected (data minimisation), and entry and exit logs are kept only as long as necessary (storage limitation, Article 5 GDPR). They are then anonymised and deleted automatically, so the statistics stay useful without keeping students' identities.
What these assignments gave me.
Working across several sites taught me to adapt quickly to different environments, to prioritise risks and to stay patient and clear with users.
- Security audit
- Nmap
- Wireshark
- NetSpot
- Wazuh
- Suricata
- AdGuard Home
- VPN LDAP / MFA
- IPsec · OPNsense
- OSI model
- L1 / L2 support
- Office suite
- WDS / PXE
- Cisco · Ruckus
- CDIstats
- Python
- PyInstaller
- GDPR
- Documentation