Commit 086019cc authored by Bengfort's avatar Bengfort
Browse files

Merge branch 'threat-models' into 'main'

add section on benefits of database separation

See merge request !108
parents c1127446 3074e31c
Pipeline #13228 passed with stages
in 44 seconds
......@@ -90,7 +90,9 @@ We chose to split the data into three different categories:
Storing contact data in a separate database provides a clear structure for
developers that should help avoiding critical data leaks. Even if an attacker
is able to dump a whole table or even a whole database, this structure still
limits the impact.
limits the impact. An attacker without access to castellum would need physical
access to both databases in order to get the same level of access as with
However, it is important to understand that the barrier between recruitment and
contact data is not that high. Since castellum has full access to both, an
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment