mstoeck3/autopsy-flatpak
1
0
Fork 0
mirror of https://github.com/overcuriousity/autopsy-flatpak.git synced 2025-07-19 11:07:43 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #1694 from sleuthkit/doc-update

Browse Source 
Added page to docs about security
This commit is contained in:
Brian Carrier 2015-11-03 18:16:44 -05:00
commit 07699e4442
2 changed files with 17 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
docs/doxygen-user/main.dox
View File

@ -52,6 +52,7 @@ The following topics are available here:
- \subpage install_postgresql
- \subpage install_solr
- \subpage windows_authentication
- \subpage multiuser_sec_page
- \subpage multiuser_page
If the topic you need is not listed, refer to the <a href="http://wiki.sleuthkit.org/index.php?title=Autopsy_User%27s_Guide">Autopsy Wiki</a> or join the <a href="https://lists.sourceforge.net/lists/listinfo/sleuthkit-users">SleuthKit User List</a> at SourceForge.

16
docs/doxygen-user/multiuser-security.dox Normal file
View File

@ -0,0 +1,16 @@
/*! \page multiuser_sec_page Multi-user Case Security
\section mulit_sec_overview Overview
This page outlines the security protections that exist in a multi-user case deployment so that you can protect sensitive data. A multi-user deployment must be in a private network to ensure that only authorized users can access data. Remote sites should connect to central services via a VPN.
- Central Storage: It is your responsibility to use folder-based permissions to restrict access to the case folder. A user must be able to read and write into the case folder to open a case via Autopsy. It contains the Solr index, module output, logs, and reports.
- Central Database: PostgreSQL supports authentication via a login and password. Each Autopsy client must be configured with a PostgreSQL username and password. It is up to you to decide if there is a single username and password for the entire lab or if you will configure a new one for each client.
- Central Solr: Solr does not require a username or password to connect to it and query it. There is an optional way to configure Solr to require them, but we have not tried that yet.
- Messaging Service: ActiveMQ can be configured to require a username and password. Like the central database, it is up to you to decide on if there is a single username and password or one for each client.
Because the Solr server does not restrict access to the indexed content,
you should depoly these services in a network that only authorized users
have access to. Future versions will allow for additional protection
of sensitive data.
*/