<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Doctena TechBlog - Medium]]></title>
        <description><![CDATA[Doctena Technology Blog - Medium]]></description>
        <link>https://medium.com/doctena-techblog?source=rss----7cc66ebb9393---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Doctena TechBlog - Medium</title>
            <link>https://medium.com/doctena-techblog?source=rss----7cc66ebb9393---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 23:27:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/doctena-techblog" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[My first year as CISO — GDPR, ISO27001 and more]]></title>
            <link>https://medium.com/doctena-techblog/my-first-year-as-ciso-gdpr-iso27001-and-more-3ba5c7e172c8?source=rss----7cc66ebb9393---4</link>
            <guid isPermaLink="false">https://medium.com/p/3ba5c7e172c8</guid>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[iso-27001]]></category>
            <category><![CDATA[gdpr]]></category>
            <category><![CDATA[ciso]]></category>
            <category><![CDATA[compliance]]></category>
            <dc:creator><![CDATA[Davy Cox]]></dc:creator>
            <pubDate>Thu, 07 Feb 2019 11:23:21 GMT</pubDate>
            <atom:updated>2019-02-09T07:23:34.966Z</atom:updated>
            <content:encoded><![CDATA[<h3>My first year as CISO — GDPR, ISO27001 and more</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/832/1*2ZdMx1Bj9l6CHKLzASlfAg.png" /><figcaption>Generated with wordart.com</figcaption></figure><p>After having done my masters in security (RSSI) in 2010 and having gained a lot of experience in IT and system infrastructure in the years following, I decided end 2017 that it was time to put all this experience to a better use. With this article I’d like to share some of my experiences during my first year as a CISO for a wildly popular online service, with the hope it will help some other (future) CISO’s out there to do their job. Doctena is a young inspiring company active in 6 different countries (Austria, Belgium, Germany, Luxembourg, Netherlands and Switzerland) and specializes in providing highly configurable online agendas for practitioners (Doctors, dentists, …) while at the same time offering the accompanying patient portal that allows anyone to quickly find a practitioner and book an appointment.</p><p>I will not go too much in detail, expecting you to know the basics of information security management, but instead I’ll put some focus on the less obvious things while at the same time trying to give an overview on what kept me busy as CISO during my first year on the job.</p><h3>1. GDPR</h3><p>The introduction of the new general data protection law was probably on the main agenda of most CISO’s in 2018. Having started only beginning 2018 as a CISO, my main challenge was to get the company compliant before May 25th when the new regulation would be enforced. Unfortunately at that time there were still a lot of uncertainties on what would be the final regulation. This meant that many questions resulted in multiple interpretations and vague answers even from our national supervisory authority, which did not make it easier. My key guideline for GDPR (still today), has been the very helpful website <a href="https://gdpr-info.eu/">gdpr-info.eu</a> which gives a good overview on the different requirements and recitals on the different articles. Pay attention if you take the German version because it is slightly different due to the fact that it extends the recently renewed Bundesdatenschutzgesetz (BDSG) with the EU-GDPR to take advantage of both sides (Germany already had a very strict data protection regulation, and like is possible for any other EU country, they are free to extend the general regulation as long as the basic rules keep applying)</p><h3>Roles and Sensitive data</h3><p>One of the elements I like most about the GDPR, is the fact that it forces all entities involved in the processing to think about who controls what, what happens with the data, and what type of processing is allowed for what purpose.</p><p>After spending some time to get to know the different types of data that were being processed, it quickly became apparent that the reason of visit indicated while taking an appointment and the optional personal notes from the patient/practitioner, were to be considered as sensitive data. Among other things, data categorized as sensitive data meant that we had to do a Data processing impact assessment (DPIA) for that data. This extra assessment forces you to think about, and document, the potential impact a data breach of this sensitive information could have for a given data subject, with the aim to push you to implement appropriate preventive measures. The documentation is required so you can later on proof that you took the appropriate steps to protect this data. In our case this exercise made us put some extra protection measures on some parts (like additional encryption on top of the already existing encryption at rest).</p><p>Doctena has always had a clear message to its customers and users that it is not interested in data mining or the generation of revenue out of the data collected by the platform (Yes companies like this still exist, I know it might shock some of you). This helped us a lot to be very transparant and clear in the definition of the different GDPR roles. But still then it is not as easy as it sounds.</p><p>In our case some of the personal data was controlled by the practitioner and some of it by Doctena, with some of it being processed on the same systems or partially being stored in a common databases. Even though this by itself is not a problem, it is important to clearly define who is controller or processor for what data. For the newbies in GDPR, the controller is the one defining the purpose of processing, while the processor is usually the subcontractor or the entity “processing” the data on behalf of the controller. Both have the responsibility to secure the data, but the controller defines what the processor is allowed to do with the data and for what purpose (which is then defined in the data processing agreement, which I’ll described later on).</p><p>For us defining the roles was relatively easy; because almost all data is under control of the practitioner, even if it is collected through our platform. Only a small part, which does not contain sensitive data, is under our control; namely the Doctena account. In the Doctena account we simply have a “user profile” (like name, email, phone etc), which allows us to make a “copied on behalf” of the patient to the practitioner on every new appointment that is made, so that the patient does not need to enter it again. Only after the copy from the Doctena account profile, the data is extended with the actual appointment information (sensitive data) and some other agenda specific information. From this moment on that data is controlled by the practitioner and Doctena is considered as a processor who can no longer decide what happens with the data. At the same time Doctena also becomes limited in what we can do to execute specific GDPR rights for the patient (like right of erasure, right to access, etc).</p><p>Knowing and understanding your role and responsibilities on the data might look daunting at first, but my experience is that once you manage to define the different roles, everything becomes a lot easier. Always try to put yourself in the data subject’s shoes, and think who would they expect to be in control of the data. The moment you start to deceive the data subject’s expectations to this principle, you better have a very good explanation.</p><h3>Data protection officer</h3><p>Due to the fact that we process sensitive personal data and process data on a large scale, the GDPR also required us to appoint a Data protection officer (DPO). This role acts as the main point of contact regarding data protection for supervisory authorities, employees and external data subjects (patients or doctors in our case). Because there should not be any conflict of interest on the person who takes this role within the company, my role as CISO prevented me from taking this position. One can not be responsible for deciding and implementing the security while at the same time being the critical judge on how it is implemented (which is the DPO’s main job).</p><p>But at the same time we also wanted to be as transparent as possible towards our customers and users, so we decided to hire two external DPO’s (one for the German speaking countries and one for the rest). An (external) DPO has several obligations to notify to the supervisory authorities during security breaches or when we do not follow the rules (even though we pay them for their services). Therefore taking an external DPO was an important decision for us that in the end gave a lot of confidence to our customers. Up to today, this decision has had many rewards because I found myself collaborating with other professionals that kept me up to date on all the regulations in case I had missed something and provided me with a strong legal background.</p><h3>Data processing agreement</h3><p>The part that probably took most of my time, was the putting in place of all the data processing agreements (DPA). These agreements contractually define (on top of main contract) all details on how two or more legal entities will process personal data, which type of personal data is concerned, what core GDPR terms/agreements apply and who is allowed to do what at which point during the life cycle of the main contract. For us there were two sides in this story; our own subcontractors (like is the case for most companies) and our customers (which only applies if you are in B2B).</p><p>Having started by identifying all subcontractors from the different legal entities of the company in the different countries where we are active, and after having signed several data processing agreement with some of the most important ones, I got a good overview on what were the key elements to be included in a good data processing agreement. To organize this for all our subcontractors, I made a simple Excel sheet which would later become my DPA register. This spreadsheet had one row per subcontractor and multiple columns containing the important elements that I wanted to be checked for every DPA. (Doctena entity, Legal name of subcontractor, DPA file location, DPO contact, Data storage location, Processing role, purpose of processing, type of data processed, end contract data return clause, security measures, liability clause, their subcontractors, notification requirements, …). This gave me a good overview and a quick reference to the different clauses in the original document, while keeping the signed DPA documents in a separate folder for when I needed them later on. I also ensured that I had the legal authority to sign all these agreements in the name of the company and it’s subsidiaries, to avoid having to loose time in the chain of command.</p><p>After just having started to handle our own subcontractor DPA’s, I started noticing that many of our own customers (the practitioners, for whom we were a subcontractor) also started sending me their own custom made DPA’s in different languages. I quickly realized I did not want to be reading and approving all of these individually. This is why I started working out a Doctena DPA template together with our DPO’s to ensure it contained all required elements, while at the same time satisfying 99% of our customer’s needs in all different countries. After translating this in the different languages, it was received as a great service by our customers, because they no longer had to pay their own lawyers to set this up.</p><p>Due to the requirement for controllers (the practitioner) to have a (digitally) singed DPA for all their subcontractors (Doctena), I put in place a workflow with an online signing platform that had our pre-signed contract template with the option for the practitioner to tick a checkbox for the applicable country and fill in some other custom fields. Once they signed this document, both the practitioner and myself receive a copy of the DPA for our records. This workflow worked like a charm and still does today!</p><h3>Privacy notice and consent</h3><p>From the patient’s point of view, there are two main ways data can flow into our systems. Either with an appointment taken directly at the practitioner, where the practitioner uses our agenda and is responsible to get the required consents and inform the patient on the processing and his rights, or by taking an appointment through one of our online services. For all data collection through our online services we were required to give the data subject a clear view on how their data would be processed, for what purpose and what rights they have according to the GDPR regulation.</p><p>An important part we had to change here was that the consent from the patient had to be collected before the actual storage of the data. This meant that we had to ensured nothing was sent to our systems before the user gave their consent. Next to that we also had to slightly modify the booking process to clearly inform the user about the fact that sensitive personal data would be processed by Doctena in the name of the practitioner. During the booking process the user also had to consent with the terms and conditions like was already the case before. But to avoid there were too many check boxes, and to keep the booking process as painless as possible, we extended our terms and conditions phrase with a more clear description to what is considered as being our core service in our terms and conditions. Because this was now considered as a contractual consent, we no longer had to trouble our users with asking additional individual consents. This you can obviously only do if this kind of processing is really essential to your service, which is the case for us. Our promise to the practitioner is that we reduce their no-shows, and therefore we need to use the email and sms notifications related to the appointment to remind people to show up. At the same time we also need to validate the identity of the patient during the booking proces using their mobile number (allowing the practitioner to be sure the booking is done by a real person). Some practitioners even charge patients that did not show up. Because these are considered as the core service which can not be opted out from, we advise people not use our service if this is a problem.</p><p>In our privacy notice which we made visible on every page, we also added what will happen with the data they enter into our systems (similar to DPA, but then in easier words for a patient), and we repeated the previously described differences in control between a Doctena account and the actual appointment data in more detail, so that this is also clear for the patient. As last we added a clear description of the different GDPR rights the patient has, and how it can enforce them with direct contacts to our different DPO’s and our Privacy Center (more on this later).</p><h3>Data processing register</h3><p>Another requirement from GDPR that took quite some work, was the conception of an internal data processing register that identifies all different personal data flows that exist within the company. This is for internal documentation only, but is there to show that you are aware of what is happening with personal data inside your system and why. For us this meant that we had to describe how our customer and patient data moves inside our systems, but also how personal data lives inside our CRM-, Support- and our marketing tools. Something that is important not to forget here, is the requirement to also document the processing of your own employee’s personal data (Payroll, HR, legal, …), and if applicable any third parties that also touch employee data (e.g. We have some countries with an external payroll service). Even unexpected things like the processing of external “temporary” personal data (like CV’s) is to be evaluated (as part of HR) in this exercise.</p><p>In the end we identified a bit more than 10 main data processing groups, and documented the following things: why the data is collected, how it is used, our role (controller, processor or both), which type of legal base applies to the processing (consent, contract, legal obligation, vital interests of data subject, public interest and legitimate interest), the way data subjects of that group can enforce their GDPR rights, the self assessed DPIA risks, the responsible DPOs, the related data processing agreements and the people responsible internally for the protection of that data.</p><p>This gives you a nice overview on what lives in your system whenever it is asked for by your supervisory authority. It also makes you feel better in control of your own data.</p><h3>Privacy center</h3><p>Due to the complexity of GDPR, we had many question coming from all directions. And because the regulation requires every company to react to data subject requests within a “reasonable time”, we interpreted this internally as one month, which became a hard deadline in which all requests had to be handled. In general most was handled within 5–10 days, but this one month was included in all communications towards the requester to avoid discussions later on. In order not to overload our support teams and to keep the overview on what has priority, I quickly saw the need to put in place a central point of entry where the most common questions would be replied to or where relevant information is collected in a structured way to do followup actions (Data removal, data access, …). This is where our <a href="https://privacy.doctena.com/">Doctena Privacy Center</a> came to live. Our privacy center is a fairly simple form based questionnaire, that changes the flow of questions depending on the choices that have been made. The form then automatically populates a spreadsheet on every new request for my personal followup and at the same time sends an email to our support teams which creates a ticket with the details to do the followup.</p><p>Due to the fact that we acquired several companies in the past years with each their own specific properties (and missing features like closing an account), I found this a great approach to generate clear tickets for our teams with which they could can then act accordingly without having to know too many details on the conditions and constraints.</p><h3>Internal compliance, training and awareness</h3><p>It is general knowledge that most data breaches (intentional or not) come from within the company. This is why one of the first things I did was to increase the awareness about the potential risks in our teams during general meetings and team events. I also added a small paragraph in our monthly team newsletter, which I knew many would read.</p><p>We already had trainings for all teams specific to their role, and all employees were also already forced to sign an NDA at the beginning of their employment, which I think is an important thing to have and document whenever you process sensitive data like we do. I extended this with a 3 page long security policy that included all the most important security measures I wanted everyone in the company to know and apply before going through our other specific policies and procedures. Regarding internal compliance, one thing worth mentioning is that you should also handle the consents on how you can use your employees data for marketing purposes. For this I put in place a simple online form where all employees had to give their consent on how and where the company can use their personal data (photo, name, public team page, corporate website, printed media, facebook, etc…).</p><p>Next to that, special focus was put on the support and development teams because I considered their jobs being the most prone to data breach risks. This special focus involved explaining common problems/situations and their potential outcomes with simple examples, while also giving a simplified education on the different GDPR terms so that they felt more at ease when asked for by a customer.</p><p>What I learned from this exercise is that people are often really simply unaware of some risks and it helps them understand why this is important for the company. It was also a quick win from my side because it did not take too much of my time.</p><h3>GDPR conclusion</h3><p>I often get the question if we are compliant with GDPR, and I think the honest answer is that it is an almost impossible state to obtain, but we are very close. With a company of +75 employees, active in 6 different countries and carrying the burden to maintain legacy software, while at the same time experiencing a massive growth, you will always have small details that are not 100% how they should be. I think it is the CISO’s job to identify the priorities and main risk areas to ensure the main objective of the GDPR is met; namely to protect the data subject’s personal data to the best of your capabilities and document these efforts accordingly.</p><h3>2. ISO27001</h3><p>At the beginning of 2018 when we started to prepare for the GDPR regulation, it became clear that there were many elements that overlapped with the requirements in the ISO27001 standard. For the newbies among you, ISO27001 is a widely accepted security standard that proposes methods on how to implement an information security management system (ISMS) within your company with the use of policies and procedures encompassing the important legal, physical and technical controls involved in an organisation’s information risk management process. Because there would be many advantages in having such a certification for our business, I took the challenge upon me to combine the GDPR preparations with putting in place an ISMS which is at the basis of the ISO27001 certification. In this chapter I’ll go over some of my experiences and some advice I can share.</p><h3>Don’t reinvent the wheel</h3><p>At the core of a good ISMS system you’ll find clear and simple policies and procedures that your colleagues can identify with, and more importantly, that they are willing to implement.</p><p>There are many service providers on the market that provide detailed and complex ISMS systems and methodologies which they are willing to implement for you for a hefty price without you having to do a thing. I think this approach has two main disadvantages. First, your colleagues will not be motivated to implement this, because it is being enforced on them rather than being developed together. And second, the resulting ISMS will most likely not accentuate the core business values of your company as well as they could, resulting in management seeing this more as a burden than something that works to their advantage.</p><p>Putting an ISMS in place is a tremendous job, and if you are in a situation like I was where you never did this before other than in theory, I would absolutely advise you to not try to do this on your own. I ended up finding a really good online service that offered templates that combined the GDPR and ISO27001 in around 50 documents with a methodology that made sense to me and allowed me to prioritize the GDPR requirements. I also found a local company with a lot of experience (also one of our DPO’s) that was willing to assist me in setting up the ISMS based on these templates. This prevented me from making common mistakes while at the same time keeping me the main implementer within the company.</p><p>One should also not make the same mistake as I did and put yourself a too hard deadline. I was convinced it would be possible to get us certified by the end of 2018, but reality turned out differently. It is for sure possible to do this in such a short time or even shorter, considering you can focus on only this or you have a bigger team to your disposal. But unfortunately I did not have that luxury, and had to share that precious time with the other obligations that came with the job. But I also found that taking your time for the certification has some advantages in the end. Something important that you should emphasize to management is that every effort you put in your ISMS, even in the beginning without being certified, will immediately improve your level of security. So even if you’re not certified, you already pick the fruits. Also it allows more time for the ISMS to grow naturally within the company as mentioned before, making it much more effective in the end.</p><p>One of the first tasks in setting up an ISMS is to clearly define the scope of your ISMS and have your management sign off on what are the core objectives they would like to obtain with the certification. Typically this would be something like “attract more business”, “ensure % up time of our services”, “reduce financial impact caused by incidents”, but this could also be something like “prepare for a potential acquisition” which would probably require a whole different approach/prioritization. And no, taking “better security” as an objective is not good enough. If you don’t know what you’re aiming for, you’ll always miss the target.</p><p>I also recommend not to aim to get the whole company certified. Instead try to identify the departments that are tightly involved in the business assets you are trying to defend as part of your objectives. In your scope definition you can even define parts of departments or only specific buildings/products where your ISMS applies. At the same time the scope also allows you to explicitly exclude specific parts that do not help with your objectives, or would be too costly in a first phase. The final definition of your scope and assets to protect will end up becoming you “statement of applicability”, which will be the first thing a certification auditor will pick up to evaluate your compliance.</p><h3>Risk assessment</h3><p>This was probably one of the most time consuming parts from the ISO27001 preparations. And in retrospect, I think the main mistake we took here was to directly start with a quantitative risk assessment (requires you to estimate financial asset values and their potential financial impacts during your risk estimations) rather than doing a qualitative risk assessment (numeric ranking from 0–1 for risk) which would have been much easier. But for some reason our local partner insisted on going for the quantitative approach.</p><p>We started our risk assessment by writing down our core business assets, processes, information components, ICT systems and relevant departments that were within the scope. This we put in a schema where we drew lines between them to indicate their dependencies (has impact on, depends on, requires, …). Each of these elements was then given a business value estimation, allowing us to identify the most important assets. Estimating a business value is really not easy to do, and too inaccurate in my opinion. This is why I recommend starting with a qualitative risk assessment, which will take you 1/10th of the time.</p><p>Once we had this part done, and knowing we had already implemented some of the policies and procedures from the standard, we had to get a good idea of our current compliance level with the standard. Our methodology to do this gap analysis, was to list all security measures from the standard, and to identify the following properties for each measure: Status (applicable, not applicable or mandatory), Current Implementation rate, remaining internal workload in days, remaining external workload in days (in case external services are required), Investment budget required on top of internal and external workload, life time in years for the measure, and the estimated yearly internal external and recurring workload to maintain the control in days. Knowing the average personnel costs per day, this gave us an annual estimated cost for the implementation of the different measures, and also how much of a gap we still had.</p><p>The next step was to find the most important threats, vulnerabilities and risks we were exposed to, which we did by creating several scenarios that identified the potential consequences from loss of confidentiality, integrity or availability on our most important assets.</p><p>Finally, putting this gap analysis and the identified risks next to each other, gave us a quantitative risk assessment. This meant that we could now say which risk had the highest financial impact (highest yearly loss expectancy) and what would be the cost to remediate these risks. This then resulted into a risk treatment plan that gave a prioritized overview on what was left to be done.</p><h3>ISO27001 conclusion</h3><p>Because we only started beginning 2018 and the ISO27001 certification was not a business priority, we did not go for the certification in the same year. But at least I knew we now had a good ISMS and security foundation, and I was proud to say that we already had several of the fundamentals in place for the moment we decided to go for the actual certification.</p><h3>3. Infrastructure</h3><p>One advantage I considered as a big help during my first year as CISO, was the fact that I was the main responsible and technical lead for the implementation of infrastructure and migration to the cloud during the year before. During that year I had tightly worked together with the different development teams and had to containerize (Docker) all the infrastructure as part of our more general disaster recovery plan. This gave me the advantage that I already knew what lived where and how it was implemented. Having also already been responsible for the security during that year, and having participated in several external security audits, I also already had a good idea on which parts were well secured, and which parts could use some reinforcements.</p><p>I can imagine that if you lack this pre-knowledge, it makes your job as a CISO much more difficult, because you depend on the information you get out of your colleagues from devops and the development teams.</p><h3>4. Security automation</h3><p>Putting together good policies and procedures as part of a your ISMS system is one thing, and knowing where your vulnerabilities are, is something else. But defending against vulnerabilities that you do not even know exist is the most difficult part of the job, because also for that you need to be prepared.</p><p>Since the beginning of Doctena, they had been doing yearly pentests by a specialized company to find vulnerabilities in their systems. Also every new acquisition went through the same process, which was a good thing. But with a team of +15 developers that inevitably will make mistakes that can lead to new security vulnerabilities (they are also just human), our CIO and myself considered that waiting for one year between each pentest was too much of a risk.</p><p>This is why we started to work together with a company that provided dynamic application security testing (DAST). Their solution also included the traditional pentests by a trained professional which they combine with the custom configuration of continuous monitoring tools on their side, which ensure that the level of security they evaluated, is maintained. This results in automated security scans that run 24/7, which automatically detect and notifies us about newly arising problems on our systems. The moment we deploy new code, our DAST system now was there to warn us, taking into account the latest best practices and attack vectors on the market. Shortly after that we also combined this with a similar technique called Static code security testing (SAST) which was offered as part of the general code quality provider we worked with. This allowed us to go one step further because it looks at the actual code to find potential security flaws or things like hard coded passwords etc.</p><p>Next to DAST and SAST, I consider the multiple development libraries/dependencies used in our system as another big security risk. Any of these externally maintained tools could potentially be compromised or intentionally have malicious code added, breaking your whole security. This is why I was happy to see the (free) introduction of automated security audits by github and npm during 2018, which is an important area I try to pay attention to. Also Dockerhub’s automated security audits based on the actual configuration of your containers is a big advantage.</p><h3>4. General conclusion</h3><p>I really loved the experience of my first year as a CISO for Doctena, and would definitely recommend anyone up for the challenge to go for it. And I feel more at ease now with all this in place to continue and keep our systems secure. It will not be easy, but let’s be honest, if you are a bit like me, then you know that easy is no fun.</p><p>I hope this article helps some of you to dare take the step to be at the center of making this world a bit more secure every day. It will always be a challenge, but a very interesting one, that I can guarantee!</p><p>Good luck!</p><p>Davy Cox</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ba5c7e172c8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/doctena-techblog/my-first-year-as-ciso-gdpr-iso27001-and-more-3ba5c7e172c8">My first year as CISO — GDPR, ISO27001 and more</a> was originally published in <a href="https://medium.com/doctena-techblog">Doctena TechBlog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>