Homesite data breach procedure

lang_custom/EN/cms_homesite.ini

@@ -74,3 +74,6 @@ TRACKER_ISSUE=Tracker Issue
 RESOLVING_TRACKER_ISSUES=Resolving tracker issues
 REPORTING_TRACKER_ISSUES=Reporting tracker issues which get resolved
 NOTIFICATION_TYPE_tracker_issue_added=Tracker issue added / reported from the report issue wizard
+
+PRIVACY_DATA_BREACH=Data Breach Procedure
+PRIVACY_DATA_BREACH_EXPLANATION=While users maintain responsibility for their own data (including damages resulting from a data breach), {1} will immediately execute the following procedure in the event of a breach being made aware through a credible source:<ol><li><strong>Reactive Mitigation:</strong> we may temporarily increase the strictness of firewalls / security systems, lock down administrative accounts or the ability to upload files, lock down all authorization (log-in) methods all-together, or take the site offline, depending on the perceived severity. This will typically last until proactive mitigation has been taken.</li><li><strong>Analysis:</strong> We will analyse and investigate the scope and severity of the data breach including identifying unauthorised access or use of personal information.</li><li><strong>Proactive Mitigation:</strong> Once we have a clear picture of what happened, we will take proactive mitigation as we deem fit. This could include resetting member passwords, banning rogue members and IP addresses, reverting changes or applying patches to software or services, rolling back the site to a stable backup / checkpoint, and/or reporting the breach to law enforcement authorities for additional investigation and prosecution.</li><li><strong>Communication:</strong> Once the above steps have been finished, we will communicate the data breach to all members of {1} via e-mail (except those who explicitly un-subscribed from e-mails) and via a news article on the site. We will explain what happened, what areas and data were affected, what {1} has done to mitigate the breach and prevent it in the future, and what members should do to protect themselves.</li></ol>
\ No newline at end of file

sources_custom/hooks/systems/privacy/cms_homesite.php

@@ -29,6 +29,8 @@ class Hook_privacy_cms_homesite extends Hook_privacy_base
             return null;
         }
 
+        require_lang('cms_homesite');
+
         return [
             'label' => 'cms_homesite:CMS_SITES_INSTALLED',
 
@@ -38,6 +40,10 @@ class Hook_privacy_cms_homesite extends Hook_privacy_base
             ],
 
             'positive' => [
+                [
+                    'heading' => do_lang('PRIVACY_DATA_BREACH'),
+                    'explanation' => do_lang_tempcode('PRIVACY_DATA_BREACH_EXPLANATION', escape_html(get_site_name())),
+                ]
             ],
 
             'general' => [