From 13869eb94e829851e1fd5ffbc6e657a8f6dac54a Mon Sep 17 00:00:00 2001 From: Cliff Hill Date: Sat, 23 Aug 2025 17:43:13 -0400 Subject: [PATCH] More readme stuff. Signed-off-by: Cliff Hill --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index 9da8a413..32ad14b7 100644 --- a/README.md +++ b/README.md @@ -8,6 +8,8 @@ This is a full-stack application simulating an online booking system for confere 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. +There already is several pieces for helping secure the application on the backend, using the HyperModern Python cookiecutter and the tools it brings into play, however additional systems could be tied into github to help check things further (like New Relic). + ### AI Use I used AI to stub out a couple of files: