public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Stefan Sterz <s.sterz@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH proxmox-backup 2/2] docs: add paragraph on verification jobs to ransomware section
Date: Mon, 28 Nov 2022 15:34:01 +0100	[thread overview]
Message-ID: <20221128143401.610254-2-s.sterz@proxmox.com> (raw)
In-Reply-To: <20221128143401.610254-1-s.sterz@proxmox.com>

Signed-off-by: Stefan Sterz <s.sterz@proxmox.com>
---
drop this if inappropriate. i just thought this might answer some
questions that a somewhat advanced user may have about verification
jobs in this scenario.

 docs/storage.rst | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/docs/storage.rst b/docs/storage.rst
index 5ba419cd..c457ff06 100644
--- a/docs/storage.rst
+++ b/docs/storage.rst
@@ -475,6 +475,13 @@ While creating backups is important, verifying that they work is equally
 important. This ensures that you are able to react quickly in case of an
 emergency and keeps disruption of your services to a minimum.
 
+:ref:`Verification jobs <maintenance_verification>` can also assist in detecting
+a ransomware presence on a Proxmox Backup Server. Since verification jobs
+regularly check if all backups still match the checksums on record, they will
+start to fail if a ransomware starts to encrypt existing backups. Please be
+aware, that an advanced enough ransomware could circumvent this mechanism.
+Hence, consider verification jobs only as an additional, but not a sufficient
+protection measure.
 
 General Prevention Methods and Best Practices
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- 
2.30.2





  reply	other threads:[~2022-11-28 14:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-28 14:34 [pbs-devel] [PATCH proxmox-backup 1/2] docs: minor re-phrasing and spell checking clean up Stefan Sterz
2022-11-28 14:34 ` Stefan Sterz [this message]
2022-11-28 14:52 ` Daniel Tschlatscher
2022-11-28 15:03 ` [pbs-devel] applied: " Thomas Lamprecht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20221128143401.610254-2-s.sterz@proxmox.com \
    --to=s.sterz@proxmox.com \
    --cc=pbs-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal