@ charanzova: 23 Apr 2022
@ vestager: 23 Apr 2022
There is an official #gdpr #adequacydecision for the #UnitedKingdom so we can keep transferring #PersonalData to the #UK and back because the #UK has deemed the security levels of #PD in the #EU as #adequate #Brexit #privacy Great job #EuropeanCommission https://t.co/U3zFSAHCJ9 https://t.co/exqwOfVgBB https://t.co/Qbe9yfpuXi
30 Jun 2021
#EDPS opens investigations following the #Schrems II Judgement regarding the use of cloud services provided by #Amazon Web Services #aws and #Microsoft and one regarding the use of Microsoft #Office365 by the European Commission #gdpr #privacy #cloudact https://t.co/BJP48W6WtV https://t.co/fJA1stx7oy
28 May 2021
Dutch #supervisoryAuthority first fine for a #Municipality. #Enschede city fined 600.000 for #wifitracking visitors of shopping centre for toooooo long. @toezicht_AP #GDPR #privacy #fines https://t.co/CjCPwqgUpo https://t.co/vSkoTAkoVE
29 Apr 2021
The security of a Windows 2008 (r2) Active Directory server can be significantly improved by configuring the server to accept only signed or SSL/TLS LDAP binds.The security of a Windows 2008 (r2) Active Directory server is default configured to be backwards compatible with Windows 2000 / NT and XP. Now that these operating systems are replaced (they are not supported by Microsoft for months or even years now) the security can be significantly improved by configuring the server to reject Simple Authentication and Security Layer (SASL) LDAP binds that do not request signing (integrity verification) or to reject LDAP simple binds that are performed on a clear text (non-SSL/TLS-encrypted) connection. SASLs may include protocols such as the Negotiate, Kerberos, NTLM, and Digest protocols. This document has information about:
How to verify current Authentication level:
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.