<?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 Johan Sydseter on Medium]]></title>
        <description><![CDATA[Stories by Johan Sydseter on Medium]]></description>
        <link>https://medium.com/@sydseter?source=rss-6f15fd5e976f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*QW5WcvlGpKRcHmWy-fQuQQ@2x.jpeg</url>
            <title>Stories by Johan Sydseter on Medium</title>
            <link>https://medium.com/@sydseter?source=rss-6f15fd5e976f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 03:13:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sydseter/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[How do you get your dev team to shift left by themselves for real?]]></title>
            <link>https://medium.com/sydseter/how-do-you-get-your-dev-team-to-shift-left-by-themselves-for-real-8a5667336c3b?source=rss-6f15fd5e976f------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a5667336c3b</guid>
            <category><![CDATA[games]]></category>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[application-security]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Johan Sydseter]]></dc:creator>
            <pubDate>Wed, 08 Oct 2025 20:46:42 GMT</pubDate>
            <atom:updated>2025-10-08T20:51:16.397Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*6braV4eSPztvI00AFmkWzg@2x.jpeg" /></figure><blockquote>Shift-left doesn’t start with scanning the code for security vulnerabilities; it begins with designing it. Play yourself secure with OWASP Cornucopia Website Edition v2.2</blockquote><p>Too often the shift-left mantra consists of implementing AI code scanning and applying AI-powered security fixes for remediation. Also, don’t forget to implement the <a href="https://engineering.fb.com/2025/04/29/ai-research/autopatchbench-benchmark-ai-powered-security-fixes/">AI-powered benchmark for AI-Powered Security Fixes</a>]. We’re not telling you to stop using these tools, instead, we want to ask ourselves:</p><ul><li>What are we working on?</li><li>What can go wrong?</li><li>What are we going to do about it?</li><li>Did we do a good job?</li></ul><p>Source: <a href="https://github.com/adamshostack/4QuestionFrame">Shostack’s Four Question Frame for Threat Modeling</a></p><p>Secure design starts with understanding <strong>what we are working on</strong>, asking <strong>what can go wrong </strong>and <strong>what we are going to do about it</strong>. I’ll leave that to the AI-assistants you say?</p><p>Before you do, know that the “<a href="https://www.veracode.com/blog/ai-generated-code-security-risks/">2025 GenAI Code Security Report</a>” from Veracode shows that after a comprehensive analysis of over 100 large language models across 80 coding tasks spanning four programming languages and four critical vulnerability types, only 55% of AI-generated code was secure (AI-Generated Code: A Double-Edged Sword for Developers, 09.09.2025). We don’t doubt that, eventually, the machines will take over the world, but in the mean time, don’t forget to ask yourself <strong>what can go wrong.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*cpz7BnFGsKcpYMexUy7Q5Q@2x.jpeg" /></figure><p>And what does the industry standard for infosec management say about writing secure code?</p><p>If you happen to be ISO 27001 certified and are writing code, you should know that the control you have called: “<strong>ISO 27002: 8.28 Secure coding</strong>”, says that: “<em>Planning and prerequisites before coding should include: … g) secure design and architecture, including threat modelling</em>”.</p><p>But, how can you possible do that in an agile and fun way?</p><p>Visit <a href="https://copi.owasp.org/">copi.owasp.org</a> and play OWASP Cornucopia, Elevation of MLSec, Elevation of Privilege or OWASP Cumulus with your team.</p><p>Games aren’t just for fun, they can be serious tools too, and that is what we are doing with <a href="https://cornucopia.owasp.org/">OWASP Cornucopia</a>. We are making threat modeling for everyone, everywhere, and we have a special love for agile teams that want to do continuous threat modeling as part of their development sprints. Don’t believe us? See how long-time project contributor Max Alejandro Gómez Sánchez Vergaray has <a href="https://cornucopia.owasp.org/how-to-play#Gameplay-using-abuse-case-modelling-approach">created a video</a> to explain how he has trained hundreds of teams to use OWASP Cornucopia in abuse case modelling sessions at a major international bank. This approach has scaled to over two-thousand developers to date.</p><h3>OWASP Cornucopia Website Edition v2.2</h3><p>In our next version of OWASP Cornucopia Website App Edition version 2.2 we have a special treat for you. We have gathered together all our threat modeling expertise, created threat modeling scenarios for each card and analyzed which STRIDE categories each of these scenarios belong to. If you have bought a <a href="https://cornucopia.owasp.org/webshop">OWASP Cornucopia deck with QR codes</a> you can now give your team advice on threat scenarios, threat vectors, attack patterns, mitigation strategies and STRIDE when playing the game by letting them scan the QR codes on each card. Each scenario follows “<strong>Shostack’s Four Question Frame for Threat Modeling</strong>” making it easy for your security champions to come up with the threats and mitigations themselves.</p><p>In addition, we have added additional CAPECs that corresponds to each card and added references to the <a href="https://devguide.owasp.org/en/04-design/02-web-app-checklist/">OWASP Developer Guide’s Web Application Checklist</a> that will link your threat modeling to OWASP secure coding practices and the <a href="https://top10proactive.owasp.org/">OWASP Top 10 Proactive controls</a>, this, thanks to Jon Gadson from the OWASP Developer Guide project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*6QF4JqCX8G69PQfoWfKj-Q@2x.jpeg" /></figure><p>We are just getting started, in fact, this is just the first step. We will continue to bring threat modeling to everyone, everywhere, and will continue to do so in the time to come.</p><p>Next time we will also talk about the last question: “Did we do a good job?”</p><p>Why? Because we want the game to be used in iterative security processes that involves continually adapting security measures in cycles to identify, address, and reassess threats and vulnerabilities, making continuous improvements rather than a one-time fix.</p><p>Stay tuned.</p><h3>How to use OWASP Cornucopia cards together with the OWASP Cornucopia website</h3><p>A – Preparations</p><p>. A1. Obtain a deck, or print your own Cornucopia deck and separate/cut out the cards</p><p>. A2. Identify an application or application process to review; this might be a concept, design or an actual implementation</p><p>. A3. Create a data flow diagram, user stories, or other artefacts to help the review</p><p>. A4. This will help answer the question: “What are we working on”</p><p>. A5. Identify and invite a group of 3–6 architects, developers, testers and other business stakeholders together and sit around a table (try to include someone fairly familiar with application security)</p><p>. A6. Have some prizes to hand (gold stars, chocolate, pizza, beer or flowers depending upon your office culture). See our “Prizes and Swags” section for ideas.</p><p>B – Play</p><p>One suit – Cornucopia – acts as trumps. Aces are high (i.e. they beat Kings). It helps if there is someone dedicated to documenting the results who is not playing.</p><ul><li>B1. Remove the Jokers and a few low-score (2, 3, 4) cards from Cornucopia suit to ensure each player will have the same number of cards</li><li>B2. Shuffle the pack and deal all the cards</li><li>B3. To begin, choose a player randomly who will play the first card – they can play any card from their hand except from the trump suit – Cornucopia</li><li>B4. To play a card, each player must read it out aloud, and explain how (or not) the threat could apply (the player gets a point for attacks that work, and the group thinks it is an actionable bug) – don’t try to think of mitigations at this stage, and don’t exclude a threat just because it is believed it is already mitigated – someone record the card on the score sheet</li><li>B5. If a player get stuck, ask them to scan the QR code on the card to access the online card page and read the section called: ”<a href="https://cornucopia.owasp.org/cards/VE2#What-can-go-wrong?"><strong>What can go wrong?</strong></a>” or click the “more info” links if playing <a href="https://copi.owasp.org/"><strong>Copi</strong></a> (the online Cornucopia version) or just browse the card from the deck at cornucopia.owasp.org while playing</li><li>B6. Play clockwise, each person must play a card in the same way; if you have any card of the matching lead suit you must play one of those, otherwise they can play a card from any other suit. Only a higher card of the same suit, or the trump suit Cornucopia, wins the hand</li><li>B7. The person who wins the round, leads the next round (i.e. they play first), and thus defines the next lead suit</li><li>B8. Repeat until all the cards are played</li></ul><p>C – Scoring</p><p>The objective is to identify applicable threats, and win hands (rounds)</p><ul><li>C1. Score +1 for each card you can identify as a valid threat to the application under consideration</li><li>C2. Score +1 if you win a round</li><li>C3. Once all cards have been played, whoever has the most points, wins</li></ul><p>D – Closure</p><ul><li>D1. Review all the applicable threats and the matching security requirements.</li><li>D2. Ask the group: “What are we going to do about it?”. Use the QR codes on the physical cards or “more info” links if playing <a href="https://copi.owasp.org/"><strong>Copi</strong></a> and read the “<a href="https://cornucopia.owasp.org/cards/VE2#What-are-we-going-to-do-about-it?"><strong>What are we going to do about it?</strong></a>” section</li><li>D3. Create user stories, specifications and test cases as required for your development methodology and add them directly into your issue tracking software under the what you are working on</li></ul><p>Uncover the security flaws in your software’s design before the bad guys do it for you! Get your team together on a call or in a room and use OWASP Cornucopia Web &amp; Mobile, Elevation of Privilege or Elevation of MLSec and OWASP Cumulus to secure your AI models and Cloud infrastructure respectively and guide your threat modelling at <a href="http://copi.owasp.org/"><strong>copi.owasp.org</strong></a>, and if you visit our <a href="https://github.com/OWASP/cornucopia"><strong>code repository</strong></a> please give us a star ⭐️.</p><p><a href="https://owasp.org/"><strong>OWASP</strong></a> is a non-profit foundation that envisions a world with no more insecure software. Our mission is to be the global open community that powers secure software through education, tools, and collaboration. We maintain hundreds of open source projects, run industry-leading educational and training conferences, and meet through over 250 chapters worldwide.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a5667336c3b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sydseter/how-do-you-get-your-dev-team-to-shift-left-by-themselves-for-real-8a5667336c3b">How do you get your dev team to shift left by themselves for real?</a> was originally published in <a href="https://medium.com/sydseter">Sydseter</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OWASP® Cornucopia 2.0]]></title>
            <link>https://medium.com/sydseter/owasp-cornucopia-2-0-8460ebbd9a45?source=rss-6f15fd5e976f------2</link>
            <guid isPermaLink="false">https://medium.com/p/8460ebbd9a45</guid>
            <category><![CDATA[cornucopia]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[threat-modeling]]></category>
            <category><![CDATA[application-security]]></category>
            <category><![CDATA[owasp]]></category>
            <dc:creator><![CDATA[Johan Sydseter]]></dc:creator>
            <pubDate>Mon, 10 Jun 2024 12:36:19 GMT</pubDate>
            <atom:updated>2024-06-10T13:07:19.602Z</atom:updated>
            <content:encoded><![CDATA[<h4>I started out as a web designer 16 years ago and my first website got brutally hacked, not once, but twice. I learned the hard way about the importance of threat modeling and having backups.</h4><figure><img alt="OWASP Cornucopia 2.0" src="https://cdn-images-1.medium.com/max/1024/1*VXNR3OHdFyGj_PHY30ShEw.jpeg" /><figcaption><a href="https://github.com/OWASP/cornucopia/releases/tag/v2.0.0">OWASP</a>®<a href="https://github.com/OWASP/cornucopia/releases/tag/v2.0.0"> Cornucopia 2.0</a></figcaption></figure><p>Today, as one of the co-leaders for OWASP® Cornucopia together with Colin Watson and and Grant Ongers, I am very proud to share that we finally, with lots of help from contributors, supporters and backers and OWASPs hardworking employees are releasing OWASP® Cornucopia 2.0.</p><p>Why is is this important and why should you care about this? First of all, as Adam Shostack would put it..</p><blockquote>“you never are going to have a better time then when people are having fun and talking to you.”</blockquote><p>OWASP® Cornucopia is a threat modeling tool in the form of a card game to assist software development teams identify security requirements in Agile, conventional and formal development processes. It strive to be language, platform and technology-agnostic.</p><p>It’s one of the few tools that connects threat modeling with OWASP ASVS, MASVS, MASTG, SAFECode, SCP and CAPEC and helps to identify security requirements, come up with a security design and a threat model without any prior knowledge of any of this.</p><p>How? OWASP® Cornucopia is open, democratic and agile, and that’s why it works.</p><p>At Admincontrol, we had been struggling for quite a while to get all our teams to do regularly threat-modeling sessions. It’s not that we weren’t able to do them it’s more that we didn’t see <strong>active participation</strong> during our threat modeling sessions. Either I would be the only one talking<strong> </strong>or I would be the only one<strong> </strong>coming<strong> </strong>up<strong> </strong>with<strong> </strong>threats<strong> </strong>and mitigations<strong> </strong>during the threat modeling sessions.<br>The initiative<strong> </strong>always had to come from me. If I didn’t take the initiative for the sessions, they wouldn’t happen. But we thought that it’s not like everybody has the same experience and knowledge about threat modeling<strong>.<br></strong>Perhaps the teams lack training and knowledge about threat modeling? Perhaps it’s normal that not everybody can’t participate equally?<br>So we tried to increase<strong> </strong>and spread<strong> </strong>the<strong> </strong>knowledge<strong> </strong>about threat modeling, but no matter what we would do, it wouldn’t change the nature of the sessions.<br>We did <strong>presentations </strong>on threat modeling.<br>We <strong>trained </strong>security champions<strong> </strong>in doing threat modeling.<br>We attended a large amount of <strong>follow-up meetings </strong>and <strong>online sessions </strong>together with the teams.<br>We did threat-modeling on the<strong> weekly security forums</strong>.<br>We even submitted<strong> </strong>ISO 27001 ISMS<strong> </strong>security incidents<strong> </strong>on non-compliance<strong> </strong>to the project managers.</p><p>At a certain point I just had enough<strong>.</strong></p><p>I remember, I was in a session together with one of the teams and It was like I was watching myself from the outside of my body while I was talking, saying the exact same thing I had said 100 times before<strong> </strong>and I could see one of the poor people participating, falling asleep, while I was talking.</p><p>If you have<strong> </strong>people in the meeting falling asleep<strong>,</strong> then that is not their fault<strong>,</strong> doesn’t matter how little<strong> </strong>they may have slept<strong> </strong>the night before<strong> </strong>really, because if you have the people in your meeting engaged and in a dialog with you, then that won’t happen. So that was on me,<strong> </strong>I had fallen in the trap of starting lecturing the people in the sessions. If anybody here have kids<strong> </strong>you may have experienced<strong> </strong>that if you start lecturing them, they<strong> </strong>very<strong> </strong>rarely<strong> </strong>listen, but lecturing adults is not only stupid it’s also disrespectful<strong>.</strong> If you want engaging<strong> </strong>and meaningful<strong> </strong>conversations<strong> </strong>you need active participation<strong> </strong>from all parties.</p><p>So I wanted participation<strong> </strong>in the meetings. I wanted the teams to take<strong> </strong>the initiative<strong> </strong>and I wanted the people participating to learn<strong> </strong>something from them and take something with them back.</p><p>Now, after having used OWASP® Cornucopia for awhile, I can say that we have a lot more conversations during our threat modeling sessions then we used to. The teams themselves takes the initiative for threat modeling creates the threat models and come up with the threats that they need to mitigate. They take a lot more ownership, not only over the security requirement gathering and security design, but the functional testers have also started to do a lot more penetration testing. We are not that dependent any longer on having an external company doing penetration testing for us, and we are discovering more security issues earlier during development. thereby, reducing time to market and the number of defects found after the release.</p><p>From having these Cornucopia sessions we have learned that delegation of security requirement gathering, threat modeling and security planning is possible. The less we intervene, the better the overall quality of the sessions. As we are able to delegate the threat modeling to the teams we get an increased capacity for process improvement, facilitation, and we decrease the time-to-marked and number of production defects. From having these sessions we have also learned that everyone can actively participate regardless of their knowledge and experience, even the QA testers and project managers scores points and win rounds for threats in the game. And it can be fun too!</p><p>But what about the <a href="https://github.com/OWASP/cornucopia/releases/tag/v2.0.0">OWASP® Cornucopia 2.0 release</a>?</p><p>Firstly, the formerly called “Cornucopia — Ecommerce Website Edition” is now called “Cornucopia — Website App Edition”. This edition was originally created in August 2012, released as v1.0 in February 2013 and has previously undergone a number of minor updates/releases in the following ten years. This has been substantially updated in today’s release of v2.0, in which the most noticeable change has been to update the OWASP ASVS mapping from ASVS v3.0 to v4.0. Further work on the data and code to generate the files for the cards themselves, the cases and folded leaflet and the legacy guide document has been undertaken, and this code also generates cards/cases/leaflets in two physical sizes. The smaller is often referred to as “bridge-sized cards” and the larger as “Tarot-sized cards”. All these v2.0 files are immediately available in six languages (EN, ES, FR, NL, NO-NB and PT-BR) due to efforts of past and current volunteers.</p><figure><img alt="The new Website App Edition comes in two sizes: bridge and tarot" src="https://cdn-images-1.medium.com/max/1024/1*emZpLC9ki7S3mrGPPFYG5Q.jpeg" /><figcaption>The new Website App Edition comes in two sizes: bridge and tarot</figcaption></figure><p>Secondly, as a result of other significant effort, there is now a completely new edition for threat modelling mobile apps. This “Cornucopia — Mobile App Edition” is released as v1.0 and is mapped to the OWASP Mobile Application Security Verification Standard (MASVS v2.0) and OWASP Mobile Application Security Testing Guide (MASTG) v1.7, and is available, initially, in one language (EN), and in two physical sizes. Like the original, this completely new edition of Cornucopia also has six suits of 13 cards plus two jokers, with the suit names drawn from MASVS: Platform &amp; Code (PC), Authentication &amp; Authorization (AA), Network &amp; Storage (NS), Resilience (RS), Cryptography (CRM) and Cornucopia (COM).</p><figure><img alt="The new Cornucopia Mobile App Edition 1.0" src="https://cdn-images-1.medium.com/max/1024/1*u6Kl5GtpvcqOi9u_6h27bg.jpeg" /><figcaption>The new Cornucopia Mobile App Edition 1.0</figcaption></figure><p>Both releases also have newly updated case designs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sJ5obkY6_lwM-KPDWuEpyQ.jpeg" /><figcaption>Two new Cornucopia case designs</figcaption></figure><p>Finally, we are releasing a brand new website called “Copi”, available from <a href="https://copi.owasp.org/">https://copi.owasp.org</a> for online collaboration and gaming where you and your team can play both these games even if you are present in different locations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kuRorfZIm5piQ32gTihTWg.png" /><figcaption><a href="https://copi.owasp.org/">https://copi.owasp.org</a></figcaption></figure><p>You can download printable files from <a href="https://github.com/OWASP/cornucopia/releases/tag/v2.0.0">https://github.com/OWASP/cornucopia/releases/tag/v2.0.0</a></p><p>We thank everyone who has contributed to OWASP® Cornucopia over the years, without whom these latest releases would not have been possible.</p><p>For more information about OWASP® Cornucopia, please visit: <a href="https://cornucopia.owasp.org/">https://cornucopia.owasp.org/</a></p><p>Later this month OWASP® Cornucopia is taking part in the project showcase track at OWASP Global AppSec Lisbon 2024.</p><p><a href="https://owasp.org/">OWASP</a> is a non-profit foundation that envisions a world with no more insecure software. Our mission is to be the global open community that powers secure software through education, tools, and collaboration. We maintain hundreds of open source projects, run industry-leading educational and training conferences, and meet through over 250 chapters worldwide.</p><p><a href="https://owaspglobalappseclisbon2024.sched.com/event/83f2aca8fa276b458eb714cb3a8ad5e5">OWASP Global AppSec Lisbon 2024: OWASP Cornucopia</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8460ebbd9a45" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sydseter/owasp-cornucopia-2-0-8460ebbd9a45">OWASP® Cornucopia 2.0</a> was originally published in <a href="https://medium.com/sydseter">Sydseter</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cyber Security in the c-suite and board rooms — Sikkerhetsfestivalen 2022]]></title>
            <link>https://medium.com/sydseter/cyber-security-in-the-c-suite-and-board-rooms-sikkerhetsfestivalen-2022-ac76ec3ca2a4?source=rss-6f15fd5e976f------2</link>
            <guid isPermaLink="false">https://medium.com/p/ac76ec3ca2a4</guid>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Johan Sydseter]]></dc:creator>
            <pubDate>Tue, 30 Aug 2022 12:18:44 GMT</pubDate>
            <atom:updated>2022-08-30T14:52:03.017Z</atom:updated>
            <content:encoded><![CDATA[<h3>Cyber Security in the c-suite and board rooms — Sikkerhetsfestivalen 2022</h3><p><strong>Disclaimer</strong>: Freely reproduced from the panel on “Cyber Security in the c-suite and board rooms” on “Sikkerhetsfestivalen” 2022. The participants has not been able to review the opinions that was expressed at the panel and therefor might want to moderate themselves if they where asked to review them in written form. <strong>ref</strong>: <a href="https://sikkerhetsfestivalen.no/bidrag2022/silvija-seres">https://sikkerhetsfestivalen.no/bidrag2022/silvija-seres</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D4fuNBuYVVKx62OSY7AyEw.jpeg" /><figcaption>Cyber Security in the c-suite and board rooms — Sikkerhetsfestivalen 2022</figcaption></figure><p><strong>Led by</strong>: Dr. Silvija Seres<br><strong>Participants</strong>: <br>Ingeborg Øfsthus, CTO, Telenor Norge <br>Sofie Nystrøm, Director, NSM <br>Dr. Hugh Thompson, Managing Partner Crosspoint Capital and Program Chair for the RSA Conference</p><p><strong>Introduction by Dr. Silvija Seres</strong></p><p><em>We find security vulnerabilities everywhere in all devices, systems, and the challenges concerning managing the risk for addressing security vulnerabilities are growing. There has been an increase in risk, globally, concerning sustainability and cybersecurity that wasn’t there 10 years ago. How can we solve new problems and implement new solutions and innovations when humans doesn’t assess risk well enough?</em></p><p><em>We are the first generation that experienced industrial availability of microchips, AI and interconnected devices and systems (Internet). There is a need for being able to perceive new risk faster as the pace of emerging technologies continue to increase. As the price of food, energy and the risk to the environment and social sustainability are continuing to increase, how can we remain focused on solving our challenges within cybersecurity?</em></p><p><em>Cybersecurity is becoming a license to operates amongst investors and board members as we are seeing an increase awareness concerning security in the boards. An increase focus on transparency concerning sustainability and cybersecurity in the board rooms are on the rise. How do we regulate? how do we increase awareness? how do we ensure that the board rooms are informed and knowledgeable?</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y3DC4U0oGS_8ZJKbBqXKeA.jpeg" /><figcaption><strong>Dr</strong>. <strong>Hugh Thompson</strong></figcaption></figure><p><strong>Dr. Hugh Thompson: </strong><em>There is a huge lack of knowledge and understanding of cybersecurity in the boardrooms, but regulations has increased the urgency to focus on information and cybersecurity as a topic. The introduction of GDPR has made board members more aware of the importance of cybersecurity. As companies started to hire GDPR consultant in order to ensure they could become GDPR compliant, they also became aware that there is a cost associated with ensuring proper security and privacy. Secondly, worldwide cyberattacks like “WannaCry” made the boardrooms aware that there now was an increased probability and risk for security breaches and that anyone could be targeted. This has also helped raise new questions concerning emerging information gathering like machine learning and privacy that previously wasn’t raised. There is an increase in the need for quantifying risk concerning reputational damage and the loss of trust in relation to security breaches. Insurance is not a good analogy in this respect and the boards are currently lacking a framework for properly assessing the impact of the decisions they make concerning challenges related to cybersecurity and privacy.</em></p><p><strong>Dr. Silvija Seres</strong>: <em>Considering the technical language that security professionals use. Are we able to properly communicate the challenges to the leaders in the public sector? Do the public sector understand the challenge? What is the state of public readiness in respect to cybersecurity?</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OC8KTqBEb0M54AmjL4oB-w.jpeg" /><figcaption><strong>Sofie Nystrøm</strong></figcaption></figure><p><strong>Sofie Nystrøm: </strong><em>We in NSM are spending a lot of effort on talking to leaders within the public and private sector. In Norway, we haven’t really seen the true effect of the changes to the threat landscape that has appeared over the last years. In terms of readiness, there is a huge difference when compared to the US. We have been much slower to implement new measures here as compared to oversees. Threat actors are investing heavily in 0-days vulnerabilities and we are not doing enough in the public sector in order to mitigate these challenges. One of the most effective measures is to talk to top-management. Cybersecurity professionals are lacking the management skills to talk to the boards. We have a long way to go. There is a need to be able to quantify the risk in order to get the points across.</em></p><p><strong>Thompson</strong>: <em>Many of the people sitting on boards are exceptionally smart and intelligent. In order to get your message across, master the art of story telling. People think better in terms of stories and analogies. If you can communicate using analogies and stories to get your message across, you can come far in communicating the challenges.</em></p><p><strong>Silvija</strong>: <em>How is cybersecurity becoming a strategic topic for companies?</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jKxoDyehN-3neehOPF-PFg.jpeg" /><figcaption><strong>Ingeborg Øfsthus</strong></figcaption></figure><p><strong>Ingeborg Øfsthus</strong>: <em>IOT and new technologies comes with inherent risks that need to be taken into account when designing new solutions and there are challenges around addressing security for legacy systems, the language is complex, Telenor is operating in various markets and cultures around the world, Together with our partners and sister companies, Telenor has lots of experience building and delivering secure systems around the world and we have a good collaboration between the group and the local level in our organization. There used to be tension between project managers and the security experts in the local projects. Telenor has therefor created a security board where the CEO and managers from different parts of the company can raise questions and communicate freely. We regularly train and have a lot of practice in crisis management where cybersecurity is a part. We believe that when addressing cybersecurity, we need to think cross-borders, not only locally.</em></p><p><strong>Silvija</strong>: <em>2 years ago, the municipality of Toten was hacked. One of the sentences that was often heard when citizens and politicians was interviewed in the press afterwards was that they never thought this could happen in Toten. Did the hackers care? When we depend on our local geography, seeing that digital is borderless, how can we address the challenges of cybersecurity which are global in nature?</em></p><p><strong>Thompson</strong>: <em>There is an increased need for government to know how the suppliers secure themselves. The hackers doesn’t really care where and what they attack. The number of ransomware attacks have increased year over year so it’s not a country specific problem it’s a global problems.</em></p><p><strong>Silvija</strong>: <em>Norway is one of the countries with the most digitized infrastructure in the world. One of the watershed moments was when Norsk Hydro got hacked. Seeing that our hospitals are getting more and more digitized, do we really have to wait for the loss of life to be a fact before something gets done?</em></p><p><strong>Sofie</strong>: <em>Mostly we know what the vulnerabilities are. All we need to do is to fix them. The board very often believe that things are just fixed and do not see the technical challenges that cybersecurity professionals are facing. We are lacking the tools for fixing vulnerabilities in the public sector. The public sector needs a push towards implementing the basics.</em></p><p><strong>Silvija</strong>: <em>We are moving towards the digitalization of everything. We are laughing about metaverse today, but 5 years from now, when we all are in metaverse, we won’t be laughing. Can cybersecurity become a competitive advantage when working with partners?</em></p><p><strong>Ingeborg</strong>: <em>Yes we see this happen already. We need to think holistically. In the board rooms, sometimes, we have solutions that have many different parts and we need to include cybersecurity as an end-to-end strategy, you are only as strong as the weakest link and that is certainly true for cybersecurity and technology.</em></p><p><strong>Sofie</strong>: <em>Military and civilian entities within the public sector are operating 20–30 years in the past. Legacy debt are making it difficult to ensure that the general citizen is secure. We in NSM are trying to prevent fires in these public entities from exploding and some of them are already exploding as we are speaking. We are trying to prevent this from happening.</em></p><p><strong>Silvija</strong>: <em>Talent shortage is a challenge when recruiting, even with a great digital strategy, talent shortage is becoming a challenge. How do we address this?</em></p><p><strong>Thompson</strong>: Security challenges in legacy systems shows that paying <em>down technical debt also is a huge opportunity for reducing security risk. The move to cloud is in many cases causing companies to move the same issues they had locally to the cloud, Norway has an incredibly advantage regarding security knowledge because of the amount of security talent that exist in Norway. I believe this to be a strategic advantage in Norway.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac76ec3ca2a4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sydseter/cyber-security-in-the-c-suite-and-board-rooms-sikkerhetsfestivalen-2022-ac76ec3ca2a4">Cyber Security in the c-suite and board rooms — Sikkerhetsfestivalen 2022</a> was originally published in <a href="https://medium.com/sydseter">Sydseter</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Rotating OAuth2 client credentials on Pivotal Cloud Foundry.]]></title>
            <link>https://medium.com/sydseter/rotating-oauth2-client-credentials-on-pivotal-cloud-foundry-1efd2a99869b?source=rss-6f15fd5e976f------2</link>
            <guid isPermaLink="false">https://medium.com/p/1efd2a99869b</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[oauth]]></category>
            <category><![CDATA[pivotal-cloud-foundry]]></category>
            <category><![CDATA[information-technology]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Johan Sydseter]]></dc:creator>
            <pubDate>Wed, 27 Nov 2019 12:05:03 GMT</pubDate>
            <atom:updated>2019-11-27T12:05:03.249Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<p><em>One of the biggest challenges in regards to information security is passwords and client secrets that never gets rotated, Not true any longer for Pivotal Cloud Foundry.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gOTLWORIX3VoB0qvg2Nq0w.jpeg" /><figcaption>Attribution: <a href="https://en.wikipedia.org/wiki/Pivotal_Software">Pivotal Software</a></figcaption></figure><p>I recently talked to a security architect that told me about a project in a large bank he was involved in. He told me that one of the projects they were starting now was to manually rotate the credentials for all the 900 systems the bank was using. This was the first time they would be doing this even though the bank has been around for 30 years. Timeframe for the project? 1 year.</p><p>This illustrates everything that is wrong with the way we approach information security in today’s world. Frankly, if it takes 1 year to rotate the credentials for all the systems you have, then you don’t take information security seriously. I am not sure you should be allowed to do internet banking at all.</p><p>Pivotal Cloud Foundry recently released <a href="https://docs.pivotal.io/p-identity/1-10/release-notes.html">v1.10 of their Single-Sign-On service</a>.<br>One of the advantages of using Pivotal Cloud Foundry is the easy way you can automate the security configuration and deployment of your services. You need to have the SSO tile installed in order to follow the demonstration in this blog post. First download the <a href="https://github.com/pivotal-cf/identity-sample-apps/tree/spring-boot-2.1/client-credentials">Identity Sample App</a> for demonstration of the client credentials.</p><ol><li>Using the CF CLI, login and target the space where you’d like the sample app to reside.</li></ol><p>Using the plan created as part of the Prerequisites, create a service instance in your space if you have not done so already</p><pre>cf create-service p-identity &lt;plan-name&gt; sso-instance</pre><p>2. Instead of using your manifest.yml to bind to SSO, <a href="https://github.com/pivotal-cf/identity-sample-apps/tree/spring-boot-2.1/client-credentials">as outlined in the second step of setting up the sample app</a>, we will be binding our application using an extra bind step when deploying the application. The reason for this is that the environment variables you’re using will only apply for the first push of an application, not the first push after binding. That means once the app exists on the foundation, the env variables are no longer used. so after we have done the first cf push we will do cf bind to bind to SSO. This will allow us to rotate the OAuth2 client credentials after we have pushed the app whenever we want.</p><p>Create a bind_sso.json file like this:</p><pre>{<br> “grant_types”: [“client_credentials”],<br> “scopes”: [“uaa.resource”, “todo.read”, “todo.write”],<br> “authorities”: [“uaa.resource”, “todo.read”, “todo.write”],<br> “identity_providers”: [“todo”],<br> “resources”: {<br>   “todo.read”: “Read Objects”,<br>   “todo.write”: “Write Objects”<br> },<br> “access_token_lifetime”: 300<br>}</pre><p>3. Remove everything from the <a href="https://github.com/pivotal-cf/identity-sample-apps/blob/spring-boot-2.1/client-credentials/manifest.yml">manifest.yml</a> this is what you should have in the <a href="https://github.com/pivotal-cf/identity-sample-apps/blob/spring-boot-2.1/client-credentials/manifest.yml">manifest.yml</a>:</p><pre>---<br>applications:<br> - name: client-credentials-sample<br>   memory: 1G<br>   instances: 1<br>   path: build/libs/client-credentials.jar</pre><p>4. Follow <a href="https://github.com/pivotal-cf/identity-sample-apps/tree/spring-boot-2.1/client-credentials#step-4-deploy-sample-application-to-pivotal-cloud-foundry">step 4</a> in the README of the sample app, but after the sample app has been deployed, do this:</p><pre>cf bind-service client-credentials-sample sso-instance -c bind_sso.json</pre><p>The app should now be bound to the sso service with a set of client credentials which it can use to communicate with the <a href="https://github.com/pivotal-cf/identity-sample-apps/tree/spring-boot-2.1/resource-server">resource server application</a>. Set up the <a href="https://github.com/pivotal-cf/identity-sample-apps/tree/spring-boot-2.1/resource-server">resource server</a> to test that it is actually working.</p><p>The advantage of this approach is that when you want to rotate your OAuth2 client credentials you can do like this:</p><pre>cf unbind-service client-credentials-sample sso-instance</pre><pre>cf bind-service client-credentials-sample sso-instance -c bind_sso.json</pre><pre>Use &#39;cf restage client-credentials-sample&#39; to ensure your env variable changes take effect&#39;</pre><p>Doing this will ensure that you can automate the rotation of your client credentials. Pivotal Cloud Foundry use Envoy and Istio on the inside to improve it’s routing layer. This means that they also have a programmatic setup of RSA certificates which means you can secure the traffic between services using mTLS. <a href="https://content.pivotal.io/blog/pivotal-cloud-foundry-2-5-istio-envoy-integration-weighted-routing-multi-port">Read more about this here</a>. It makes the manual rotation of mTLS certificates a thing of the past.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1efd2a99869b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sydseter/rotating-oauth2-client-credentials-on-pivotal-cloud-foundry-1efd2a99869b">Rotating OAuth2 client credentials on Pivotal Cloud Foundry.</a> was originally published in <a href="https://medium.com/sydseter">Sydseter</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using mTLS to connect to S3 using Java AWS S3 SDK]]></title>
            <link>https://medium.com/sydseter/using-mtls-to-connect-to-s3-using-java-aws-s3-sdk-95c9c1351b5?source=rss-6f15fd5e976f------2</link>
            <guid isPermaLink="false">https://medium.com/p/95c9c1351b5</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[java]]></category>
            <category><![CDATA[nginx]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Johan Sydseter]]></dc:creator>
            <pubDate>Fri, 13 Sep 2019 15:54:40 GMT</pubDate>
            <atom:updated>2019-09-19T09:15:21.195Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<h3>Using mTLS to connect to S3 using Java or .NET AWS S3 SDK</h3><p><em>Here is how you setup an mTLS connection to Minio S3 using a TLS client certificate.</em></p><p>Even though AWS S3 doesn’t support mTLS out-of-the-box so you can still setup client certificate authentication when connecting to S3 over TLS if you have such a security requirement. If you use AWS S3 you will need to <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/access-control-block-public-access.html">block public access</a> to your account to make sure external client applications only can access your S3 accounts over certain IPs. For this example I will use Minio S3, a popular open-source object storage that is compatible with AWS S3. I will also use <a href="https://docs.nginx.com/nginx/admin-guide/security-controls/securing-http-traffic-upstream/">Nginx</a> as an edge proxy to terminate the mTLS connection, but you can use <a href="https://www.haproxy.com/de/blog/ssl-client-certificate-management-at-application-level/">HAProxy</a> or <a href="https://www.envoyproxy.io/docs/envoy/v1.5.0/intro/arch_overview/ssl#arch-overview-ssl-auth-filter">Envoy</a> as well if you like or have the know-how. You can also setup <a href="https://medium.com/@zhimin.wen/https-client-certificate-authentication-with-sidecar-9b07d82a6389">Nginx as a mTLS sidecar proxy</a> if this is a pattern that fits you better. The concept should be transferable.</p><p>If you are like me and just want to skip right to the code just grab <a href="https://github.com/sydseter/aws-s3-mtls-nginx-minio">my Java code</a> or <a href="https://github.com/sydseter/aws-s3-mtls-nginx-minio-net">.Net code</a> on Github and have a look.</p><p>First of all, why do you want to do this? The reason you want to use mTLS is to allow a much stronger security then any other authentication mechanisms can provide. A TLS client certificate is the only measure that fully guarantees confidentiality and integrity according to the <a href="https://whatis.techtarget.com/definition/Confidentiality-integrity-and-availability-CIA">CIA triad</a>. mTLS therefor allows you to transfer highly sensitive information over an insecure network connection. (see: fig.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FOtCBVBkRzYUBq-th_4fcg.png" /></figure><p>To generate your own certificates and private keys you can follow the <a href="https://fardog.io/blog/2017/12/30/client-side-certificate-authentication-with-nginx/">“Client-side certificate authentication with nginx</a>” guide. To create your Java identity and trust store you can follow the “<a href="https://www.naschenweng.info/2018/02/01/java-mutual-ssl-authentication-2-way-ssl-authentication/">Java mutual SSL authentication / 2-way SSL authentication</a>” guide. If you don’t bother with that and only are interested in the Java code, just look at my code example and use <a href="https://github.com/sydseter/aws-s3-mtls-nginx-minio/tree/master/certs">my generated certificates and trust stores</a> for your testing.</p><p>The first we will do is install Minio S3. Just head over to “<a href="https://docs.min.io/docs/minio-quickstart-guide.html">MinIO Quickstart Guide</a>” and you should be up and running within 5 minutes. Then follow the “<a href="https://www.devdungeon.com/content/nginx-tutorial#install_nginx">Dev Dungeon — Nginx Tutorial</a>” guide and install nginx.</p><p>Git clone my <a href="https://github.com/sydseter/aws-s3-mtls-nginx-minio">aws-s3-mtls-nginx-mini</a> repository if you are interested in the Java solution.</p><p>Git clonet my <a href="https://github.com/sydseter/aws-s3-mtls-nginx-minio-net">aws-s3-mtls-nginx-minio-net</a> repository if you are interested in the .NET solution</p><p>Follow the instructions under “<a href="https://github.com/sydseter/aws-s3-mtls-nginx-minio#setup-nginx-as-a-mtls-proxy">Setup NginX as a mTLS proxy</a>”. Change the <a href="https://github.com/sydseter/aws-s3-mtls-nginx-minio/blob/master/nginx/servers/minio">Nginx minio config file</a> so that it reflects the location of the certificates and certificate chain ca file that you find under <a href="https://github.com/sydseter/aws-s3-mtls-nginx-minio/tree/master/certs">my generated certificates and trust stores</a> or generate your own using the tutorials above. Once you have all that setup you should be able to run the mTLS JUnit tests that I have written.</p><p>What the Java code does is basically these lines of code:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/0c6337327ea21d6ea8ac4e271aa0df28/href">https://medium.com/media/0c6337327ea21d6ea8ac4e271aa0df28/href</a></iframe><p>What the .NET code does is basically these lines of code:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/19c8bb0b34022366445831146eb14d4c/href">https://medium.com/media/19c8bb0b34022366445831146eb14d4c/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=95c9c1351b5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sydseter/using-mtls-to-connect-to-s3-using-java-aws-s3-sdk-95c9c1351b5">Using mTLS to connect to S3 using Java AWS S3 SDK</a> was originally published in <a href="https://medium.com/sydseter">Sydseter</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GDPR compliant event sourcing
with HashiCorp Vault]]></title>
            <link>https://medium.com/sydseter/gdpr-compliant-event-sourcing-with-hashicorp-vault-f27011cac318?source=rss-6f15fd5e976f------2</link>
            <guid isPermaLink="false">https://medium.com/p/f27011cac318</guid>
            <category><![CDATA[event-sourcing]]></category>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[microservices]]></category>
            <dc:creator><![CDATA[Johan Sydseter]]></dc:creator>
            <pubDate>Sat, 07 Sep 2019 21:04:55 GMT</pubDate>
            <atom:updated>2019-11-11T09:58:02.257Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<p><em>Events are records from the past. In the same way, as we can not rewrite the history books, we can’t remove immutable events. How then do we design microservices using event sourcing In a way that is compliant with the GDPR article 17, “the right to be forgotten”, and enforce data retention policies according to article 5?</em></p><p><a href="https://www.hashicorp.com/resources/gdpr-compliant-event-sourcing-with-hashicorp-vault"><em>This article is a written version of the presentation I did for HashiConf EU 2019 with the same title.</em></a></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F_czdzNUZGFs%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D_czdzNUZGFs&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F_czdzNUZGFs%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/0c635f87525b73cde3316816754564d0/href">https://medium.com/media/0c635f87525b73cde3316816754564d0/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4kkwtmkq0oinUVvyYR6Kjw.png" /></figure><p>I have been a developer for some time, but I didn‘t understand what it meant “to be compliant” before the end of 2017 when the General Data Protection Regulations came into focus. That’s when I came to understand that we all, as European citizens, have the right to privacy and the right to data protection and that these are fundamental rights that we and our clients are legally obligated to follow.<br>GDPR is mainly a reiteration of the Data Protection Directive. What is new is that data protection now must be implemented by design and by default. So what does it mean to do “data protection by design and by default”?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j0mpmNp_ltgXjYUlgFktAw.png" /></figure><p>Data protection by design and by default is derived from two terms.<br>One is “Data protection” and the other is “Privacy by design and by default”.<br>Originally the European Commission used the term “Privacy by Design” and „Data Protection by Design“ to mean the same thing, but in order to make a separation between the right to privacy and the right to data protection, the terms “Data Protection by Design and by Default” was chosen. In this way, A distinction was made between the two fundamental European rights, on the one hand, “The Right to Privacy” and on the other “The Right to Data Protection“, but “Privacy by Design and by Default” is still recognized as what the European Commission calls “an essential component for fundamental privacy protection” and „privacy engineering“.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7t90k_nbt1RZYlHJK5YPRA.png" /></figure><p>„Privacy by Design“ is based on 7 foundational principles originally conceived by „Dr. Ann Cavoukian“ during the 90‘ when she was the „information and privacy commissioner for Ontario, Canada“. These 7 foundational principles are like a “manifesto” for “The General Data Protection Regulation” as they are the foundation for many of the articles. F.ex. for article 25 which is called „Data Protection by Design and by Default“</p><p>HashiCorp Vault is a tool that can help us to implement these principles. Especially in relation to data protection. F.ex: With HashiCorp Vault, you can ensure that private data only is exposed unencrypted after the user has been authenticated, authorized and audited for being allowed to decrypt the data. Which is a proactive approach to data protection as it assumes that the data can be stolen and protects the privacy of the data subject even if that were to happen. That also means that “by default” private data is inaccessible until proper trust has been established. Which is according to principle 2 in regards to “the default setting”.<br>HashiCorp Vault, therefore, helps us in implementing these principles, except perhaps for principle 6 in regards to „Visibility and Transparency“.<br>To ensure visibility and transparency when processing private data we need a way to keep track of changes to the private data as they happen over time. We should be able to see what operations are responsible for changing the private data and why.<br>A very interesting architectural pattern for achieving this is event sourcing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lKZJA5mkk_Kvmg2OAkJMWQ.png" /></figure><p>When using traditional SQL or NoSQL databases we can query an application’s state, and this answers many questions.<br>However there are times when we not only just want to see where we are, we also want to know how we got there.<br>Event Sourcing ensures that all changes to the application’s state are stored as a sequence of events.<br>Meaning, that instead of storing the result of the computation we instead store the series of transactions that in sum represent the result.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FTMD4L4J-UYMwVAjGP65UQ.png" /><figcaption>Early 19th-century German ledger. <a href="https://commons.wikimedia.org/w/index.php?title=User:RaphaelQS&amp;action=edit&amp;redlink=1">RaphaelQS</a> — Own work</figcaption></figure><p>Take as an example your bank account. Your bank account is not a secure box where you keep your money.<br>Your bank account is a principal book or computer file for recording and totaling economic transactions.<br>Each time you buy a t-shirt or take out cash from an ATM an event is registered as a transaction in your bank account, and based on the result of that transaction we get to know our balance which is the result of applying the sum of all transactions that has happened to your account.<br>Tracking our spending makes us capable of planning ahead to ensure we don’t spend more than we have, but what if someone has taken advantage and charged you unreasonably for a service?<br>Maintaining transaction logs makes sure everyone stays honest in regards to buying and selling as all transactions are transparently recorded.<br>So event sourcing can be a tool, not only for keeping track of state but also to ensure transparency and visibility into what is happening and what has happened to your private data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4kkwtmkq0oinUVvyYR6Kjw.png" /></figure><p>But events are records from the past. In the same way, as we can not rewrite the history books, we can’t remove immutable events either, but according to GDPR article 17, the data subject has “the right to be forgotten” so we need to have mechanisms for deleting the data subject’s personal information. At the same time according to article 5, private data should also not be kept around “for longer than what is necessary”.<br>So how then do we handle the “right to be forgotten” and “data retention” when the data is immutable, undeletable and spread around in logs, backups, and different microservices.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pAcXBO7jlpcNVcAFWHfaYQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fwdy6A0okyQupOZspkUAdw.png" /></figure><p>So to address these challenges we can apply a technique called crypto-trashing.<br>Crypto-trashing is a technique were we encrypt the data and once we want to remove that data, instead of deleting the data itself, we delete the encryption key. Once the encryption key is deleted, private data consumed by other services, saved to event stores, backups or logs will become unreadable. <br>So how can we use this technique for implementing GDPR compliance? According to GDPR, we need to implement the user’s „right to be forgotten“. At the same time private data should not be stored for longer then what the data subject has agreed to according to our privacy policy. So let’s say I create an encryption key specific for each individual data subject. I call this key the PIIRef key. Then I create a temporal encryption key that I will use during a specific data retention period. Then I will use double encryption and encrypt the private data first using the personal PIIRef key and then the temporal key. So when an individual, for some specific reason, asks to get their private data deleted, I delete the PIIRef key making the data unreadable. If the data retention period pass, I create a snapshot of the data and encrypt it with the key for the next retention period, then I delete the key for the previous retention period, making all private data events created during the previous retention period unreadable.</p><p>Let‘s have a look at how this works.</p><p>I have installed HashiCorp Vault and an event store from AxonIQ called Axon server and created a microservice for registering health treatment for elderly patients in need of medical assistance at a home for the elderly. From Axon server, I have a full overview of all events that is generated by the microservice. As you can see. The event store is completely empty so I will go ahead and register some health treatments for two patients living at the home.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WSB_CkmUNtTfnKvzP_XqPA.png" /></figure><p>So I will subscribe 10 mg of Brintellix to Jan Johansen as he had become increasingly depressed the last year and 20 mg to his brother Stig Johansen as he has been depressed for many years now. As you can see our event store has started to fill up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rfKxJ-tb7wO7M82jpES-aw.png" /></figure><p>To better see that the data has been encrypted, I have created an endpoint for viewing the encrypted data and another endpoint showing how the data looks when it is unencrypted.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HlcMhC3sZgyVg6Nbr4EtCQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cx2OOiLAfLxQ2WUz3bxFdg.png" /></figure><p>To encrypt the data we are using the Vault transit secret engine. The reason we are using this engine is for two reasons. Reason number 1, the vault transit secret engine exposes encryption as a service, meaning that it does the encryption and decryption for us without exposing the encryption key to the application. This means that even if an attacker were able to gain access to our service, he still wouldn‘t be able to decrypt the data as he wouldn‘t have access to the encryption key. The 2. reason is that the Vault transit secret engine supports key derivation, which allows the same key to be used for multiple purposes by deriving a new key based on a user-supplied context value. By making this context-specific for each person, I can encrypt and decrypt each data subject’s health treatments using a single encryption key. I then store this context value in a normal database. Now let’s say Jan‘s brother dies and his family requests the deletion of Stigs data. As I am using event sourcing I can‘t simply delete all his events. What if this data is being used for generating a report to the government that they need once a year. If I delete the data I might risk losing data needed for this report. Besides. Deleting data from the event store can be quite resource consuming, complicated to implement and risky in itself. And what about logs, backups, and copies of the data that has been spread to other microservices? So what I want to do instead is to delete the context value represented by the NINRef. So that is what I am going to do.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_Gsh7Eezp0tjl2Y3aWkWEw.png" /></figure><p>There, now, as you can see, the microservice only exposes Jan‘s health treatments and if I am going to the unencrypted data endpoint, I understand why as it is no longer possible to decrypt Stig‘s health treatments.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RIjcSJAARrmwRy6EIcw-sw.png" /><figcaption>Encrypted HTTP endpoint</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZqGbLnp0h5xoinUxGpURzg.png" /><figcaption>Unencrypted HTTP endpoint</figcaption></figure><p>So, in this way we have with a very simple operation made sure that Stig is deleted, but we can still use his data for our reports as the product data is still there and completely anonymous. I have also made sure that Stig not only is deleted for this microservice. Stig’s data is also removed from any other microservice and any logs or backups which have processed his data as well.<br>For data retention, I would apply the same technique, but I would make sure I create a snapshot for all the data using the retention key for the new period before deleting the old key.<br>Please keep in mind that you should encrypt the PIIRef and not share it with external consumers other than the internal services you have control over. The reason for this is that the PIIRef is itself a personal identifier, but it’s ok to leave it undeleted as long as you only are using it between your internal services, but if external services were to use it, they could theoretically use it to retrieve the sensitive information that you told the data subject that you had deleted. That could potentially lead to a very awkward situation. You should, therefore, consider encrypting the PIIRef with a table/column/field key and never share the PIIRef as I have done in the examples above meant for demonstration purposes. You should obviously never use the value of the PIIRef itself as the user derived context value either. The PIIRef should point to a user derived context value which is unique for each service that will be encrypting your data. You, therefore, need to create an encryption service responsible for encrypting and decrypting your data as a wrapper service around the HashiCorp Vault transit secret engine or possibly a Vault secret engine plugin.</p><p>There is one more thing. How do I ensure that the data that the data-controller have flagged as personal data really is encrypted, how do I test that the correct data is being encrypted and how can I prove to an auditor that this encryption is being applied in production?<br>To be able to do this we use JSON schemas for data flow validation. Using JSON schema draft version 7 we can specify which fields we want to encrypt.<br>So I have created a very small library that takes a JSON Schema, the context value used for key derivation encryption and the object that should be encrypted.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z3Z_uE6Lkp0z3QwpNXY2_g.png" /></figure><p>Here I have the JSON schema that is used for encrypting the health treatment. The library will use the “<strong>contentEncoding”</strong> and “<strong>contentMediaType”</strong> properties from the draft version 7 of the JSON Schema standard to specify which of the fields will be encrypted. The library will then validate that encryption is being correctly applied, log a warning if something is wrong and log an info entry if everything is ok. Based on the log output I can test the encryption, monitor how encryption is being applied and do a data flow analysis for auditing purposes.<br>So why am I using a JSON Schema for this, why am I not just validating the input with code?<br>I want to be able to model how the data structure is encrypted in a modeling software like f.ex Sparks and export that data model as a JSON schema directly from the modeling software and into the code so I can have complete traceability from the design phase until the schema is used in production as this enables me to design and review the encryption of personal data for my microservices. This also makes me able to make some assumptions based on the solution design so that I can ensure when doing the data flow analysis, that private data is encrypted and protected by design and by default using HashiCorp Vault.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f27011cac318" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sydseter/gdpr-compliant-event-sourcing-with-hashicorp-vault-f27011cac318">GDPR compliant event sourcing
with HashiCorp Vault</a> was originally published in <a href="https://medium.com/sydseter">Sydseter</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Continuous delivery for data protection by design — customer satisfaction and incident response…]]></title>
            <link>https://medium.com/sydseter/continuous-delivery-for-data-protection-by-design-customer-satisfaction-and-incident-response-97618a983f2a?source=rss-6f15fd5e976f------2</link>
            <guid isPermaLink="false">https://medium.com/p/97618a983f2a</guid>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[customer-service]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[continuous-delivery]]></category>
            <category><![CDATA[privacy]]></category>
            <dc:creator><![CDATA[Johan Sydseter]]></dc:creator>
            <pubDate>Tue, 04 Jun 2019 16:54:18 GMT</pubDate>
            <atom:updated>2019-09-19T09:35:23.694Z</atom:updated>
            <content:encoded><![CDATA[<h3>Continuous delivery for data protection by design and by default — customer satisfaction, microservices and incident response plans</h3><p><em>In </em><a href="https://medium.com/sydseter/continuous-delivering-microservices/home"><em>a series of articles</em></a><em>, I will present a way of continuously delivering software while protecting the privacy of natural persons by design and by default.</em></p><p>A good incident response plan is about more than just being compliant, it’s about customer and employee satisfaction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rw46inYpRGiF0velzEfvkA.jpeg" /><figcaption>Attribution: <a href="https://www.fiverr.com/mahnazyazdani?source=Order+page+seller+link">Mahnazy Azdani</a></figcaption></figure><h4>Complying with the regulation</h4><p>GDPR sets requirements in regards to notifying incidents and on the restoration of availability and access to personal data. article <a href="https://gdpr.eu/article-32-security-of-processing/"><em>32.1c</em></a><em>, </em><a href="https://gdpr.eu/article-33-notification-of-a-personal-data-breach/"><em>33 </em></a><em>and </em><a href="https://gdpr.eu/article-33-notification-of-a-personal-data-breach/"><em>34</em></a><em><br></em>In order to be able to meet these demands, the processor will need to instruct it’s employees in how to handle security and privacy related incidents in a way that complies with the regulation. <br>Conduct regular fire drills to prepare and educate your employees on what they should be doing during security or privacy breaches. The fire drill should identify improvements like possibilities for automation or gaps in the security of the system. You need to be able to verify that your organization communicates appropriately with data controllers and supervisory authorities.</p><h4>Empower your incident response team</h4><p>I worked as a support operator doing both 1., 2. and 3. line support for a couple of years. I was also the acting support manager for some time. What I noticed during my time doing support was that the lead-time on incidents relied mainly on 5 variables:</p><ul><li>The number of hand-overs before completion.</li><li>Not having a clear definition of what an incident is.</li><li>Lacking sufficient information about the incident.</li><li>Lacking clear service ownership.</li><li>Not enforcing concise and clear communication during the incident.</li></ul><p>Make sure you empower your incident response team and give them the tools and mandate they need in order to handle incident responses. What does that mean?<br>It means that they should be allowed to involve whoever they need in the organization given the nature, context, and criticality of the incident. If that means stopping the ongoing commitment of staff in other parts of the organization, so be it. Your incident response team need ownership over the incident. It’s your incident response team that is responsible for securing the ongoing communication, resolving and closing the incidents but do not forget to loop in your customer service and support desk as well. Establish a clear line between your incident response team and your customer service desk. Use a system like <a href="https://www.statuspage.io/">statuspage.io</a> to communicate with all relevant stakeholders and refer to your status page when you are communicating with customers, users, etc.. Make sure that your service desk knows what information is required for reporting an incident to your incident response team and that they know what an incident response is. Clear service ownership needs to be established for all systems running in production so that both system administrators and the development teams are committed to fixing incidents. The ownership can be shared, but in doing so, make sure there is a person responsible for answering the phone on behalf of the team with the service ownership of the application. Keep in mind that this requires that developers also need to answer the phone during a critical incident, so make sure the development team is on phone rotation as well. Both <a href="https://www.pagerduty.com/">PagerDuty </a>and <a href="https://freshdesk.com/">FreshWorks </a>has solutions for this. Which one you choose depends on what type of organization you are, but regardless of which solution, make sure anyone in the organization can be looped in if required. <a href="https://freshdesk.com/">FreshWorks</a> has an edge in that it is marketed as a support system, but you can use it for incident management as well.</p><h4>Applying “<a href="https://en.wikipedia.org/wiki/Force_multiplication">force multiplication</a>” to your incident response strategy</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*7HiM2-HV2nH61NyK2DZyQg.jpeg" /><figcaption><a href="https://commons.wikimedia.org/wiki/File:No_11_Fighter_Group%27s_Operations_Room,_Uxbridge_(1943)_(Art.IWM_ART_LD_4140).jpg">No 11 Fighter Group’s Operations Room, Uxbridge (1943) (Art.IWM ART LD 4140)</a></figcaption></figure><p>During the second world war, early tests of the British <a href="https://en.wikipedia.org/wiki/Chain_Home">Chain Home</a> system suggested that the slow flow of information from the CH radars and observers to the aircraft often caused them to miss their “bandits”. The solution, today known as the “<a href="https://en.wikipedia.org/wiki/Dowding_system">Dowding system</a>”, was to create a set of reporting chains applying filters in between to move the information from the various observation points to the pilots in their fighters. The Dowding system dramatically improved the speed and accuracy of the information that flowed to the pilots. During the second world war, the Dowding system maintained an average possibility for the pilots to intercept their target at over 75%, with several examples of 100% rates. In contrast, Luftwaffe fighters attempting to intercept raids had to randomly seek their targets and often returned home never having seen enemy aircraft. The result is what is now known as an example of “<a href="https://en.wikipedia.org/wiki/Force_multiplication">force multiplication</a>”; RAF fighters were as effective as two or more Luftwaffe fighters, greatly offsetting, or overturning, the disparity in actual numbers. ref: <a href="https://en.wikipedia.org/wiki/Battle_of_Britain#The_Dowding_system">https://en.wikipedia.org/wiki/Battle_of_Britain#The_Dowding_system</a></p><p>The example highlights the importance of having a clear communication chain with multiple filters aggregating the information from multiple sources and displaying that information coherently so that it can be interpreted by your operators. If you are maintaining microservices, having this central operation room where the operators can see what is happening to the system is mandatory in order to figure out what is going on and to take decisive action to mitigate the risk of security, privacy, and downtime incidents. This central reporting and monitoring system will enable you to apply “<a href="https://en.wikipedia.org/wiki/Force_multiplication">force multiplication</a>” in the continued operation of your system. When maintaining microservices having such a system is not only nice to have it&#39;s mandatory and required.</p><h4>Incident management and customer satisfaction</h4><p>The 72 hour response time mandated by GDPR should be possible to achieve for all organizations, but in order to build trust and show excellence and service mindedness when giving support, merely complying with the regulation is a poor solution for any processor that wants to have high customer retention. In fact, it’s during an incident, more than in any other context, that a processor will affect customer satisfaction for better or worse.<br>If you ever have experienced e.g. getting your flight canceled, then you know what I mean. Having your flight canceled, and the way the airliner dealt with the cancelation is something you remember. Whether the hostess smiled to you or not as you were entering the plane on your last flight, is something you probably have forgotten by now.</p><p>It’s therefore critical that you streamline your incident response plan. It’s not only about merely fulfilling the GDPR requirement, but it’s also about customer and employee satisfaction. Why employee satisfaction? Everyone doing a job, that wants to do their job well, wants to feel that they are making a difference. If all you care about is the bottom line, then you will probably fail in providing the culture for giving exceptional service. After all, it’s much cheaper to offshore your support, but when considering offshoring, have you ever stopped to really consider the impact that might have on your customer service? Do you think that it will help build your customer’s trust in you and improve your customer retention and add-on sales? If the answer is no, chances are that your business won’t be here 10 years from now. Offshoring your service desk means you have to increase the number of hand-overs. Due to the physical distance offshoring creates between your service desk, management- and your technical personnel, offshoring makes it difficult to provide sufficient information about the incident quickly to your service desk. The consequence is that the communication done from your service desk operators becomes much less transparent then what it could have been otherwise. This, in turn, decreases the trust in you as a company. Many support operators at offshoring facilities get a nickname so that their name becomes easier to pronounce and remember, but if your support operator has an Indian accent and bears the name Bob, chances are you won’t be perceived as particular honest and trustworthy by your customers and users. The trust and the honesty by which you are perceived indirectly affects the bottom line. This is unfortunate for you as it is the “companies that choose to be transparent under attack … that win customer loyalty through their sincerity, honesty, and openness.” (“<a href="https://www.amazon.com/Customer-Support-Handbook-Ultimate-Experience/dp/0615962017">The Customer Support Handbook</a>”, p.131)</p><p>From a customer service perspective, customer follow-ups are key in order to show that you sincerely care about the customer or user. What happens after you have reassigned the incidence to somebody else? Will the IT-department get back and inform the customer about what the problem was, thank them for their patience and reimburse them when necessary? Whether the customer or user “ends up feeling taken care of by the technician, y<em>ou’ll only find out if you check back in</em>. customers want you, their original ally, to follow up on such questions, not just somebody over in IT, not even if you know for a fact that the IT person is the best equipped to help.” (“<a href="https://www.amazon.es/Exceptional-Service-Profit-Five-Star-Organization/dp/0814415385">Exceptional Service, Exceptional Profit: The Secrets of Building a Five-Star Customer Service Organization</a>”, p. 32)</p><p>An incident response plan is mandatory in order to be able to react to security-related incidents in a timely manner. Eliminating hand-overs is key to maintaining a lean incident response plan. The danger is that any plan involving managing incidents tend to grow out of proportions to what it is meant to achieve as it often involves several departments within the organization. Make sure you empower your incident response team and that your customer service and support desk is sufficiently looped in.</p><p>I hope these articles have shown you a way of continuously delivering microservice while doing data protection by design and by default. There are much more I could have said, but I’ll end with this.</p><p>Protecting the privacy of your users and maintaining the security of your customers is more than just being GDPR compliant. It’s about customer retention, add-on sales, and user satisfaction. If your customers are processors or controllers, they will choose you based on your privacy and security policies not because they care about your security and privacy from day to day, no, they choose you because they know that it’s the way you treat their privacy and security and their user’s privacy and security that’s going to make a difference when shit really matters. When someone gets their identity stolen or their password exposed, that’s when it really matters that you continuously delivered data protection by design and by default.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=97618a983f2a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sydseter/continuous-delivery-for-data-protection-by-design-customer-satisfaction-and-incident-response-97618a983f2a">Continuous delivery for data protection by design — customer satisfaction and incident response…</a> was originally published in <a href="https://medium.com/sydseter">Sydseter</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Continuous delivery for data protection by design and by default — Security and privacy reviews]]></title>
            <link>https://medium.com/sydseter/continuous-delivery-for-data-protection-by-design-and-by-default-security-and-privacy-reviews-a543643814bb?source=rss-6f15fd5e976f------2</link>
            <guid isPermaLink="false">https://medium.com/p/a543643814bb</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[continuous-delivery]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[privacy]]></category>
            <dc:creator><![CDATA[Johan Sydseter]]></dc:creator>
            <pubDate>Mon, 03 Jun 2019 00:15:05 GMT</pubDate>
            <atom:updated>2019-06-04T19:41:09.370Z</atom:updated>
            <content:encoded><![CDATA[<h3>Continuous delivery for data protection by design and by default — Security and privacy reviews</h3><p><em>In </em><a href="https://medium.com/sydseter/continuous-delivering-microservices/home"><em>a series of articles</em></a><em>, I will present a way of continuously delivering software while protecting the privacy of natural persons by design and by default.</em></p><p>The supervisory authority is tasked with periodically reviewing the operation of the data controller. <a href="https://gdpr.eu/article-41-approved-code-of-conduct/">(article.41)</a><br>Don’t let the supervisory authority catch you off guard, conduct regular reviews for evaluating the system’s security and privacy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OOtznGggRFFhSmbwTMNAvA.jpeg" /><figcaption>Attribution: <a href="https://www.fiverr.com/mahnazyazdani?source=Order+page+seller+link">Mahnazy Azdani</a></figcaption></figure><p>The regulation states that “the controller and the processor shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk, including inter alia as appropriate:…a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures for ensuring the security of the processing.” <a href="https://gdpr.eu/article-32-security-of-processing/"><strong><em>article 32.1d</em></strong></a><strong><em> </em></strong>If the supervisory authority decides to audit your operations and find that your not reviewing the “effectiveness of technical and organisational measures for ensuring the security of the processing”, they may question your security and privacy practices and fine you appropriately. To avoid the risk of repercussions you should conduct your own security and privacy reviews.</p><h4>The tools and library review</h4><p>“The tools and libraries review” evaluates the effectiveness of your system for running “software composition analysis”. These systems tend to report a lot of false positives and unimportant findings. False positives and non-applicable findings need to be actively labeled as such to ensure that the SCA system stays relevant and are used and heeded during the development and testing processes, hence the review. According to Gartner, several vendors of AST systems have started to look into using AI to help their customers to avoid these false positives showing up during analysis. <a href="https://www.gartner.com/en/documents/3700418">Artificial Intelligence and Application Security Vendors: Marketing Hype or Genuine Hope?</a> You might have to rely on some manual processes if AI not is an option for you, you should, therefore, make sure that the SCA system is integrated into your software development cycle so that developers and testers can address false positives during the development phase instead of having these being reported after the release approval and thereby cause reduced visibility into the your “software composition analysis” findings. To read more about how the tools and library review is setup and conducted, please read my article on “<a href="https://medium.com/sydseter/continuous-delivery-for-data-protection-by-design-and-by-default-quality-assurance-and-approval-13e4c6f72ad2">Quality assurance and approval of tools and third party software</a>”.</p><h4>The security review</h4><p>“The security review” is needed in order to evaluate “the effectiveness of technical and organisational measures for ensuring the security of the processing”. <a href="https://gdpr.eu/article-32-security-of-processing/">article 32.1d</a><br>Reports from your <a href="https://en.wikipedia.org/wiki/Static_program_analysis">SAST</a>, <a href="https://en.wikipedia.org/wiki/Dynamic_Application_Security_Testing">DAST</a>, and <a href="https://www.veracode.com/security/interactive-application-security-testing-iast">IAST</a> efforts need to be reviewed. False positives and non-applicable findings need to be actively labeled as such to ensure that the security test systems stay relevant and are used and heeded during the development and testing cycles. Look into using AI to ascertain whether you can avoid false positives showing up during analysis and reporting. The security review should be integrated into the software development cycle to ensure it’s effectiveness. <br>As with the “The tools and libraries review”, create three documents. One page explaining the purpose behind doing the security review (the why). This is the document you show to your data controller, security advisors, and supervisory authorities. Secondly, create a document describing the step-by-step process including any checklists and routine descriptions (the recipe). This is the document the team will continuously update as their process changes and is used to learn new team members about the process. Then create an overview page where project management can read out the status of each individual review completed or in progress. Then finally, collect and archive all the reviews in a central repository for security and privacy reports according to your ISO 27001 certified ISMS. The security review needs to established guidelines for what should be scanned and when. The tools used for conducting <a href="https://en.wikipedia.org/wiki/Static_program_analysis">SAST</a>, <a href="https://en.wikipedia.org/wiki/Dynamic_Application_Security_Testing">DAST</a>, and <a href="https://www.veracode.com/security/interactive-application-security-testing-iast">IAST</a> need to be documented together with any manual procedures that need to be done for conducting the review. <a href="https://en.wikipedia.org/wiki/Static_program_analysis">SAST</a>, <a href="https://en.wikipedia.org/wiki/Dynamic_Application_Security_Testing">DAST</a>, and <a href="https://www.veracode.com/security/interactive-application-security-testing-iast">IAST</a> tools are still considered to be a black art for many developers and testers so new employees need to receive proper training in order to be able to use the security tools properly. All security-related issues found during the review is assigned a work item and addressed immediately or on priority depending on their severity. Deviations found during the review, that also exists in the production environment, which involves personal data and that breaches the confidentiality, integrity, and availability of the system, must be reported to the data controller immediately and to the supervisory authority within 72 hours.</p><h4>The privacy review</h4><p>It is a recommended practice to do a manual security and privacy review to “ensure that any weaknesses that could lead to improper use or leakage of personal data are caught. For example, it may be difficult to identify patterns because data alone does not necessarily constitute personal data, but connections between different types of data can provide personal information. In order to ensure data protection, it is important to map where in the software personal data is stored. A review of the code should particularly examine where personal data is written. A common weakness is to write personal data in application logs with insufficient security.” (Norwegian Data Authority, <a href="https://www.datatilsynet.no/en/regulations-and-tools/guidelines/data-protection-by-design-and-by-default/?id=7734">Software development with Data Protection by Design and by Default — Coding</a>)<br>But relying on a fully manual process for conducting the security and privacy review makes microservice development and continuous delivery impossible. In order to ensure that as much as the process can be automated, Various systems used for information modeling and design needs to be integrated into the software development cycle to ensure that the information models designed by the architect and reviewed and approved by the data controller are implemented by design and by default into the system. There are a couple of ways this can be done. Data input can be validated by Schemas through APIs and at REST by using <a href="https://json-schema.org/">JSON Schemas</a> or <a href="https://www.w3schools.com/xml/schema_intro.asp">XSDs</a>. Schemas are much easier to acceptance test than code, and they can be exported directly from modeling solutions provided by companies like <a href="https://sparxsystems.com/">Sparx</a> to make sure the validations implemented at rest and in motion has been applied according to the design done by the information architect. Data protection by design and by default can then be guaranteed. There is also nothing stopping you from committing the schema directly to a central code repository where it automatically can be picked up by the build process and compiled into the code. MongoDB is NoSQL database vendor that has started with using JSON schemas for <a href="https://docs.mongodb.com/manual/core/schema-validation/">validating data before it’s stored at rest</a> in a similar way to how SQL schemas are enforced for traditional RDBMS. If schema validation errors are logged to a central log repository like <a href="https://www.elastic.co/webinars/introduction-elk-stack">ELK</a>, ongoing auditing and monitoring of the system can alert on breaches to the <a href="https://gdpr.eu/article-35-impact-assessment/">DPIA</a> and guarantee the ongoing privacy of the data subject, thereby making sure the system can be continuously delivered and protected by design and by default. Reviewing the privacy of the solution could be as simple as analyzing log messages stored in ElasticSearch. <br><a href="https://smartbear.com/product/ready-api/soapui/overview/#_ga=2.96353180.1854872575.1559468918-2137844579.1557410605">Smartbear</a> is a company that has a solution for acceptance testing APIs. Their solution can also be used to verify the <a href="https://support.smartbear.com/readyapi/docs/testing/environments/jdbc.html">database result of api calls</a> which means that the tester/developer can verify that data is appropriately encrypted and pseudonymized at REST and that only the data that has been approved for processing by the data controller through the <a href="https://gdpr.eu/article-35-impact-assessment/">DPIA</a>, is transferred and stored at rest. By combining the capability for exporting schemas from data modeling software with schema validation, logging and API- and database testing, the privacy review can be entirely automated given that some time is set aside for implementing the continuous delivery pipeline from design, development and testing to review and finally, delivery.</p><h4>Automating your privacy and security review process</h4><p>To ensure you always are prepared for an audit, you need to be sure you continuously conduct and automate as much of the review processes as possible. If you are developing microservices, you have to. <a href="https://en.wikipedia.org/wiki/Static_program_analysis">SAST</a>, <a href="https://en.wikipedia.org/wiki/Dynamic_Application_Security_Testing">DAST</a>, and <a href="https://www.veracode.com/security/interactive-application-security-testing-iast">IAST</a> systems used for security analysis and testing must be setup to automatically publish their reports to a central repository where they are made available to personnel conducting the privacy and security review. Make sure you have covered all the points mentioned in my article about <a href="https://medium.com/sydseter/continuous-delivery-for-data-protection-by-design-and-by-default-security-and-privacy-testing-e49969530567">Security and privacy testing</a>. The report from the privacy test suite is of particular interest; So is any external penetration test report conducted by an independent offensive security team. The regularity by which you should conduct these internal reviews depends on the degree of automation you are relying upon for doing regular patching and testing of the security and privacy of your system. Only a continuous and automated approach to testing, development, and reporting can ensure that the “Privacy and security reviews” can be automated. I can’t overstate the importance of automation in this regards, especially, if you are developing microservices. Microservice development depends on an “automate or die” approach to ensure continuous delivery. Automating your continuous testing, patching, reporting, and reviews are prerequisites for ensuring that your microservices are properly secured.<br>AI could help you leverage automation techniques to ensure the correctness of your reporting and the continuous security of your system. According to Gartner, several vendors of AST systems have started to look into using AI to help their customers with conducting application security testing and to sanitize security reports. <a href="https://www.gartner.com/en/documents/3700418">Artificial Intelligence and Application Security Vendors: Marketing Hype or Genuine Hope?</a></p><h4>To conclude</h4><p>The supervisory authority is tasked with periodically reviewing the operation of the data controller. <a href="https://gdpr.eu/article-41-approved-code-of-conduct/">(article.41)</a> If the supervisory authority decides to audit your operations and find that you’re not reviewing the “effectiveness of technical and organisational measures for ensuring the security of the processing”, they may question your security and privacy practices and fine you appropriately. To avoid the risk of repercussions you should conduct your own security and privacy reviews.<br>It is a recommended practice to do these reviews manually as “data alone does not necessarily constitute personal data, but connections between different types of data can provide personal information”, but relying on a fully manual process for conducting the security and privacy review makes microservice development and continuous delivery impossible. In order to ensure that as much as the process can be automated, various systems used for information modeling and design needs to be integrated into the software development cycle.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a543643814bb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sydseter/continuous-delivery-for-data-protection-by-design-and-by-default-security-and-privacy-reviews-a543643814bb">Continuous delivery for data protection by design and by default — Security and privacy reviews</a> was originally published in <a href="https://medium.com/sydseter">Sydseter</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Continuous delivery for data protection by design — Security and privacy testing microservices.]]></title>
            <link>https://medium.com/sydseter/continuous-delivery-for-data-protection-by-design-and-by-default-security-and-privacy-testing-e49969530567?source=rss-6f15fd5e976f------2</link>
            <guid isPermaLink="false">https://medium.com/p/e49969530567</guid>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[continuous-delivery]]></category>
            <dc:creator><![CDATA[Johan Sydseter]]></dc:creator>
            <pubDate>Sun, 02 Jun 2019 11:33:38 GMT</pubDate>
            <atom:updated>2019-06-05T04:44:04.534Z</atom:updated>
            <content:encoded><![CDATA[<h3>Continuous delivery for data protection by design and by default — Security and privacy testing your microservices</h3><p><em>In </em><a href="https://medium.com/sydseter/continuous-delivering-microservices/home"><em>a series of articles</em></a><em>, I will present a way of continuously delivering software while protecting the privacy of natural persons by design and by default.</em></p><p>Security is not something static that is defined once. Security is a dynamic property that changes over time. Regular testing is therefore vital in order to secure the processing of personal data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZeBNXPa2Qzm2uZPRhdznxA.jpeg" /><figcaption>Attribution: <a href="https://www.fiverr.com/mahnazyazdani?source=Order+page+seller+link">Mahnazy Azdani</a></figcaption></figure><p>The regulation states that “the controller and the processor shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk, including inter alia as appropriate:…a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures for ensuring the security of the processing.” <a href="https://gdpr.eu/article-32-security-of-processing/"><strong><em>article 32.1d</em></strong></a><em><br></em>What the regulation does not mention is what is meant by doing regular testing to ensure data protection is done by design and by default. The following points will be required in order to do regular security testing to ensure data protection is done by design and by default.</p><ol><li>Adopt a “Security by design and by default” approach to security during development and testing.</li><li>Automate all your security tests and run them against your CI environment.</li><li>Test your third party components as if they were your own.</li><li>Test your incident response procedures and review, and possibly test, all configuration changes for security concerns.</li><li>Load test the system to confirm a certain level of availability.</li><li>Test your privacy.</li></ol><h4>Adopt a “Security by design and by default” approach to security during development and testing.</h4><p>Security testing should never wait until the end. It should be the first thing you implement to ensure it’s applied by design and by default.<br>Each feature introduces a new attack vector for an attacker. Doing security testing as an integral part of the feature development is required in order to ensure that data protection is implemented by design and by default. As microservices are independent systems, security testing has to be done on a service by service basis to ensure proper coverage. Solutions like SoapUI from Smartbear that has <a href="https://support.smartbear.com/readyapi/docs/soapui/secure/scans/types/index.html">a number of security testing options</a> should be used during development and testing to ensure your systems uphold a certain level of security. The regulation doesn’t state how often this should be done only that it should be done (<a href="http://a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures for ensuring the security of the processing."><strong><em>article 32</em></strong></a><strong><em>.1d</em></strong>), but in order to be able to continuously deliver software and implement privacy by design and by default, security testing needs to be an integral part of the software development cycle.<br>You should, therefore, look for test tools that can do <a href="https://en.wikipedia.org/wiki/Static_program_analysis">SAST</a>, <a href="https://en.wikipedia.org/wiki/Dynamic_Application_Security_Testing">DAST</a>, and <a href="https://www.veracode.com/security/interactive-application-security-testing-iast">IAST </a>for analysis and testing. For a full overview of the major vendor in this space, read <a href="https://www.microfocus.com/en-us/assets/security/magic-quadrant-for-application-security-testing?utm_campaign=00134846">Gartner’s 2019 Magic Quadrant report for Application Security Testing</a>.<br>What I haven’t mentioned is hiring an external provider for offensive security testing to do an independent test of the system. It’s, of course, important to make sure the security can be independently verified, but it should only be an extra stamp of approval and not a measure for ensuring an appropriate level of security.</p><h4>Automate all your security tests and run them against your CI environment.</h4><p>Your security tests need to run automatically as you are developing in order to ensure continuous delivery. Microservices exponentially increase the testing effort making manual testing impossible when developing microservices. You, therefore, need to automate your security tests and run them continuously against your CI environment. I would advise you to have two CI environments. One for continuous integration and one for continuous testing. The continuous testing environment should receive a new update during the nightly build. After the nightly build has been run and the static code analysis has completed and has verified that the code upholds the quality enforced by your quality gate, deploy the new version of the software automatically to your continuous test environment and run regression tests, security scans, etc. against the new deployment to ensure that the security and functionality hasn’t degraded since yesterday. Given that the regression tests and security scans all is green, the testers can start verifying that the new functionality has been implemented and uphold a certain level of security. You could look into the possibility of using artificial intelligence in order to root out false positive when conducting application security testing. According to Gartner, several vendors of AST systems have started to look into using AI to help their customers with conducting application security testing. <a href="https://www.gartner.com/en/documents/3700418">Artificial Intelligence and Application Security Vendors: Marketing Hype or Genuine Hope?</a></p><h4>Test your third party components as if they were your own.</h4><p>As a data processor, according to<em> </em><a href="https://gdpr.eu/article-28-processor/"><strong><em>article 28.4</em></strong></a>, you’re responsible for maintaining the security of your third party components as they were your own. If the third party component is maintained by a data sub-processor and that processor not can guarantee for the security, then the main data processor is fully liable. This means that you should continuously monitor third party components for security vulnerabilities to make sure they are properly secured. As a minimum, you should do “software composition analysis” (SCA) as part of the continuous integration testing. Any vulnerability found can then immediately and automatically be patched thereby guaranteeing the continuous delivery of the system according to security by design and by default principles. Be aware that new patches introduce a security risk in the form of the possibility of trojan horses and other viruses so make sure you follow best practices for network segregation and security and that you can immediately react in case unauthorized network traffic gets reported through your monitoring system. You should conduct regular tools and library reviews to ensure that your third party components don’t use deprecated or insecure dependencies that may make your system vulnerable. See my article on “ <a href="https://medium.com/sydseter/continuous-delivery-for-data-protection-by-design-and-by-default-quality-assurance-and-approval-13e4c6f72ad2">Quality assurance and approval of tools and third party software</a>” to find out how this can be done.</p><h4>Test your incident response procedures and review, and possibly test, all configuration changes for security concerns.</h4><p>Your code is not the only thing you need to review and test. You need to review and test your configuration and procedures too. An important DevOps strategy is to treat your <a href="https://en.wikipedia.org/wiki/Infrastructure_as_code">infrastructure as code</a>. Through version control, authorization barriers and approval mechanisms like pull-requests, data protection principles like <a href="https://en.wikipedia.org/wiki/Security_management#Security_risk_management">security risk management</a> can be applied during the review process to ensure data protection is done by design and by default.</p><p>The regulation also sets down requirements for reporting security and privacy incidents. The project should conduct regular fire drills to prepare and educate employees on what they should be doing during security or a privacy breaches. The fire drill should identify improvements like possibilities for automation or gaps in the security of the system. You should be able to verify that your organization communicates appropriately with data controllers, supervisory authorities and data subjects according to <em>article </em><a href="https://gdpr.eu/article-33-notification-of-a-personal-data-breach/"><em>33</em></a><em> and </em><a href="https://gdpr.eu/article-34-communication-of-a-personal-data-breach/"><em>34</em></a>.</p><h4>Load test the system to confirm a certain level of availability.</h4><p>The three most important security principles to follow is what is known as the <a href="https://en.m.wikipedia.org/wiki/Information_security">CIA tria</a>d. The CIA triad is also mentioned several places in the European General Data Protection Regulation. e.g</p><p><em>(b) the ability to ensure the ongoing confidentiality, integrity, availability and resilience of processing systems and services;</em> <a href="http://www.privacy-regulation.eu/en/32.htm"><strong>article 32</strong></a></p><p>That the system has a certain degree of <strong>Availability </strong>means that the system<strong> </strong>ensures the readiness of the information it process when required. The required information must be available to authorized persons when they need it.</p><p>Load testing guarantees that the system upholds a certain level of availability according to the processing load that the system will need to cope with. There are a number of solutions out there that can be used for load testing. Choose a solution that can be setup for testing realistic scenarios that mimic the future production load. A big part of creating realistic scenarios is to calculate what the future load may be. A good place to start is to look through statistics that the business has been collecting up through the years. Do not fall in the trap of relying heavily on old system load statistics alone. System load statistics only shows you what the load was not what it will be. <br>Be aware that doing the calculations and finding the scenarios will take time and is cross-disciplinary work that requires input from business leaders, functional architects, UX designers, system administrators, security engineers, and developers. This is why load testing not should be done by the system administrator and test manager alone. Sadly, that’s how it’s traditionally done, but if you are serious about getting the numbers right, you better not follow the tradition of failing to predict the future load.</p><h4>Test your privacy.</h4><p>Testing your security is all well and good, but how do you test your privacy?<br>Testing your security means that you have ascertained that your system has a confirmed level of confidentiality and integrity. By load testing, you also verify what the system delivers in terms of availability, but what about privacy?<br> <strong>C</strong><a href="https://gdpr.eu/article-28-processor/"><strong>hapter III</strong></a> of the regulation states that the data subject has the right to <a href="https://gdpr.eu/article-15-right-of-access/"><strong>access</strong></a>, <a href="https://gdpr.eu/article-16-right-to-rectification/"><strong>rectification</strong></a>, <a href="https://gdpr.eu/article-17-right-to-be-forgotten/"><strong>erasure</strong></a>, <a href="https://gdpr.eu/article-18-right-to-restriction-of-processing/"><strong>restrict processing</strong></a>, <a href="https://gdpr.eu/article-19-notification-obligation/"><strong>notification</strong></a>, <a href="https://gdpr.eu/article-20-right-to-data-portability/"><strong>data portability</strong></a> and <a href="https://gdpr.eu/article-21-right-to-object/"><strong>objection</strong></a><strong> </strong>in relation to the processing of personal information. These rights need to be implemented as part of the system’s privacy functionality in order for the data controller to fulfill the regulation, but just because you are a data processor doesn’t mean you aren’t completely out of the woods. As a processor, you have to “assists the controller by appropriate technical and organisational measures, insofar as this is possible, for the fulfilment of the controller’s obligation to respond to requests for exercising the data subject’s rights laid down in <a href="https://gdpr.eu/tag/chapter-3/"><strong>Chapter III</strong></a>”. <a href="https://gdpr.eu/article-28-processor/"><strong><em>article 28.3e</em></strong></a><em><br></em>You should create a suite of privacy system test criterias that verify the requirements laid down by <a href="https://gdpr.eu/article-28-processor/"><strong>chapter III</strong></a><strong> </strong>of the regulation. Additionally, you should make sure you have put in place “a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures for ensuring the security of the processing.” <a href="http://a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures for ensuring the security of the processing."><strong><em>article 32</em></strong></a><strong><em>.1d</em></strong><em> <br></em>This also includes measure like <em>data minimisation, pseudonymising </em>and <em>encryption </em>of personal data. <a href="https://smartbear.com/product/ready-api/soapui/overview/#_ga=2.96353180.1854872575.1559468918-2137844579.1557410605">Smartbear</a> is a company that has a solution for acceptance testing APIs. Their solution can also be used to verify the <a href="https://support.smartbear.com/readyapi/docs/testing/environments/jdbc.html">database result of api calls</a> which means that the tester/developer can verify that data is appropriately encrypted and pseudonymized at REST and that only the data that has been approved for processing by the data controller through the <a href="https://gdpr.eu/article-35-impact-assessment/">DPIA</a>, is transferred and stored at rest. To minimize the amount of work on the testers it’s a smart move to implement schema validation through your APIs and at REST e.g <a href="https://json-schema.org/">JSON Schema</a> and <a href="https://www.w3schools.com/xml/schema_intro.asp">XSDs</a> validation. Data schemas are much easier to acceptancy test than code, and they can be exported from modeling solutions provided by companies like <a href="https://sparxsystems.com/">Sparx</a> to make sure the validations implemented at rest and in motion has been applied according to the design done by the information architect. In this way, data protection by design and by default can be guaranteed. Furthermore, if schema validation errors are logged to a central log repository like <a href="https://www.elastic.co/webinars/introduction-elk-stack">ELK</a>, ongoing auditing and monitoring of the system can alert on breaches to the <a href="https://gdpr.eu/article-35-impact-assessment/">DPIA</a> and guarantee the ongoing privacy of the data subject making sure the system can be continuously delivered and protected by design and by default.</p><h4>To conclude</h4><p>A “process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures for ensuring the security of the processing” (<a href="https://gdpr.eu/article-32-security-of-processing/"><strong><em>article 32.1d</em></strong></a><strong><em>)</em></strong><em> </em>is not only mandatory for complying with the European General Data Privacy Regulation, it’s also mandatory for the continuous delivery of microservices. Without a DevOps engineers mindset in regards to automation and a Privacy engineers perspective on data protection by design and by default, you will never be able to continuously deliver privacy-sensitive microservices to your users and customers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e49969530567" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sydseter/continuous-delivery-for-data-protection-by-design-and-by-default-security-and-privacy-testing-e49969530567">Continuous delivery for data protection by design — Security and privacy testing microservices.</a> was originally published in <a href="https://medium.com/sydseter">Sydseter</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is an Architect?]]></title>
            <link>https://medium.com/sydseter/what-is-an-architect-b734696d497f?source=rss-6f15fd5e976f------2</link>
            <guid isPermaLink="false">https://medium.com/p/b734696d497f</guid>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[information-architecture]]></category>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Johan Sydseter]]></dc:creator>
            <pubDate>Sat, 01 Jun 2019 04:43:22 GMT</pubDate>
            <atom:updated>2019-06-17T15:09:10.584Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<p>Have you ever dreamt of being an architect? We all have at some time or another, but what is an architect, and what does an architect do? This is what I will try to answer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XLkFtIkwUiCPFa9xQEdIAw.jpeg" /><figcaption>Attribution: <a href="https://www.flickr.com/photos/mariaeklind/">Maria Eklind</a></figcaption></figure><p>To know what an architect is, we need to know what an architect does. An architect is responsible for creating architecture, but what is architecture? Architecture comes from the Greek word <a href="https://en.wiktionary.org/wiki/%E1%BC%80%CF%81%CF%87%CE%B9%CF%84%CE%AD%CE%BA%CF%84%CF%89%CE%BD">ἀρχιτέκτων</a> (<em>arkhitekton)</em> which comes from the word “architect” put together by the two words <a href="https://en.wiktionary.org/wiki/%E1%BC%80%CF%81%CF%87%CE%B9-">ἀρχι-</a> “chief” and <a href="https://en.wiktionary.org/wiki/%CF%84%CE%AD%CE%BA%CF%84%CF%89%CE%BD">τέκτων</a> “creator”. So, architecture, according to the widest interpretation of the word, means “creation”. So you can say that architecture is what binds it all together, “the creation” and an architect, the chief creator. You may further expand on this idea and say that architecture is what binds humans, processes, and technology together. What do I mean by that? Well, Architecture gives our cultural environment structure. It’s how we have defined that our culture should work. In this way, you may say that we all participate in creating architecture and that an architect is nothing but a person that has this as his professional title. What is important to note is that by technology, I am not only referring to machines and software. Technology is the tools that we have used for executing our processes from the beginning of man until this day. A stone hammer is also technology. To most people, architecture is invisible. That’s why it’s so hard to define. It’s not the buildings themselves that represent the architecture, the buildings are just the output for what architecture really is, the ideas and concepts that hold the building together. The rest is just structural engineering.</p><p>So why do we really want to become architects? After all, we all take part in defining architecture. If I may speculate, I believe it’s because we understand that the persons that define the concepts and ideas for binding our culture together are the people that really hold the power over our lives. It’s not necessarily the domain of our politicians and CEOs, it’s the domain of the architects that comes up with the ideas and concepts that we will use from cradle to grave.</p><p>Architecture is more than just what we define as such. The word is just a concept we have chosen were ideas and concepts are needed in order to define which tools to use and how the processes for using these should be put to good use. When you need a person to do this job, you hire an architect, and in turn, this person may or may not call himself an architect. It all depends on the architect that decided what an architect really is and should be doing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b734696d497f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sydseter/what-is-an-architect-b734696d497f">What is an Architect?</a> was originally published in <a href="https://medium.com/sydseter">Sydseter</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>