Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix: format Least privilege #1005

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from
Open

fix: format Least privilege #1005

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion 05_node_operations.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -533,7 +533,7 @@ To secure your operating system, here are some of the top items to consider:

Provenance:: Start by ensuring that you are downloading the correct operating system image, and verify any signatures or checksums before installing it. Extend this to any software that you install. Double-check any source or URL from where you download. Verify the integrity and correctness of the downloaded software via signature and checksum verification.
Maintenance:: Make sure that you keep your operating system up to date. Enable automated daily or weekly installation of security updates.
Least privilege: set up users for specific processes and give them the least access needed to run a service. Do not run processes with admin privileges (e.g., +root+).
Least privilege:: set up users for specific processes and give them the least access needed to run a service. Do not run processes with admin privileges (e.g., +root+).
Process isolation:: Use the operating system features to isolate processes from each other.
Filesystem permissions:: Configure the filesystem carefully, on the least-privilege principle. Do not make files readable or writable by everyone.
Strong authentication:: Use strong randomly generated passwords or, whenever possible, public-key authentication. For example, it is safer to use Secure Shell (SSH) with a cryptographic key pair instead of a password.
Expand Down