President Biden is expected to publish executive order concerning new agreement on EU-U.S. data flows per Oct. 3. It covers legal protections over personal data access and use by U.S. national security entities. EC ratification could take 6 months. #GDPR https://t.co/PQ8GF2JZEf
27 Sep 2022
Happy 4th anniversary #GDPR #EuropeanUnion @EU_EDPB @toezicht_AP Indeed a strong and swift enforcement by #supervisory #authorities is crucial so companies do invest to protect #personaldata and reduce the risk of #dataleaks https://t.co/oGcBzb4hfV
25 May 2022
The #EDPB adopted #European harmonisation of #privacy #fines. The guidelines also include harmonised ‘starting points’ for the calculation of a fine. 3 elements considered: the categorisation of infringements by nature, infringement seriousness and the worldwide turnover. #GDPR https://t.co/E7L7Z0wV6X
17 May 2022
@ charanzova: 23 Apr 2022
@ vestager: 23 Apr 2022
Business Continuity Management: Escalation procedure (ICT).Many ICT-departments modelled their management processes according to the ITIL (ISO 20000) standard and have a service desk/help desk process implemented that receives user incidents. In addition to the automatic Asset management process to update the CMDB , a NOC function to check the availability of the network and their attached devices is deployed. This monitoring process can automatically generate incidents (tickets) for the service desk.
As a result, user requests and various (computer) alerts (incidents) are received daily by the help desk to be serviced as fast, complete and correct as possible. Implementing the procedure below creates an additional filter to timely detect calamities.
Picture 1. Implement the Business Continuity escalation procedure in normal ITIL Servicedesk procedures.
The Business Continuity Manager evaluates the incident, trends and decides if the Business Continuity procedures should be activated or returns the incident to the Service desk.
You may vote your opinion about this article:
Scripts and programming examples disclaimerUnless stated otherwise, the script sources and programming examples provided are copyrighted freeware. You may modify them, as long as a reference to the original code and hyperlink to the source page is included in the modified code and documentation. However, it is not allowed to publish (copies of) scripts and programming examples on your own site, blog, vlog, or distribute them on paper or any other medium, without prior written consent.
Many of the techniques used in these scripts, including but not limited to modifying the registry or system files and settings, impose a risk of rendering the Operating System inoperable and loss of data. Make sure you have verified full backups and the associated restore software available before running any script or programming example. Use these scripts and programming examples entirely at your own risk. All liability claims against the author in relation to material or non-material losses caused by the use, misuse or non-use of the information provided, or the use of incorrect or incomplete information, are excluded. All content is subject to change and provided without obligation.