44 lines
2.3 KiB
TeX
44 lines
2.3 KiB
TeX
% =========================================================================== %
|
|
\nn{Conclusion}
|
|
|
|
The objectives of the thesis have been to create the Password Compromise
|
|
Monitoring Tool aimed at security-conscious user in order to validate their
|
|
assumptions on the security of their credentials. The thesis opened by diving
|
|
into cryptography topics such as encryption and briefly mentioned TLS.
|
|
|
|
Additionally, security mechanisms such as Site Isolation and Content Security
|
|
Policy, commonly employed by mainstream browsers of today, were introduced and
|
|
the reader learnt how Content Security Policy is easily and dynamically
|
|
configured.
|
|
|
|
An extensive body of the thesis then revolved around the practical part,
|
|
describing everything from tooling used through high-level view of
|
|
application's architecture to implementation of specific parts of the
|
|
application across the stack.
|
|
|
|
Finally, the practical part concluded by broadly depicting validation
|
|
methods used to verify if the application worked correctly.
|
|
|
|
The author would like to recognise that there are certain aspects of the thesis
|
|
in the need of further development. It is necessary to admit that not
|
|
everything could have realistically been realised in the limited timespan and
|
|
scope imposed on the project to prevent diverging. The concerns mentioned above
|
|
constitute clear candidates for future work of the author who intends to
|
|
improve on the existing state, for example accessibility-wise. The author's
|
|
unfamiliarity with the accessibility tooling sometimes compromised on the
|
|
quality in this segment of the application, but it is a known deficiency.
|
|
Furthermore, the list of tasks for the future may also contain adding
|
|
\emph{fuzzing} tests for the program, producing Software Bill of Materials,
|
|
utilising additional immutable database or unifying the frontend design
|
|
language across the pages.
|
|
|
|
The program does have a very solid core that for instance listens for OS
|
|
signals, handles graceful shutdown and supports structured logging but still
|
|
has room for improvements, despite the fact that its creation has been
|
|
best-effort. Due to a number of reasons mentioned earlier, it should not be
|
|
called an utterly \emph{finished} project yet, but it can already serve a clear
|
|
purpose.
|
|
|
|
|
|
% =========================================================================== %
|