Skip to content

Commit

Permalink
Best-practice guide
Browse files Browse the repository at this point in the history
  • Loading branch information
MathiasOHedegaard committed Aug 22, 2024
1 parent 1b893b5 commit 0d40577
Show file tree
Hide file tree
Showing 3 changed files with 24 additions and 1 deletion.
21 changes: 21 additions & 0 deletions docs/guides/best_practice_guides/How_to_avoid_malware.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
# How to minimize the risk of malware on your STATO server

By adhering to these best practices, you can significantly reduce the risk of malware infections and strengthen the overall security posture of your STATO environment

### 1. **Use trusted repositories**

- **Stick to official sources**: Always install software from your Linux distribution’s official repositories (e.g., APT for Ubuntu/Debian, YUM/DNF for CentOS/RHEL). These repositories are regularly vetted and maintained by trusted developers, ensuring a higher level of security.

- **Verify external sources**: If you need to use third-party repositories or download packages from external sources, ensure they are well-known, trusted, and verified. Always check for digital signatures and authenticity.

### 2. **Opt for minimalist installation**

- **Install only essential packages**: Limit the installation to only the software necessary for your server’s intended purpose. A minimalist approach reduces the potential attack surface by limiting the number of installed packages that could be compromised.

### 3. **Keep the operating system and packages up-to-date**

- **Timely kernel and software updates**: Regularly update the Linux kernel and all installed packages to ensure that security vulnerabilities are promptly patched. Consider automating this process where possible to minimize delays.

### 4. **Implement strong access controls**

- **Enforce Strong SSH Keys**: Mandate the use of strong, unique SSH keys for server access. Avoid using weak or default passwords.
1 change: 1 addition & 0 deletions docs/guides/best_practice_guides/index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
In this section, we outline best practices for effectively utilizing STATO. Adhering to these guidelines will optimize your workflow, ensure efficient resource usage, and maintain system stability for all users.
3 changes: 2 additions & 1 deletion mkdocs.yml
Original file line number Diff line number Diff line change
Expand Up @@ -23,10 +23,11 @@ nav:
# - "Ubuntu 20.04": guides/application_guides/ubuntu/ubuntu_20-04.md
# - "QGIS": guides/application_guides/qgis.md # NEEDS REWORK
- "Best-practice guides":
- guides/best_practice_guides/index.md
- "Best-practice guides": guides/best_practice_guides/index.md
- "Delete and restart an instance from the volume": guides/best_practice_guides/delete_instance_launch_from_volume.md
- "Stop, pause & delete instances": guides/best_practice_guides/Pause_shutdown_delete_instances.md
- "Create smaller volumes": guides/best_practice_guides/diffrent_volume_size.md
- "How to Minimize the Risk of Malware": guides/best_practice_guides/How_to_avoid_malware.md
- "Advanced guides":
- guides/advanced_guides/index.md
- "CLI": guides/advanced_guides/openstack_CLI.md
Expand Down

0 comments on commit 0d40577

Please sign in to comment.