From 4479e1d0218cd93883d5c8df8234806a52a3a4d6 Mon Sep 17 00:00:00 2001 From: Cliff Hill Date: Sat, 23 Aug 2025 17:41:30 -0400 Subject: [PATCH] Added security concerns. Signed-off-by: Cliff Hill --- README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.md b/README.md index e46955cb..9da8a413 100644 --- a/README.md +++ b/README.md @@ -4,6 +4,10 @@ This is a full-stack application simulating an online booking system for conference rooms. +### Security concerns + +There is no login or security in place with this project. However if set up with zero trust, an example scenario could use OpenID or similar login security, encrypted JWTs, secure connections could be established to the database as well as all traffic being moved to https rather than http, locking everything down to ensure that those who communicate with any part of this system are authenticated and have only the access that they are authorized. Each endpoint would need to be able to check that the user is authenticated and has a valid token that has not expired in order to be used. + ### AI Use I used AI to stub out a couple of files: