Warning: Use of undefined constant TIMEBEFORE_NOW - assumed 'TIMEBEFORE_NOW' (this will throw an Error in a future version of PHP) in /home/sites/dataclassification.com/public_html/wp-content/themes/data-classification/singular.php on line 16

Warning: Use of undefined constant TIMEBEFORE_MINUTE - assumed 'TIMEBEFORE_MINUTE' (this will throw an Error in a future version of PHP) in /home/sites/dataclassification.com/public_html/wp-content/themes/data-classification/singular.php on line 17

Warning: Use of undefined constant TIMEBEFORE_MINUTES - assumed 'TIMEBEFORE_MINUTES' (this will throw an Error in a future version of PHP) in /home/sites/dataclassification.com/public_html/wp-content/themes/data-classification/singular.php on line 18

Warning: Use of undefined constant TIMEBEFORE_HOUR - assumed 'TIMEBEFORE_HOUR' (this will throw an Error in a future version of PHP) in /home/sites/dataclassification.com/public_html/wp-content/themes/data-classification/singular.php on line 19

Warning: Use of undefined constant TIMEBEFORE_HOURS - assumed 'TIMEBEFORE_HOURS' (this will throw an Error in a future version of PHP) in /home/sites/dataclassification.com/public_html/wp-content/themes/data-classification/singular.php on line 20

Warning: Use of undefined constant TIMEBEFORE_YESTERDAY - assumed 'TIMEBEFORE_YESTERDAY' (this will throw an Error in a future version of PHP) in /home/sites/dataclassification.com/public_html/wp-content/themes/data-classification/singular.php on line 21

Warning: Use of undefined constant TIMEBEFORE_FORMAT - assumed 'TIMEBEFORE_FORMAT' (this will throw an Error in a future version of PHP) in /home/sites/dataclassification.com/public_html/wp-content/themes/data-classification/singular.php on line 22

Warning: Use of undefined constant TIMEBEFORE_FORMAT_YEAR - assumed 'TIMEBEFORE_FORMAT_YEAR' (this will throw an Error in a future version of PHP) in /home/sites/dataclassification.com/public_html/wp-content/themes/data-classification/singular.php on line 23

Warning: Use of undefined constant TIMEBEFORE_DAYS - assumed 'TIMEBEFORE_DAYS' (this will throw an Error in a future version of PHP) in /home/sites/dataclassification.com/public_html/wp-content/themes/data-classification/singular.php on line 24

Warning: Use of undefined constant TIMEBEFORE_WEEK - assumed 'TIMEBEFORE_WEEK' (this will throw an Error in a future version of PHP) in /home/sites/dataclassification.com/public_html/wp-content/themes/data-classification/singular.php on line 25

Warning: Use of undefined constant TIMEBEFORE_WEEKS - assumed 'TIMEBEFORE_WEEKS' (this will throw an Error in a future version of PHP) in /home/sites/dataclassification.com/public_html/wp-content/themes/data-classification/singular.php on line 26

Warning: Use of undefined constant TIMEBEFORE_MONTH - assumed 'TIMEBEFORE_MONTH' (this will throw an Error in a future version of PHP) in /home/sites/dataclassification.com/public_html/wp-content/themes/data-classification/singular.php on line 27

Warning: Use of undefined constant TIMEBEFORE_MONTHS - assumed 'TIMEBEFORE_MONTHS' (this will throw an Error in a future version of PHP) in /home/sites/dataclassification.com/public_html/wp-content/themes/data-classification/singular.php on line 28
  • It’s classified, but so what?

    Here at HANDD we do lots of work with organisations looking to implement a Data Classification (DC) solution. There are many different resources on this website which condone using DC within your technology stack.

    But as we’ve said so many times before, DC does not solve your security issues. It helps drive upstream and downstream technology it doesn’t prevent a breach occurring.

    20th June 2022, we’ve seen another embarrassing breach, this time from a government website, which highlights that point precisely.

    The document in question, which set about rulings on technology usage within the country in questions government, was classified as “restricted” and for access within the government departments only. However, found with relevant ease by the online website The Register.

    The majorly ironic item for us governs the uploading of internal/restricted/confidential government data!

    There’s a bunch of bits of technology which could have helped them here. Data Discovery (DD) in conjunction with the underlying classification policy perhaps being the obvious choice to find the offending server location of the data.

    Or perhaps Data Loss Prevention (DLP) to check the classification tags when the document was attempted to be uploaded or downloaded.

    The solution could be delivered many ways, but the problem remains the same. Choosing DC is good, making data protection decisions based on it is so so much better!

    If you would like to discuss how HANDD can help your organisation with a DC solution or enhance DC policy further with a DLP or DD tool please contact us today at info@handd.co.uk or 08456 434 063.

Securing the Journey of Your Data
A Free Advisory Paper

Download

Get In Touch

Please fill in the form and our staff will get in touch