<?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[Stories by Nicolas Ameye on Medium]]></title>
        <description><![CDATA[Stories by Nicolas Ameye on Medium]]></description>
        <link>https://medium.com/@nicolasameye?source=rss-2378ed2c7fde------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*j2npuG5l4j511L1VkI8Zpg.jpeg</url>
            <title>Stories by Nicolas Ameye on Medium</title>
            <link>https://medium.com/@nicolasameye?source=rss-2378ed2c7fde------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 22:02:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nicolasameye/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[GDPR — 50 days before the compliance deadline! Let’s answer to the most Frequently Asked Questions.]]></title>
            <link>https://medium.com/@nicolasameye/gdpr-50-days-before-the-compliance-deadline-lets-answer-to-the-most-frequently-asked-questions-6f1d7c5977d?source=rss-2378ed2c7fde------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f1d7c5977d</guid>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[gdpr]]></category>
            <category><![CDATA[computer-science]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Nicolas Ameye]]></dc:creator>
            <pubDate>Tue, 10 Apr 2018 13:32:53 GMT</pubDate>
            <atom:updated>2018-04-10T13:32:53.942Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/922/1*uh8UakUYntdZpoOvavS2VQ.png" /></figure><p>There are fewer than 50 days before the GDPR compliance deadline. By Friday 25 May 2018 organizations must be able to demonstrate that they are compliant or show evidence that they are working towards being able to satisfy the Articles that will govern data protection for the foreseeable future.</p><p><strong>The time has come to answer to a small FAQ.</strong></p><p><strong>Q: When does this law is applied?</strong></p><p>A: May 25th of 2018.</p><p><strong>Q: What is the General Data Protection Regulation (GDPR)?</strong></p><p>A: The GDPR updates and adds more requirements in regards to the 1995 data protection directive. GDPR is creating a harmonized and unified set of rules across the EU. The EU GDPR is a regulation, not a directive. A directive is a set of rules presented to the entire EU that can then be interpreted and implemented differently by each of the 28 countries within the union. The new regulation, on the other hand, creates a unified digital economy across the EU, and will be implemented uniformly by one supervisory authority across the entire union. The idea of GDPR is to provide individuals with full control over their sensitive personal data and boost Europe’s digital economy.</p><p><strong>Q: What is considered sensitive personal data?</strong></p><p>A: Under the GDPR, the scope of what is considered personal data has been expanded.</p><p>Under the current directive, each of the 28 countries developed their own interpretation of what constituted personal data. The EU GDPR enforces a strict and broad definition of personal data, referring to any information that could be used, on its own or in conjunction with other data, to identify an individual.</p><p>The scope of what personal data includes is broader. Under the GDPR, personal data includes anything that might identify an EU citizen, including IP addresses and cookie IDs. This may mean, for example, that even a phone number stored on its own without an associated name or address falls under EU GDPR guidelines and needs to be properly protected.</p><p><strong>Q: My company is outside the EU, does it apply to me?</strong></p><p>A: GDPR applies for all companies that process data on EU residents. With the GDPR, any company either based in the EU or dealing with data involving EU citizens or organizations are required to comply, no matter where the company is based or where data processing takes place.</p><p>Indeed, even though the regulation is being rolled out by the European Union, it has a global impact. Organizations based outside of the EU must comply if they handle, store, manage, or process EU citizens’ personal data. Any companies in the world who sell to European companies, or received data from EU citizens, for example will be affected.</p><p><strong>Q: Can I share personal data with companies/organizations outside the European Economic Area?</strong></p><p>A: Of course you can share personal data within the EEA respecting GDPR guidelines and the explicit consent of the private individual. Sharing personal data outside the EEA is only permitted if the country in question guarantees an adequate level of protection.</p><p><strong>Q: You just mentioned “explicit consent”. Consent? Should I have a consent? For what?</strong></p><p>A: Explicit consent is mandatory and needs to be freely given. Consent is one of the major developments of the GDPR. Silence or inactivity cannot be interpreted any longer as an acceptation. Companies will need to receive explicit consent from individuals (data subject) when collecting and/or processing their information. Consent of personal data must be freely given, specific, informed and unambiguous. Consent is not freely given if a person is unable to freely refuse consent without detriment. Likewise, companies will need to disclose the purpose of the data collection in clear and concise terms.</p><p><strong>Q: This seems like a lot of work… If I do not comply, what can happen to me?</strong></p><p>A: Non-compliance to GDPR results in big administrative fines. Under the new regime, the administrative fines have increased from a cap of about EUR 1 million to EUR 20 million — or up to 4% of the worldwide turnover (revenue) in the preceding financial year, whichever is greater. In most instances, the fines will be substantially lower, but for egregious conduct we can expect substantial fines (the GDPR mandates that fines must be effective, proportionate and dissuasive).</p><p><strong>Q: OK, so I will just say that I am compliant and that’s all?</strong></p><p>A: Accountability is key! GDPR is about demonstrating compliance. Organizations will not only be responsible for adhering to all the principles, they also must be able to demonstrate compliance with them. The GDPR has placed great emphasis on the accountability for data controllers to demonstrate data compliance. For most organizations this means they will have to elevate their internal privacy governance maturity, not only because of this new accountability principle, but also because the public opinion will expect it from modern organizations. They will be required to maintain certain documentation, conduct impact assessment reports for riskier processing and employ data protection practices by default — such as data minimization.</p><p><strong>Q: “Privacy By Default”? What is this notion of “Privacy By Default” that I keep hearing about?</strong></p><p>A: GDPR demands an integrated approach to Privacy By Default. The principle of “Privacy/data protection by default” means that, in the default setting, the user is already protected against privacy risks. When the system, process, service, etc. to be designed will include choices for the individual on how much personal data he shares with others, the default setting is the most privacy friendly one, so the one that says to not share any information at all. This data protection by default notion further includes data minimization principles.</p><p><strong>Q: Wait, “Privacy By Default”, I get it, but what about “Privacy By Design” then?</strong></p><p>A: GDPR also requires an integrated approach to Privacy By Design. The principle of “Privacy/data protection by design” is based on the insight that building in privacy features from the beginning of the service process is preferable over the attempt to adapt a product or service at a later stage. Or, in other words, this principle is based on the idea that new processes and systems must be designed from the beginning to comply with privacy laws. For example, they must secure data (encryption), restrict access, be capable of deleting or transferring data, reduce the risk of data breaches, etc.</p><p><strong>Q: This seems like a lot of security…</strong></p><p>A: You are right, GDPR requires that you take internal organizational measures and inform and raise awareness among your employees about the risks involved in collecting, using, storing, saving and destroying personal data. All these operations must also be carried out safely: you must therefore take appropriate technical and organizational measures.</p><p>The need to take proper information security measures to ensure the confidentiality, integrity, availability and resilience of processing systems and services has always been a part of privacy legislation. Nevertheless, the GDPR is bringing up some new security champions such as the pseudonymisation and encryption of personal data. These security measures are thought so valuable that they have been specifically mentioned in the text of the act. Furthermore, it is stressed that security should be based on a risk assessment, however, not of the risks the organization faces, but the risks for the rights and freedoms of natural persons, i.e. the risks that an individual’s privacy is compromised.</p><p>But GDPR is not only about security. Security is only one aspect of the GDPR. Yes, security is a GDPR concern on many levels and, yes, just as strategy, information management and a plan, cybersecurity and the prevention of data breaches is of the utmost importance.</p><p><strong>Q: What more is needed?</strong></p><p>A: Lots of things; DPO, data process inventory, breach notification protocols, DPIA…</p><p><strong>Q: A DPO? What is it?</strong></p><p>A: A DPO is a Data Protection Officer. Designation of a Data Protection Officer (DPO) is mandatory under the GDPR. Companies that process sensitive data on a large-scale will be required to appoint a data protection officer. The need to designate a Data Protection Officer (DPO) is a part of the Regulation, separate from a CISO. The role of the DPO is to ensure that his organization is in compliance with the GDPR, and, of course, any other applicable compliance requirements. Moreover, a DPO also has to manage the notifications and registrations to attain and maintain compliance. The DPO will be responsible for implementing the policies and procedures required to manage data outsourcing and processing activities, and should report directly to management.</p><p><strong>Q: And about the data process inventory? What do I need to do with that?</strong></p><p>A: An inventory of personal data processed needs to be maintained. An organization now must maintain a record of processing activities under its responsibility — or, in short, they must keep an inventory of all personal data processed. The minimum information about what should be in the inventory has been described and it goes beyond just knowing what data the organization processes. Also included should be, for example, the purposes of the processing, whether or not the personal data is exported and all third parties receiving the data.</p><p><strong>Q: For the breach notification. What will change under the new regulation?</strong></p><p>A: Breach notification protocols have been overhauled. Every organization that processes personal data needs to make sure that personal data is properly safeguarded against loss, theft, unauthorized access, etc. In other words: the security of the personal data is important. So important that the GDPR includes a personal data breach notification rule. This says that when a breach of security occurs, this breach should be reported to the supervisory authority within 72 hours. And if the security breach also is likely to result in a high privacy risk for individuals, then these individuals should also be informed of the breach.</p><p><strong>Q: You also mentioned DPIA… What is a DPIA?</strong></p><p>A DPIA is a Data Protection Impact Assessments. The GDPR introduces and requires Data Protection Impact Assessments (DPIA) as a means to identify high risks to the privacy rights of individuals when processing their personal data. When these are identified, the GDPR expects that an organization formulates measures to address these risks. This assessment should happen prior to the start of processing the personal data and should focus on topics like the systematic description of the processing activity and the necessity and proportionality of the operations.</p><p><strong>Q: OK, I think I get it. However, I hear a lot about the new rights of the data subject. What about those?</strong></p><p>A: Well, there are a lot of changes around the rights of the data subjects. For example, the right to access their personal data.</p><p>Built into the EU GDPR is a strong focus on citizen rights. Organizations will have to disclose the intended use and duration of storage of the data acquired, and re-solicit permissions each time a new use of the data is proposed.</p><p>EU citizens will have to explicitly opt in to the storage, use, and management of their personal data, and will have the right to access, amend, or request the deletion of, their personal data. Additionally, they will be able to object to certain types of processing — profiling for marketing purposes, for example.</p><p><strong>Q: I also heard about the “Right to be forgotten”. What does that stand for?</strong></p><p>A: The “Right to be forgotten” is one of the most useful changes for the average person managing their data protection risks. A person will be able to require their data to be deleted when there is no legitimate reason for an organization to retain it. Following this is requested the organization must also take appropriate steps to inform any third party that might have any links or copies of the data and request them to delete it.</p><p><strong>Q: Other data subject’s rights?</strong></p><p>A: Well, a few others, including the Right to Data portability. Data subjects will be allowed to: 1) request the transfer of data from one service provider to another; 2) situationally terminate any personal data upon request. The right to data portability. It basically says that an individual has the right to transport his personal data from one organization to the next — hence the word ‘portability’. The personal data must be provided to the individual in a structured, commonly used and machine-readable format. And the rules also stipulate that when technically feasible, organizations should facilitate electronic transfer of personal data from one to another, if the individual requests this.</p><p><em>My name is Nicolas Ameye. I am a PhD Candidate and Cloud Security researcher at the Université Libre de Bruxelles. I have two master degrees in Business and Management, one executive master in Innovation and Strategic Management, another one in Information Risk Management; and two Professional Education, one from the MIT on Systems Engineering, and another from the ULB on General Data Protection Regulation.</em></p><p><em>I am continuously looking to improve myself and learn something new every day. I love sharing what I learned to the people around me and take pleasure in the process of co-creation.</em></p><p><em>This </em><a href="https://medium.com/@nicolasameye/my-guidebook-to-cloud-security-a20b8144fc9"><em>blog</em></a><em> and </em><a href="https://docs.google.com/document/d/148ukD7GraenML7N5Lusr3cMcXvL7XHC2Lu8bQTCw66Q/edit?usp=sharing"><em>My Guidebook to Cloud Security</em></a><em> aim to create an engaged community of people looking to tackle to current Cyber Security challenges.</em></p><p><em>You have a Google account and want to be on top of GDPR and Cloud Security? Request access to </em><a href="https://docs.google.com/document/d/148ukD7GraenML7N5Lusr3cMcXvL7XHC2Lu8bQTCw66Q/edit?usp=sharing"><em>My Guidebook to Cloud Security</em></a><em>.</em></p><p><em>Follow me on </em><a href="https://www.linkedin.com/in/nicolasameye/"><em>LinkedIn</em></a><em>, </em><a href="https://www.instagram.com/nicolas_ameye/"><em>Instagram</em></a><strong><em>, </em></strong><a href="https://medium.com/@nicolasameye"><em>Medium</em></a><em> or </em><a href="https://www.facebook.com/OfficialNicolasAmeye/"><em>Facebook</em></a><em> to stay updated on my latest posts.</em></p><p><em>To follow my posts on GDPR, you can also register to the </em><a href="http://www.dpocircle.eu/"><em>DPOCircle</em></a><em> and the</em> <a href="https://gdprpro.com/"><em>GDPRpro</em></a><em> blog</em> <em>for free.</em></p><p><em>To get more information about me or my research interests, you can browse through my </em><a href="http://www.ameye.tech/"><em>personal website</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f1d7c5977d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Guidebook to Cloud Security]]></title>
            <link>https://medium.com/@nicolasameye/my-guidebook-to-cloud-security-a20b8144fc9?source=rss-2378ed2c7fde------2</link>
            <guid isPermaLink="false">https://medium.com/p/a20b8144fc9</guid>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[risk]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[information-technology]]></category>
            <category><![CDATA[gdpr]]></category>
            <dc:creator><![CDATA[Nicolas Ameye]]></dc:creator>
            <pubDate>Mon, 02 Apr 2018 15:15:29 GMT</pubDate>
            <atom:updated>2018-04-02T15:15:29.189Z</atom:updated>
            <content:encoded><![CDATA[<p>A year ago, I was sitting in the middle of this panel, just next to Julien Blanchez — then Global Security and Compliance Strategist at Google Cloud. We were discussing Cloud Computing security challenges and how to ensure the Information Security driven engineering of Cloud-based applications. An interesting but yet puzzling topic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*x_lRZS_bGXfq99orZByOTA.jpeg" /></figure><p>One year later… where am I?</p><p>Well, I have learned a lot. I have had the extraordinary opportunity of meeting and working with a lot of interesting people and experts from different industries.</p><p>I have had the opportunity to study Cloud Information Security in all its glory.</p><p>Besides having studied Cloud Computing security from the Information Risk Management perspective for three years, I had the chance to meet people who challenged me throughout the various other approaches of Cloud Computing security, such as its Architecture, its Infrastructure, its Programming and Processes.</p><p>To mention only a few…</p><p>The inputs provided by and the discussions with my colleagues from the “Laboratory of Web &amp; Information Technologies” — CoDE (belonging to the Université Libre de Bruxelles), allowed me to reconsider the<strong> architecture</strong> for Cloud-based applications.</p><p>My view of selecting and adopting security <strong>infrastructures</strong>, protocols and standards was also challenged throughout many discussions with colleagues from the “Cryptography and Computer Security Group” of the ULB — Qualsec, as well as with associates from the “UCL Crypto Group”. Through various debates, both of them allowed me to gain a stronger expertise, not only on cryptography, but also on an efficient implementation of cryptosystems. This view that I have been able to develop on Cloud security infrastructure has also only been possible thanks to discussions with my colleagues from the “Centre for Quantum Information and Communication” — QuIC, who are actively involved in quantum cryptography, or quantum algorithms.</p><p>The perspective that I had on secure <strong>programming</strong> has also been challenged throughout the past year. And again, in order to challenge a thought, what is best than a discussion and common work. My knowledge on programming technology used to secure cloud software has therefore been challenged through common works with the “Artificial Intelligence Laboratory” (COMO) and the “Software Languages Lab” (SOFT) of the Vrije Universiteit Brussel as well as with the “Louvain Verification Lab” (LVL).</p><p>The same goes for my understanding of the <strong>processes </strong>used to secure the Cloud. I also had the opportunity to challenge my view on the changing organizational and development processes used to secure Cloud-based applications through discussions with my colleagues from the “Research Group on Law Science Technology &amp; Society” from the VUB (LSTS) as well as from partners from Sirris, a collective centre for and by the technological industry.</p><p>What came out of those discussions? … Well, out of those last paragraphs, for sure the words “challenging” and “discussing”.</p><p>So… after three years gathering knowledge, grasping every little bit of information, learning and challenging Cloud security topics on all perspectives, it is time that, for me too, I start using the words “challenging” and “discussing”.</p><p>The security-driven engineering has always been a passion of mine… and I believe it is time to share that passion for those of you that might be interested.</p><p>I write this Guidebook to help the people out there who might be interested in Cloud Computing Information Security and Compliance. The insights that will be gathered in this Guidebook are coming from my expertise in Cyber Security as well as discussions I had in the past and will have in the future with experts and practitioners.</p><p>The guidebook will be constantly changing; it needs to change to stay on top. I will be posting the big updates on Medium, but it’s all created in an ever changing Google Document.</p><p>You have a Google account and want to learn more about Cloud Information Risk Security, as well as the General Data Protection Regulation? Request access to “<a href="https://docs.google.com/document/d/1A-T2YY6Ka9Z4OBtYZEWwCdgMuc_ZOXCmvcToAznOtmI">My Guidebook to Cloud Security</a>”. I’ll give you access to view and comment on my Guidebook. This way you can see my work in progress, you can even see me writing (Saturday mornings GMT+1 8–11 AM) and you can engage with me by leaving comments in the document.</p><p><em>My name is Nicolas Ameye. I am a PhD Candidate and Cloud Security researcher at the Université Libre de Bruxelles. I have a passion for security and continuous education. I have four master degrees: two in Business and Management, one in Innovation and another one in Information Risk Management. I have two Professional Education: one from the MIT on Systems Engineering, and another from the ULB on General Data Protection Regulation.</em></p><p><em>I am continuously looking to improve myself and learn something new every day. I love sharing what I learned to the people around me and take pleasure in the process of co-creation.</em></p><p><em>This blog and </em><a href="https://docs.google.com/document/d/148ukD7GraenML7N5Lusr3cMcXvL7XHC2Lu8bQTCw66Q/edit?usp=sharing"><em>My Guidebook to Cloud Security</em></a><em> aim to create an engaged community of people looking to tackle to current Cyber Security challenges.</em></p><p><em>You have a Google account and want to be on top of GDPR and Cloud Security? Request access to </em><a href="https://docs.google.com/document/d/148ukD7GraenML7N5Lusr3cMcXvL7XHC2Lu8bQTCw66Q/edit?usp=sharing"><em>My Guidebook to Cloud Security</em></a><em>.</em></p><p><em>Follow me on </em><a href="https://www.linkedin.com/in/nicolasameye/"><em>LinkedIn</em></a><em>, </em><a href="https://www.instagram.com/nicolas_ameye/"><em>Instagram</em></a><strong><em>, </em></strong><a href="https://medium.com/@nicolasameye"><em>Medium</em></a><em> or </em><a href="https://www.facebook.com/OfficialNicolasAmeye/"><em>Facebook</em></a><em> to stay updated on my latest posts.</em></p><p><em>To follow my posts on GDPR, you can also register to the </em><a href="http://www.dpocircle.eu/"><em>DPOCircle</em></a><em> and the </em><a href="https://gdprpro.com/"><em>GDPRpro</em></a><em> blog for free.</em></p><p><em>To get more information on my or my research interests, you can browse through my </em><a href="http://www.ameye.tech/"><em>personal website</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a20b8144fc9" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>