Bárbara M. Peres · Full-Stack Developer & AI Engineer, Portugal
The interactive version of this page did not load. Reloading usually fixes it. Otherwise the links below still reach me.
Security Engineering · 2023–2024
End-to-end secure medical records platform
A Java client/server for exchanging medical files between doctors and patients, built over three phases of an information-security course. Phase 1 was the cryptography: hybrid encryption (RSA-2048 wrapping AES-128), digital signatures and secure envelopes. Phase 2 added multi-user authentication over TLS and a MAC-protected users file. Phase 3 moved out to the perimeter, with iptables firewall rules and a Snort IDS.
Java · RSA-2048 · AES-128 · KeyStore · TLS · MAC + salt · X.509 Certificates · iptables · Snort IDS
A platform where doctors and patients exchange medical files is a bad place to start from, security-wise: the data is sensitive and the two sides share no trust anchor. On top of that, the server holding the files should not be able to read them. The brief split the work into three passes, and each pass closed a different attack surface.
Phase 1 was cryptography. Every file gets its own AES-128 key, wrapped with RSA-2048, plus a digital signature for authorship. Secure envelopes mean the server never holds plaintext. Keys and X.509 certificates go through the Java KeyStore. Phase 2 was authentication: multi-user login over TLS, with the users file protected by a salted MAC so credentials cannot be tampered with offline. Phase 3 was the perimeter, iptables rules restricting who can reach the service at all, and Snort on top as intrusion detection. We were a team of three and I worked as security developer.
Each of the three layers is useful without the other two. An attacker who gets the stored files gets ciphertext. On the wire there is TLS, and anything probing the host runs into the firewall and the IDS first.