Vanderbilt solutions and products enable customers to manage and process personal data in such a way as to meet GDPR requirements. This guide is intended to help and support our customers in assessing their own readiness in meeting their responsibilities and obligations towards the new regulations.
Data protection is a fundamental right whereby everyone has the right to the protection of personal data concerning him or her. The General Data Protection Regulation (GDPR) is applicable from 25th May 2018 and is designed to give individuals more control over their personal data. There is one set of rules for the whole of the EU, which can be complemented in some areas by national legislation.
The GDPR imposes obligations on businesses or organisations that collect, use and process personal data. At the centre of GDPR is the requirement for organisations and businesses to be fully transparent about how they are using and protecting personal data, and to be able to demonstrate accountability for their data processing activities. Such data must be processed fairly for specified purposes and on the basis of the consent of the person concerned or some other legitimate basis laid down by law.
While Vanderbilt offers customers flexible and intuitive product functionality to facilitate compliance with the new regulations, the Vanderbilt organisation does not collect, control, use or process personal data which exists within Vanderbilt on-premises products. Therefore, it is the role and responsibility of the controller and processor of personal data to ensure that obligations stated in GDPR are complied with.
If you are in any doubt or are unsure about the identity of the data controller and/or data processor, in any case, you should consult your legal adviser.
The term “personal data” means any information relating to a living person who is identified or identifiable.
A person is identifiable if they can be identified directly or indirectly using an “identifier”. The GDPR gives examples of identifiers, including names, identification numbers, and location data. A person may also be identifiable by reference to factors which are specific to their identity, such as physical, genetic or cultural factors.
Personal data that has been de-identified, encrypted or pseudonymised but, can be used to re-identify a person remains personal data and falls within the scope of GDPR. If personal data has been rendered anonymous in such a way that the individual is no longer identifiable, then this is not considered personal data. For data to be truly anonymized, the anonymization must be irreversible.
The law protects personal data regardless of the technology or method used for processing that data – it applies to both automated and manual processing. It also doesn’t matter how the personal data is stored – in an IT system, through video surveillance, or on paper; in all cases, personal data is subject to the protection requirements set out in the GDPR.
Processing covers a wide range of operations performed on personal data, including by manual or automated means. It includes the collection, recording, organisation, structuring, storage, adaptation or alteration, retrieval, consultation, use, disclosure by transmission, dissemination or otherwise making available, alignment or combination, restriction, erasure or destruction of personal data.
The General Data Protection Regulation (GDPR) applies to the processing of personal data wholly or partly by automated means as well as to non-automated processing, if it is part of a structured filing system.
A data controller is an individual or the legal person who controls and is responsible for the keeping and use of personal information on a computer or in structured manual files. Being a data controller carries with its legal responsibilities, so you should be quite clear if these responsibilities apply to you or your organisation.
If you or your organisation controls and is responsible for the personal data which it holds i.e. decides what personal information is going to be kept and to which use the information will be put, then you or your organisation is a data controller.
Examples of cases where the data controller is an individual include general practitioners, pharmacists, politicians and sole traders, where these individuals keep personal information about their patients, clients, constituents etc.
If you or your organisation holds the personal data, but some other individual or organisation decides and is responsible for what happens to the data, then that other individual or organisation is the data controller, and you or your organisation is a "data processor".
Examples of data processors include payroll companies, accountants, and market research companies, all of which could hold or process personal information on behalf of someone else.
In order to legally process personal data, organisations and businesses must identify and document the legal basis for doing so from the start. Some of the legal ways to process data include:
If you are in any doubt, as to whether you have acquired sufficient consent to process personal data, you should consult your legal adviser.
If you hold or process (enter, edit, maintain) personal data (data processor) on behalf of your customer (data controller) you will require a data processing contract. We would recommend obtaining legal advice to best ensure the contract addresses appropriate security and other data protection safeguards. As part, we would advise customers to have a checklist regarding data handling and the handover of the security system.
It is clear the law is changing to GDPR and this needs to be factored into security system planning. Areas need be identified and addressed that may cause compliance problems under the GDPR. Under GDPR individuals have the right to be given clear information relating to the use of their data.
The first practical step is to identify your role and responsibility with respect to GDPR. Are you a data controller or data processor or both? If you are in any doubt or are unsure about the identity of the data controller and/or data processor, in any case, you should consult your legal adviser.
The second step is to become accountable. Consider all the personal data you are handling when working with the security system and examine it under the following headings:
The following information outlines how the Vanderbilt Entro V6.7 system can be used to facilitate GDPR compliancy.
Collection of personal data is not mandatory within Entro, although it does have the capacity to store some user-definable fields, which could be used to store personal data.
The entry of data and the maintaining of data is controlled by the data controller and data processor of the site. As such it is the responsibility of the data controller and/or data processor to ensure the legal basis for processing the personal data is obtained.
There are no explicit procedures built into the Entro SW for obtaining user consent, or recording it.
Data is stored both at the PC, and at the Entro controllers, with all data that is stored on the PC being replicated at the controller. For every controller in the system there is essentially another full backup of the database, that can be pulled back in to the PC. IP Comms between PC and SR, and SR -> SR is RC4 encrypted.
The database is in a bespoke format, and cannot be read by conventional DB analysis tools such as SQL Management Studio etc. It is only possible to view the contents of a database via the Entro software, when you have the correct combination of serial number, system name, and valid login credentials.
There exists a tool that allows for the retrieval of system name/serial number and login information, but access to this is restricted. The database itself uses a custom encryption protocol to protect it when stored on the PC.
User data is retained on the Entro system until removed by the administrator of the system. It is the responsibility of the system administrator to communicate in a transparent way the data retention period.When a card is deleted from the system, the card immediately becomes invalid, however the associated user information will be retained on the Entro DB for an additional 3 weeks, after which time it will be automatically deleted from the database.
Event data is kept as long as the setting is for event retention or if a specified request is made to remove personal data from the event logs. This event data retention is on a per software user basis, and as such for every user of the software, there will exist a set of event files.
If a request is made it is the responsibility of the data controller and/or data processors to outline the policy and to supply the data in a timely manner in accordance with GDPR regulations.
It is possible to filter the events held in the Entro system to see what individual data is held about a person, e.g. recent log events, or information relating to their individual record. This data can be exported in a standard format such as CSV.
If a request is made it is the responsibility of the data controller and/or data processors to outline the policy and to remove the data in a timely manner in accordance with GDPR regulations.
Cardholder data can be manually deleted from the Entro system, upon request. However, deleting a cardholder will not delete their associated events. This will be retained for as long as the setting is for event retention or if a specified request is made to remove personal data from the event logs.
It is the responsibility of the data controller and/or data processor to disclose who has access to the personal data on the Entro system installed on site. Entro has the capability of defining different user logins to the client software. There are different levels of login available. Vanderbilt have no access to and/or ability to process personal data on an on-premises Entro system.
In normal operational mode Entro user data is not shared outside the system. It is the responsibility of the data controller and/or data processor to disclose if the system is configured in a way which transfers data outside the EEA.