<?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 James Stewart on Medium]]></title>
        <description><![CDATA[Stories by James Stewart on Medium]]></description>
        <link>https://medium.com/@jystewart?source=rss-579b9ccb0cc0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*9LssACCP9TkJM8u7.jpg</url>
            <title>Stories by James Stewart on Medium</title>
            <link>https://medium.com/@jystewart?source=rss-579b9ccb0cc0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 19:32:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jystewart/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[Getting past the off-shoring debate]]></title>
            <link>https://medium.com/@jystewart/getting-past-off-shoring-132b74665498?source=rss-579b9ccb0cc0------2</link>
            <guid isPermaLink="false">https://medium.com/p/132b74665498</guid>
            <category><![CDATA[risk-management]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[James Stewart]]></dc:creator>
            <pubDate>Thu, 20 Jul 2017 09:53:22 GMT</pubDate>
            <atom:updated>2017-07-20T09:59:09.394Z</atom:updated>
            <content:encoded><![CDATA[<p>One of the factors many organisations (including governments) agonise over when deciding whether to use public cloud services is whether or not services and data can be stored “off shore”. It’s not a topic we tend to discuss very well.</p><p>“Off shore” usually means stored in data centres in other countries but can sometimes mean in facilities within the originating country but operated by foreign-owned companies.</p><p>For UK organisations looking at infrastructure as a service that conversation is dissipating now that the three biggest players all have UK data centres, but switching to UK data centres is really just dodging the issue rather than looking at how and why decisions are made.</p><p>It was great to hear Ian McCormack from NCSC addressing offshoring in his spot in the keynote at the AWS Public Sector Summit in DC recently.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F75Xkm0ZaSvw%3Fstart%3D355%26feature%3Doembed%26start%3D355&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D75Xkm0ZaSvw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F75Xkm0ZaSvw%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/69632bd9cdd154bba0e2c0dd0a1c3040/href">https://medium.com/media/69632bd9cdd154bba0e2c0dd0a1c3040/href</a></iframe><blockquote>“It’s often said to us that due to the global nature of a service it’s somehow inherently less secure than if exactly the same service was hosted on a datacentre in the UK. But actually that just doesn’t stand up to technical security outside of particular national security type applications.” — Ian McCormack, NCSC</blockquote><p>For the vast majority of applications from the vast majority of organisations, the physical location is not a factor in confidentiality or integrity. There may be compliance requirements that force decisions on you, or there may be performance reasons to choose particular geographies, but not security.</p><p>That said, the topic comes up so often that it seems worth breaking down some thoughts on how you might approach the issue if you want to really consider the risks. Which hosting companies you use, who they’re owned by, and where their various assets are hosted should be considered within your overall risk assessment.</p><p>A risk model is only as good as your understanding of the service it’s protecting. Before starting on anything you should make sure you have a solid grasp of the service expectations, what its impact on other services is, and so on. That will help you understand any trade-offs that need to be made, and also help understand whether any offshoring concerns might be coming from.</p><p>The following thoughts are based on a set of conversations over the past couple of years. They’re far from comprehensive, but I’m regularly in situations where I find people who don’t know where to start with breaking down these issues and it seemed worth sharing even some sketchy thoughts.</p><h3>The context, then the risks</h3><p>Before getting into detail on the particular risks, it’s worth first considering the scenarios where the location of data might be important.</p><p>Are you solely concerned about data security, or are your concerns about making sure your services keep working in the unlikely event that all network connections out of the UK fail?</p><p>If that unlikely event is a real consideration for you would you need to get your services back up and running immediately, or will backups that let you rebuild locally be sufficient? Most of the time it’s going to be more important that you’re running in multiple locations than whether one of those locations is in your home country.</p><p>Once you understand your context, you can go into the next level of detail. Roughly speaking there are three areas of risk that people are concerned about when they trust their services to a third party, regardless of the classification of that data.</p><ol><li>Confidentially and integrity risks if staff in those companies can access their data through their administrative roles</li><li>Confidentiality risks should a foreign government issue a legal order that the company hand over data from your service</li><li>Confidentiality, integrity or availability risks should a hostile state-sponsored organisation use access to the network or physical proximity to a data centre to attack your service</li></ol><p>There is also a further risk that we don’t often discuss, which is that the availability of services will be disrupted due to the complexity of international network routing.</p><p>It’s worth noting that I’m assuming you are using a robust cloud provider and are applying good practices to your cloud usage so that the chances of other customers affecting your services are very small.</p><h3>Staff accessing data</h3><p>The risks relating to staff at cloud companies accessing your data are similar whether your data is entirely contained within the UK or is stored elsewhere.</p><p>Before worrying about where the data is, you should be thinking about what impact comes with disclosure of the data. For much of what we do simply being careful about how we use a tool will minimise that impact. For example, if we’re using a project management tool we shouldn’t include personal data or credentials in what we store.</p><p>When you do have data that needs to be restricted then many infrastructure as a service providers will share information about the measures they take to make it very difficult for their staff to access customers’ data. Increasingly details of those measures are available publicly. Those measures apply whether the data is stored in the UK or outside it.</p><h3>Legal orders</h3><p>Non-UK ownership of companies, or non-UK residence of data centres is a reality of most modern internet services. There have been a number of legal cases around the world over the past few years beginning to test to what extent governments can compel companies to provide their customers’ data to law enforcement agencies or litigants in certain cases.</p><p>The full ramifications of those cases are still unclear and the legal situation will continue to vary significantly from jurisdiction to jurisdiction, but there are other things we should consider before getting into the detailed legal situation.</p><p>Once again, we need to understand the risk associated with a court granting access to the data we have in a service. That will largely depend on the way any data that is disclosed will be handled and what guarantees we have offered to our users. Access to a very specific record granted via a warrant and committing the accessing parties to hold the information carefully, is very different from a court allowing various parties to hold full copies of a database without protection.</p><p>We then need to consider the likelihood of such an order and the practicalities of fulfilling it. These cases are extremely rare and likely to remain so.</p><p>For governments, in the very rare circumstance where such situations did arise, most foreign governments are likely to use diplomatic channels to address requests of this sort that touch on government-owned data. Not to do so would risk a diplomatic incident and that is rarely worthwhile. Those diplomatic channels give us an opportunity to find other ways to address the situation.</p><p>Regardless of whether you’re a government, where your data is stored on third-parties’ servers that doesn’t mean it’s entirely out of your control. Just because your data rests on someone else’s server doesn’t mean you can’t encrypt it and store the keys elsewhere, or take other similar steps.</p><h3>Hostile interference</h3><p>There are always risks that hostile actors will want to interfere with your service, and that’s something that should be considered as part of the general threat modelling and risk assessment for a system regardless of where it’s hosted.</p><p>Infrastructure security is incredibly important but far too often people focus on that at the cost of application security, which is where the easiest to exploit vulnerabilities are usually found. Regardless of where an application is hosted you should be managing the application security appropriately. With that, you should be taking appropriate and proportionate steps to maintain the integrity of the data in your services. For example, when using large-scale public cloud services you should implement industry standard encryption of your network traffic, and thinking about how you’d detect tampering with your data at rest.</p><p>It is possible that certain types of attacks will be easier if data is in another country, particularly disruption to the availability of a service. If your service is genuinely critical, you should already have plans to make it resilient against network outages, for example by deploying software you run to multiple “regions” or by ensuring that your software-as-a-service providers do similarly.</p><p>It’s also worth noting that there are limits to what you can reasonably prepare for or protect against.</p><p>One example of where an organisation has thought ahead about that and set out to be realistic, is the <a href="https://www.gov.uk/government/uploads/system/uploads/attachment_data/file/251480/Government-Security-Classifications-April-2014.pdf">threat model for UK-OFFICIAL</a>. The UK government accepted the possibility that determined and highly capable foreign governments may be able to access some data and services:</p><blockquote>“This model does not imply that information within the OFFICAL tier will not be targeted by some sophisticated and determined threat actors (including Foreign Intelligence Services) who may deploy advanced capabilities. It may be. Rather, a risk based decision has been taken not to invest in controls to assure protection against those threats, i.e. proportionate not guaranteed protection.”</blockquote><h3>Conclusion</h3><p>For the vast majority of what any of us do, considerations about where to host your data and services come down to good architectural practices: are our services designed to be resilient, fault-tolerant and responsive enough to meet users’ expectations?</p><p>In some cases being comfortable hosting services off-shore brings very real advantages, not just because it gives us access to a wider market of suppliers but also because it allows for geographical resilience, or for better services to those based outside the UK.</p><p>The main thing that’s important whatever we’re doing is to maintain awareness of what we’re using and how. In a cloud-centric world that no longer means understanding every server, but having a good sense of where companies you’re dependent on are owned and operated and for high-availability services how their network connectivity is provided.</p><p><em>Originally published at </em><a href="https://jystewart.net/2017/07/20/getting-past-off-shoring/"><em>jystewart.net</em></a><em> on July 20, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=132b74665498" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A few thoughts from ITEM]]></title>
            <link>https://medium.com/@jystewart/a-few-thoughts-from-item-efd9eba51e0?source=rss-579b9ccb0cc0------2</link>
            <guid isPermaLink="false">https://medium.com/p/efd9eba51e0</guid>
            <category><![CDATA[speakers]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[ukraine]]></category>
            <dc:creator><![CDATA[James Stewart]]></dc:creator>
            <pubDate>Fri, 30 Jun 2017 11:04:09 GMT</pubDate>
            <atom:updated>2017-06-30T11:05:43.719Z</atom:updated>
            <content:encoded><![CDATA[<h3>A couple of weeks back I made my first visit to Ukraine, to keynote the (outdoor!) <a href="https://item.com.ua/">ITEM conference in Dnipro</a>.</h3><p>It was one of those trips where you don’t really feel like you see the place. Due to flight troubles (the culmination of many frustrations with Ukrainian Airlines) I arrived at my hotel in Dnipro at 3am, and departed at 5.30 the next morning.</p><p>That, combined with delivering two talks, hosting two Q&amp;A sessions, being interviewed for two different video shows, and being on a panel meant the whole day is a bit hazy in my memory, but a few things stand out.</p><h3>The hotel</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/0*q33HnaGcz19TH6IH." /></figure><p>With such a short visit, I didn’t get much time in the hotel, but it still stands out as one of the more distinctive I’ve visited. Set inside <a href="https://en.m.wikipedia.org/wiki/Menorah_center_(Dnipro)#">the Menorah Center</a>, the biggest multifunctional Jewish community center in Europe, the building was huge and rather imposing!</p><h3>My talks</h3><p>My keynote was about how to get started with digital transformation. I told some of the GDS story and highlighted some examples from elsewhere, but primarily exhorted the audience to start, and start small. Throughout my time in government, and in several consulting engagements since I’ve been frustrated by the assumption that to make big change you have to start out big. The mission should be bold, the vision should be big, but the first steps and initial team should be small.</p><p>I also gave a short talk exploring some of the themes about open source, open standards, and what I’ve learned about leadership from exploring those topics. There’s a separate blog post or two in that, which I should get to at some stage.</p><h3>The diversity panel</h3><p>I’d initially been inclined to turn down ITEM’s invitation as their website gave me the impression that they weren’t doing much to encourage diversity. I was delighted to be proven wrong.</p><p>While primarily white, the audience had more of a gender mix than I’d expected and there were a number of children present. There was also a wider range of speakers than the initial announcements had suggested and the organisers had laid on childcare — particularly important for a weekend event.</p><p>It was sobering to see the context in which that was happening during our panel. After the panelists had all said our bit, the moderator asked the audience to raise their hands if they thought lack of diversity was an issue in the Ukrainian IT industry. Not a single hand went up.</p><h3>Estonia</h3><p>I didn’t realise when I gave my customary shout-out to the Estonian government in my talk that the next speaker was from their <a href="https://e-resident.gov.ee/">E-Residency programme</a>.</p><p>The E-Residency team were sponsoring the event, which was the first time I’ve seen a government sponsor a tech event of this kind in another country. It was also striking how international the team representing e-residency were.</p><p>It seems Ukraine is a big source of e-residents, in part because running a business and moving money around in Estonia is much simpler than in Ukraine. It’s clear that Estonia’s reach in the region is significant, and their work remains fascinating to watch.</p><h3>Future of Ukrainian IT</h3><p>Several people approached me during the event to ask about how they win more outsourcing business. It was apparent that a lot of the IT sector in Ukraine is built around being an outsourcing provider, but that is being squeezed as cost of living goes up and western companies want to move away from traditional outsourcing.</p><p>While quite a few startups were present (and it’s difficult to draw inferences from such a short visit) there’s also not nearly such a large local economy as in India and so not quite the same opportunity to transition to providing products to a growing local market.</p><p>I encouraged those I spoke to at least move from talking “outsourcing” to a clearer presentation of whether they’re providing a product or a partnership, and to make those partnerships more agile. But there are no easy answers and with so many countries vying to rebuild their economies around tech, many of these companies could be facing a challenging transition.</p><h3>Going back, seeing more</h3><p>It’s been a real privilege over the last few months to get insights into digital and tech in such different contexts: Canada, Philippines, Australia and now Ukraine.</p><p>For Ukraine, 26 hours really isn’t long enough to see very much and I’m hoping there’ll be a chance to go back and see a bit more before long!</p><p><em>Originally published at </em><a href="https://jystewart.net/2017/06/30/a-few-thoughts-from-item/"><em>jystewart.net</em></a><em> on June 30, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=efd9eba51e0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Transition beyond GDPR compliance]]></title>
            <link>https://medium.com/@jystewart/transition-beyond-gdpr-compliance-719812ac47be?source=rss-579b9ccb0cc0------2</link>
            <guid isPermaLink="false">https://medium.com/p/719812ac47be</guid>
            <category><![CDATA[eu-gdpr]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[regulatory-compliance]]></category>
            <category><![CDATA[compliance]]></category>
            <dc:creator><![CDATA[James Stewart]]></dc:creator>
            <pubDate>Tue, 30 May 2017 17:52:09 GMT</pubDate>
            <atom:updated>2017-05-30T17:57:43.220Z</atom:updated>
            <content:encoded><![CDATA[<h3>360 days from now the <a href="https://gdpr-info.eu/">General Data Protection Regulation</a> (GDPR) comes into force. Anyone handling personal data from an EU citizen or subject (and <a href="https://iconewsblog.wordpress.com/2016/10/31/how-the-ico-will-be-supporting-the-implementation-of-the-gdpr/">the Information Commissioner has been clear we should assume that includes Brits regardless of what happens around EU exit</a>) will be held to new standards in how they obtain, store, process and dispose of that data.</h3><p>I was asked to speak about compliance at <a href="http://www.salford.ac.uk/onecpd">Salford Centre for Professional Development</a>‘s event on GDPR, and used it as an opportunity to try to encourage everyone to think beyond compliance.</p><p><a href="https://speakerdeck.com/jystewart/transition-to-gdpr-compliance">Slides are on speakerdeck</a>, but as usual they probably don’t make much sense out of context. So here’s a quick write-up to capture the gist.</p><h3>If compliance is our goal we’ll always be playing catch-up</h3><p>While organisations have been starting to wrap their heads around GDPR, the Conservative party have included a clause in their manifesto saying that if elected:</p><blockquote><em>“we will bring forward a new data protection law, fit for our new data age, to ensure the very best standards for the safe, flexible and dynamic use of data and enshrining our global leadership in the ethical and proportionate regulation of data”</em></blockquote><p>The GDPR has been seen as a once in a generation change in how data protection works, but it’s unlikely that will remain true. The ways in which we generate data, the ways in which it can be exploited, and the debate around what’s acceptable are moving quickly and that is finally part of the political debate.</p><p>When it comes to managing data, it’s all too common for compliance to become the end in itself.</p><p>Recent changes to information security risk management in government (eg. the new classification policy and the updated Security Policy Framework) were in part made to address the fact that meeting certain “baseline control set” requirements had taken the place of making sensible security decisions in context. At its worst that meant people had to bend the rules to respond to security incidents rapidly.</p><p>I also used the example of the Digital by Default Service Standard, noting that I rarely saw any correlation between the time people spent preparing for an assessment and the likelihood of success. The people who were successful were the ones who invested time in their users and service design, not preparing for assessment.</p><p>If organisations want to be on the front foot, they can’t allow current regulation to set their level of aspiration. Instead we have the transition to new regulation as a force for wider transformation.</p><h3>GDPR puts the focus on users. We should all be doing that already.</h3><p>GDPR gives individuals a lot of new rights, to be informed, to be able to restrict processing, to understand automated processes, and so on.</p><p>The way those rights will be interpreted in law is yet to be determined, but organisations that have really invested in understanding their users will be in a far better position to shape and defend their approach than those who allow corporate policy to ignore users.</p><p>And if we actually respect our users, get close to them and have a conversation with them we’re more likely to be able to find new opportunities and build their trust and loyalty.</p><p>We should try and go beyond GDPR’s expectation that policies will be explained in “plain English”. Or at least not fall into the trap that that solely means applying better writing to sign-up forms and privacy policies. I cited If’s <a href="https://newdigitalrights.projectsbyif.com/">“New Digital Rights”</a> work as an example of actually applying design thinking to the relationship with users around data.</p><h3>Understand our organisations</h3><p>There are all sorts of trade-offs that everyone’s going to have to face in meeting GDPR’s requirements. Hold on to data for potential future analysis, or dispose of it to reduce your liabilities? How much consent should you ask of your users? And so on.</p><p>It would be foolish to try and balance those trade-offs without understanding our organisations’ purpose, but all too often people are asked to do just that. People responsible for GDPR compliance need to push that conversation, to make sure that decisions are made in the context of overall value.</p><p>That also means finding ways to express that purpose and the way in which it’s being worked out right across the organisation. I cited the design principles we created at GDS as a tool for that. Principles like that give people a common frame of reference, and create a better environment for constructive challenge.</p><h3>Better cultures, better feedback loops</h3><p>Most organisations are going to struggle with GDPR compliance not because they’re doing anything nefarious, but because data has sprawled all over their organisations.</p><p>The reasons for that vary, but a common pattern is that people have one or two core tools that are theoretically their core data stores, but those stores are inflexible and so people create parallel systems (usually spreadsheets) in order to get their jobs done. Over time it gets less clear which the authoritative data set is, and more and more copies emerge.</p><p>Spreadsheets are an important tool and usually the easiest way to do some simple analysis, but they’re not the best choice for long term data storage. Their use is the sort of thing a purely compliance approach would try to stomp out, but doing that without an alternative won’t help.</p><p>Those charged with compliance should instead try to get to grips with the real causes of that information sprawl and help create feedback loops that limit it. Make sure that data stores have clear custodians who can adapt them to help people get their jobs done. Create channels where people can be open about the workarounds they’ve had to create and can have a grown up debate about the right way to manage that data in the future.</p><p>Not only will that focus reduce the risk that everyone works around compliance (cause they still need to do their jobs), there’s a really good chance that organisations will get more efficient if a culture is created that’s rich with feedback loops and includes empowered custodians.</p><h3>That all applies to security, too</h3><p>People are understandably worried about the risk of “data breaches” after a range of high profile incidents, and the GDPR increases the expectation that people will respond clearly and quickly.</p><p>For too many organisations, the biggest risk they have around data breaches is simply not knowing what data they hold, or where it is. Exactly the same principles around providing great tools and developing feedback loops are what’s needed there too.</p><p>There is an important place for discussions of specific technical security measures, like encryption, data minimisation, sharing, and so on. And it’s important that people understand the divisions in responsibility between their teams, software as a service providers and others. But none of that’s of much use unless we know the real data flows of the organisation.</p><p>Finding that out and improving it will work best in the context of recognising that people can be the strongest link in security, making sure that we have a security culture that recognises that most people are trying to do “the right thing” and supports them in doing it.</p><p>It also means practicing. My favourite clause in GDPR seems to recommend “game days” which seems like a very positive idea:</p><h3>Regulation isn’t aspiration</h3><p>Everyone will have to comply with GDPR, but if that’s all we focus on we’ll always be playing catch-up.</p><p>Educating staff about compliance may be important, but if that’s where it stops it’s unlikely to be transformative.</p><p>Instead, organisations should focus on understanding their users, providing the right data services for them, and building internal product ownership and feedback loops that make sure staff can contribute to improving data management over time.</p><p>There are a lot of hard challenges coming in working out what’s possible with data, with privacy and with consent. We need to free up organisations’ capacity to work on that, not on the endless cycles of compliance.</p><p><em>Originally published at </em><a href="https://jystewart.net/2017/05/30/transition-beyond-gdpr-compliance/"><em>jystewart.net</em></a><em> on May 30, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=719812ac47be" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What’s next?]]></title>
            <link>https://medium.com/@jystewart/whats-next-d6565e77a4b9?source=rss-579b9ccb0cc0------2</link>
            <guid isPermaLink="false">https://medium.com/p/d6565e77a4b9</guid>
            <category><![CDATA[consultancy]]></category>
            <category><![CDATA[freelancers]]></category>
            <category><![CDATA[digital]]></category>
            <dc:creator><![CDATA[James Stewart]]></dc:creator>
            <pubDate>Sat, 25 Mar 2017 12:14:00 GMT</pubDate>
            <atom:updated>2017-03-25T12:15:11.456Z</atom:updated>
            <content:encoded><![CDATA[<h3>It’s been nearly two months since I left GDS. It’s high time I talked a bit more about what’s next for me.</h3><p>I was really pleased with everything we got done in my last few weeks at GDS. Alongside the inevitable handover tasks, we made <a href="https://jystewart.net/2017/03/25/what-next/(https://governmenttechnology.blog.gov.uk/2017/01/20/the-internet-is-ok/)">a big announcement about the future of government networking</a>, began to share a draft policy about APIs and <a href="https://governmenttechnology.blog.gov.uk/2017/02/03/clarifying-our-cloud-first-commitment/">expanded the guidance around the “Cloud First” policy</a>. I remain very grateful to the many brilliant colleagues who helped get all that done.</p><p>For the most part I spent February trying to slow down. I finished some books, watched some films, and had coffee with lots of friends. But I can’t switch off completely, so I spent a very pleasant morning doing a little mentoring for <a href="http://www.rgaiot.com/press/rga-ventures-announces-iot-venture-studio-uk/">Matt’s accelerator</a> and preparing for sessions at <a href="http://www.opengovasia.com/events/56-philippine-opengov-leadership-forum-2017">OpenGov Leadership Forum Philippines</a>, Cloud Expo Europe and <a href="https://www.ncsc.gov.uk/events/cyberuk-2017">CyberUK In Practice</a>.</p><p>March has been another change of gears. I spent some time helping FutureGov work through plans for an exciting new project. I then had a couple of days in Toronto sharing experiences and advice with the Ontario government. Then it was Manila, where I spent a day talking with regional governments about cloud and leadership. And quick stops at Cloud Expo Europe, and CyberUK In Practice (chairing a panel on cloud security).</p><p>I’ve decided that my next phase is going to be a spell of independent consulting. It wouldn’t be right to dive straight into one big thing after the intense experience of building and sustaining GDS. And I quite like the thought of a bit more variety. I’m already seeing how much the lessons learned at GDS can help all sorts of other organisations.</p><p>I want to help organisations who are trying to integrate internet-era technology and thinking into their strategy. To help people approach security as a positive agent for change. To bring together cross-disciplinary teams and adopt continuous delivery. The sort of things we did at GDS, but in a few different contexts.</p><p>So… if you think I could help you, do get in touch. I’m London based, but happy to travel for the right project.</p><p>(To keep up the travel theme, I’m also planning a trip to Perth, Australia in May to speak at <a href="http://west.yowconference.com.au/">YOW! West</a>. If you know of anyone round there who’d like some of my time, I have a few days free around the conference and would love to use them productively).</p><p><em>Originally published at </em><a href="https://jystewart.net/2017/03/25/what-next/"><em>jystewart.net</em></a><em> on March 25, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6565e77a4b9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Enterprise-ready SaaS Features]]></title>
            <link>https://medium.com/@jystewart/enterprise-ready-saas-features-9f6e3fc76ffa?source=rss-579b9ccb0cc0------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f6e3fc76ffa</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[technology-strategy]]></category>
            <category><![CDATA[saas]]></category>
            <dc:creator><![CDATA[James Stewart]]></dc:creator>
            <pubDate>Fri, 24 Mar 2017 10:35:44 GMT</pubDate>
            <atom:updated>2017-03-24T10:37:51.193Z</atom:updated>
            <content:encoded><![CDATA[<p>In my last post on c<a href="https://jystewart.net/2017/03/20/cloud-native-organisations/">loud-native organisations</a> I said:</p><blockquote><em>“we should be clear about the principles that apply and help our people understand what we need to watch out for when choosing technology.”</em></blockquote><p>As the responsible people in an organisation we need to be thinking about things like:</p><ul><li>We need to be confident that when people leave our organisation we retain access to information on the work they’ve been doing</li><li>We need to be sure that the sensitive information we handle in our organisation can only be accessed by authorised people</li><li>Where we have time-sensitive business commitments, we need to be confident that third-party software will be available for us to use when we need it</li></ul><p>The specifics like how important that is, what types of information, etc. will be context sensitive.</p><p>Being clear about those concerns, and then translating them into the sort of features we need (eg. good archiving tools, single-sign-on integration, etc) helps us think about what’s really essential and then be clear with the market about what we need and why.</p><p>Approaching it with those two steps–what is important to my organisation, and then what might that mean in terms of features–helps us in a few ways. It:</p><ul><li>Helps us work out when these things become important — is it whenever someone uses a tool, or is it when they’re used for certain purposes?</li><li>Lets us consider which measures are best dealt with through product features, and which are about how we shape our processes or use our tools</li><li>Provides space for innovative approaches as we’re free to consider what we’re trying to achieve, not how we expect it to be done</li></ul><p>That said, most of the time the basics we want are covered by pretty standardised, common features.</p><p><em>(As an aside: it’s worth recognising that these are all things we’d think about regardless of who provides our software, it just happens that they come into focus for many people when thinking about “cloud”)</em></p><p>Catching up on blog posts recently I was delighted to discover <a href="https://www.enterpriseready.io/">“The Enterprise Ready SaaS Feature Guides”</a> (via <a href="http://tomtunguz.com/pm-guide-to-moving-up-market/">Tomasz Tunguz</a>). It’s very much a supply-side resource that covers those basic implementation requirements, and well worth anyone making software decisions (whether supply-side or buyer-side) taking a look.</p><p>It’s been really good to see the UK’s National Cyber Security Strategy <a href="https://www.ncsc.gov.uk/blog-post/architecture-behind-ncscs-it-system">covering some of that ground in its recent blog posts</a>. It’d be great to see more consumers sharing their thinking.</p><p><em>Originally published at </em><a href="https://jystewart.net/2017/03/24/enterprise-ready-saas-features/"><em>jystewart.net</em></a><em> on March 24, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f6e3fc76ffa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cloud-native organisations]]></title>
            <link>https://medium.com/@jystewart/cloud-native-organisations-7ef9953bba4f?source=rss-579b9ccb0cc0------2</link>
            <guid isPermaLink="false">https://medium.com/p/7ef9953bba4f</guid>
            <category><![CDATA[organisational-design]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[James Stewart]]></dc:creator>
            <pubDate>Mon, 20 Mar 2017 16:18:59 GMT</pubDate>
            <atom:updated>2017-03-21T10:42:58.445Z</atom:updated>
            <content:encoded><![CDATA[<h3>I spoke recently at the <a href="http://www.opengovasia.com/events/56-philippine-opengov-leadership-forum-2017">OpenGov Leadership Forum in Manila</a> and at <a href="http://www.cloudexpoeurope.com/">Cloud Expo Europe</a>. At both I started to explore a theme from <a href="https://governmenttechnology.blog.gov.uk/2017/02/03/clarifying-our-cloud-first-commitment/">my final GDS blog post</a>: cloud-native organisations.</h3><p>“Cloud” is a nebulous term. At the start of both talks I explained that, while there are formal definitions that I’ve found useful, for me it’s just a useful term for starting a conversation about what’s currently happening at the collision point of “the internet” and “computing tools”. Most of the time for technology, I don’t draw a distinction between the impact of cloud, agile, devops and a number of other inter-related movements.</p><p>I talked in both settings about the work that we did in GDS and across government, of which the “Cloud First” policy was a significant part. They were both short talks and I was struggling for time. I should have gone into quite a bit more detail about GDS’ work when speaking in Manila.</p><p>For Cloud Expo Europe I drew out several lessons from the work in government. The primary lesson was that changing how we approach technology changes how we think about what government does.</p><h3>Learning from the government journey</h3><p>I’ve talked before about how there’s a real opportunity to be much clearer about what needs to be bespoke and what we can consume. There are a set of areas where organisations think they have special requirements for their core technology. Most of the time that’s not true.</p><p>That is important, but the more transformative change is that as a set of technologies becomes more accessible it becomes part of our normal toolkit.</p><p>A much lower barrier to entry for technology lets cross-disciplinary teams incorporate technology development into policy and service design, and to iterate it in an operational setting. A set of traditional barriers are no longer necessary. Those cross-disciplinary teams–given freedom to meet their goals–are where we will get performance and innovation.</p><h3>Today’s technology world</h3><p>I went on to talk about some general trends in the technology world, once again citing Stephen’s <a href="https://thenewkingmakers.com/">Developers are the new Kingmakers</a>. Top-down decision making isn’t enough to handle the pressure organisations are facing to change, or the scale of opportunities available through open source and cloud technologies.</p><p>What we see with the <a href="https://devops-research.com/">mature end of devops</a>, and in much of the thinking behind “cloud native” architectures, is a strong focus on the team as the unit of delivery. And the team as the unit of responsibility. There are a set of architectural practices that support independent teams. They work where organisations set clear goals and principles.</p><p>Too often when we talk about “cloud” we either talk about infrastructure-as-a-service, or we talk about software-as-a-service. By and large they’re treated as very different things, but there are some common principles here that ought to be applicable to IT adoption more generally.</p><p>Software-as-a-service–particularly software that’s offered via a “freemium” model–allows a complete shift from a world where every new productivity tool has to be evaluated by a central IT department. People are expecting tools at work at least as good as those they have at home, and often will just adopt what they need whether the central department likes it or not.</p><p>As with many things we associate with cloud, that’s not new (though the scale has changed). It’s what we have been calling “Shadow IT”. With the shift to cloud we have the opportunity to change our approach.</p><p>In the talks, I cited the “<a href="https://www.gov.uk/government/publications/cloud-service-security-principles/cloud-service-security-principles">Cloud Security Principles</a>” as an example of how being more explicit about the things we care about lets us empower more people to make good decisions.</p><p>Those principles are an early illustration of how we should be thinking about cloud tools (IaaS or SaaS) in general. We should be clear about the principles that apply and help our people understand what we need to watch out for when choosing technology. Then we can help scale the use of the tools they find most useful.</p><p>There’s a lot more to do to take the thinking in those principles and really open it up to a wide audience, but they work very well as an indicator of direction.</p><blockquote><a href="https://techblog.netflix.com/2017/02/introducing-netflix-stethoscope.html"><em>“Software that treats people like people, not like cogs in the machine”</em></a></blockquote><p>To illustrate what that should be letting us do, I stole a line I loved from a recent Netflix blog post. A goal of all “cloud adoption” efforts should be to give people more control of how they meet their goals.</p><h3>The real challenge</h3><p>As with almost everything, the real challenge for organisations is about leadership. Organisations face many challenges and it’s easy to fall back on locking things down as a way of reducing the perceived risks. That’s rarely the most productive approach.</p><p>Leaders need to focus on being open: about the real objectives, about the principles that guide how the organisation approaches issues, and about any particular risks.</p><p>Management needs a set of practices that understand what’s happening in the organisation, but that’s to keep things on course not to lock them down.</p><p>When thinking about cloud-adoption people seem to often get caught up in questions about catalogues of services and new lists of approved tools. Those things may be useful, but we would be better off spending more time explaining how we create a well-aligned, enabling environment before we get down into those sorts of details.</p><p><strong>Update:</strong><br><a href="https://twitter.com/kushalp">Kush</a> quite rightly pointed out that I didn’t go into anything specific about what to do next. In Manila, there were a set of roundtable conversations where we could begin to get into that. In London, I really just wanted to get people thinking. More blog posts to come…</p><p><em>Originally published at </em><a href="https://jystewart.net/2017/03/20/cloud-native-organisations/"><em>jystewart.net</em></a><em> on March 20, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7ef9953bba4f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Talking challenges and change at GitHub Universe]]></title>
            <link>https://medium.com/@jystewart/talking-challenges-and-change-at-github-universe-a69fdb19cfe3?source=rss-579b9ccb0cc0------2</link>
            <guid isPermaLink="false">https://medium.com/p/a69fdb19cfe3</guid>
            <category><![CDATA[digital]]></category>
            <category><![CDATA[government]]></category>
            <dc:creator><![CDATA[James Stewart]]></dc:creator>
            <pubDate>Fri, 11 Nov 2016 00:00:00 GMT</pubDate>
            <atom:updated>2016-11-13T16:58:14.656Z</atom:updated>
            <content:encoded><![CDATA[<p>Talking challenges and change at GitHub Universe</p><p>A short while back I was fortunate to speak at <a href="https://www.githubuniverse.com/">GitHub’s annual Universe conference</a> in San Francisco. <a href="https://gdstechnology.blog.gov.uk/2014/01/27/how-we-use-github/">GitHub is a tool we use extensively at GDS</a> and it was good to be able to talk with other customers, share how we’re using the product, and discuss the future product direction with their core team.</p><p>I was asked to tell the story of GOV.UK and that’s what most of my talk covered. Starting with <a href="https://www.gov.uk/government/publications/directgov-2010-and-beyond-revolution-not-evolution-a-report-by-martha-lane-fox">Martha Lane Fox’s report</a>, the alpha version of GOV.UK and the story from there. I was keen to emphasise a number of points.</p><h3>Starting small</h3><p>When we start out trying to do something big, we often think that means we need to start with a big team. You may eventually need a lot of people to make a big change but successful delivery starts with teams that know and trust each other.</p><p>The reason that we were able to move fast was that we started small and built trust in the core team before we scaled up. We were able to prioritise trust and the team’s sense of responsibility (to each other and for the work) before working out the co-ordination and governance challenges that come with a bigger team.</p><h3>Trust, users, delivery</h3><p>The GitHub audience was naturally interested in our decision to <a href="https://gds.blog.gov.uk/2012/10/12/coding-in-the-open/">code in the open</a>. Preparing for the talk I’d tried to find some record of the moment that we first started developing GOV.UK code in the open but couldn’t find any, which shows what a simple decision it was.</p><p>This was partly because we had a mandate to do things differently, but fundamentally it was because we were working in a high trust environment where the team understood our responsibility and those sponsoring the project trusted us to act accordingly.</p><p>When decisions of that sort need to go through multiple layers of sign-off radical change rarely happens, but when teams are trusted significant changes become almost unremarkable.</p><h3>Getting close to users</h3><p>Our former colleague Tom Loosemore’s <a href="https://twitter.com/tomskitomski/status/729974444794494976">tweet defining digital</a> has been cited continually since he posted it, and this talk was no different.</p><p>While some of the biggest challenges in making government work for its users lie far deeper into the system, it’s no accident that we started with a website.</p><p>To really reform the deeply embedded culture, practices, processes and technologies of a large organisation you need to get close to your users. You need to go to them with high quality user research, but a website is the primary way that the majority of people now come to you and is an incredibly valuable source of data about what they need and value. As a website, GOV.UK laid out a new vision for what interaction with government could be, and for how we could meet that across our internal silos. Change that’s worth making works from the outside in and GOV.UK was the first step on the way.</p><h3>Professional responsibility</h3><p>Having touched on trust and responsibility when introducing opening our code I want to dwell on that point. A sense of broader responsibility is something that naturally comes with the <a href="https://www.gov.uk/government/publications/civil-service-code/the-civil-service-code#civil-service-values">civil service values</a> and public service ethos but there are some areas in which it’s worked out that might be of particular interest to the sort of tech audience that was at the conference. Reflection on responsibility is vitally important as technology professions dominate so much of how the modern world is evolving.</p><p>I started with the responsibility to put accessibility over exciting technologies. In an industry so dominated by new JavaScript frameworks and fascinating new techniques it can sometimes feel like we’re constraining ourselves with the very simple interaction patterns on GOV.UK, but our work is more successful when we focus on what’s right for our users before satiating our own curiosity. Robin Whittleton has recently written about <a href="https://gdstechnology.blog.gov.uk/2016/09/19/why-we-use-progressive-enhancement-to-build-gov-uk/">why we are committed to progressive enhancement</a> (unfortunately we published just after the conference so I couldn’t reference that).</p><p>As you get deeper into transformative change you have to work on the mechanics of the system and I used work to change the<a href="https://www.gov.uk/government/publications/government-security-classifications"> security classification system</a> as a striking example of that (and hope I was clear enough that that work was led by some of our Cabinet Office colleagues, not GDS). Those changes were vital to strip away a lot of the complexity and legend that had built up around the old system, to let us adopt new ways of working and to put more responsibility in the hands of specific civil servants and their teams.</p><p>What’s been challenging is finding the right way to bring people with us, to make sure that a change that enables the confident trailblazers doesn’t paralyse people who need more guidance or have to make a lot more decisions than they used to. This is still a work in progress but it’s vital to be conscious of that challenge if you want to make changes stick.</p><p>More broadly I wanted to acknowledge that very few of the big problems the world faces are specifically about technology. They’re about systems and people. Thinking about the technology and grasping new technologies can help us understand those problems in new ways and find other ways to resolve them, but we need to keep remembering that context.</p><p>Everything changes, and often quickly. User needs shift, our understanding of them increases, the way technology can meet those needs evolves. Most of the time our job as technologists is to minimise the cost of changing the systems we inherit or develop so that they can rapidly react to those changing expectations.</p><h3>Finally</h3><p>GitHub did an incredible job of creating a diverse, inclusive and welcoming event, and I’m very grateful to them for inviting me. It was particularly good to see a growing presence for public sector work at the event, with Alvand Salehi representing the US government’s new <a href="https://github.com/WhiteHouse/source-code-policy">federal source code policy</a> (which GDS provided some support with), Clarence Wardell talking about the <a href="https://www.whitehouse.gov/the-press-office/2016/04/22/fact-sheet-white-house-police-data-initiative-highlights-new-commitments">Whitehouse’s police data initiative</a>, and Ian Lee from the <a href="https://www.llnl.gov/">Lawrence Livermore National Laboratory</a> talking about “developing open source in service to national security”.</p><p>Videos of all the talks, including my own, are <a href="https://www.youtube.com/channel/UC7c3Kb6jYCRj4JOHHZTxKsQ">available on YouTube</a>.</p><p><em>Originally published at </em><a href="https://governmenttechnology.blog.gov.uk/2016/11/11/talking-challenges-and-change-at-github-universe/"><em>governmenttechnology.blog.gov.uk</em></a><em> on November 11, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a69fdb19cfe3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We are renewing our Cloud First commitment]]></title>
            <link>https://medium.com/@jystewart/we-are-renewing-our-cloud-first-commitment-c3f2eaa0af05?source=rss-579b9ccb0cc0------2</link>
            <guid isPermaLink="false">https://medium.com/p/c3f2eaa0af05</guid>
            <category><![CDATA[digital]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[government]]></category>
            <dc:creator><![CDATA[James Stewart]]></dc:creator>
            <pubDate>Tue, 13 Sep 2016 00:00:00 GMT</pubDate>
            <atom:updated>2016-09-13T17:29:41.827Z</atom:updated>
            <content:encoded><![CDATA[<p>We are renewing our Cloud First commitment</p><p>A few weeks ago I spoke at an event organised by <a href="https://www.oracle.com/uk/index.html">Oracle</a> focussed on how the public sector uses the cloud. I talked about why we are committed to the cloud, how this commitment has changed how we think about technology, and what we plan to do next. I spoke alongside my Government Digital Service (GDS) colleague <a href="https://governmenttechnology.blog.gov.uk/2016/06/03/a-new-approach-to-common-technology-services/">Iain Patterson, who updated attendees on the work of Common Technology Services (CTS</a>).</p><h3>The Cloud First policy</h3><p>In 2013, the <a href="https://www.gov.uk/government/news/government-adopts-cloud-first-policy-for-public-sector-it">Cloud First policy</a> set out government plans to focus technology commitments on where it can most add value. This put an end to the government running its own data centres, and sometimes running its own software.</p><p>The policy (part of the overall <a href="https://www.gov.uk/government/publications/technology-code-of-practice/technology-code-of-practice">Technology Code of Practice</a>) reflected a change of thinking. For a range of crucial components, we can now clearly think about what we need from technology and consume them as products and commodities, rather than build or buy the entire stack as custom pieces.</p><p>We can now work flexibly, separating services so they can be defined in ways even computers understand (APIs). We use resources elastically, summoning them when we need them, and paying for them on a utility basis (based on the number of users we have or the amount of processing we’re doing). Cloud First means less of our time is focussed on procurement negotiation and complex licensing, and more on making our tools robust and responsive.</p><p>The cloud reduces the time and cost to get something up and running, making change easier and empowering our people to experiment with new tools and approaches.</p><p>Change is constant for us, whether it’s changing user needs, a growing understanding of how to meet them, or the wider landscape of changing challenges and opportunities. It’s our responsibility as technologists to minimise the cost of change so that our teams can continually iterate services.</p><h3>Clarity around system components</h3><p>Too often we use the wrong labels and concepts when discussing the technology that powers our services. In thinking about what we want from cloud we need to do better.</p><p>Software engineers are trained to talk about very low-level building blocks at the library or microservice level. Meanwhile it’s still too common to find discussions taking place around around large, monolithic concepts like <a href="https://en.wikipedia.org/wiki/Enterprise_resource_planning">enterprise resource planning</a> (ERP) and case management. This dichotomy in terms reflects the problems with the old fashioned business process design approach.</p><p>Even though there’s inherent confusion surrounding software labels in this traditional approach to procurement, the products have to be bought anyway. Complicated compromises have to be made between the functionality of large pieces of software, the cost of customising it, and how to effectively meet user needs. We are locked into a vendor and have to spend a lot of money on configuration.</p><p>New practices let us think more flexibly. Being clear about how our systems break down into components let’s us understand how we can use utility and commodity elements and where we should be innovating ourselves. API-enabled software as a service let’s us blend off the shelf components into broader systems using common standards, with a clear understanding of where canonical data lives.</p><p>We can make smarter use of what the market offers, and develop the talent, understanding and experience in our own teams. We also have a far richer toolbox than we’ve ever had before to respond to rapidly changing user expectations.</p><h3>Our future plans</h3><p>Over the next few months we’ll refresh the Cloud First policy and do more to share existing good practice. For example, we’ll work with our colleagues in security and across government to <a href="https://gdstechnology.blog.gov.uk/2016/07/13/why-security-says-no-wont-cut-it-anymore/">improve our security advice</a> and do more to make sure that the changes are clearly communicated to the right people.</p><p>The <a href="https://www.gov.uk/government/publications/cloud-service-security-principles/cloud-service-security-principles">Cloud Security Principles</a> were a big step, but it’s clear that worked examples will make them more valuable. We’ve still got lots of myths to bust and best practice to share, to prove that most of the time public cloud is at least as secure as your own hosting.</p><p>We’ll also be updating and reviewing the range of tools that we can promote to help departments make the transition. <a href="https://digitalmarketplace.blog.gov.uk/2016/06/28/how-the-serious-fraud-office-used-the-digital-marketplace/">Crown Hosting has helped many departments reduce their datacentre commitments</a> and get a better understanding of what they have and will remain crucial, but not every journey to the cloud is the same and there are a huge range of tools and techniques out there to help.</p><p>We’re <a href="https://governmenttechnology.blog.gov.uk/2016/08/19/developing-our-technology-network-and-approach/">refreshing our approach to Open Standards</a>, making sure we can identify, select and contribute to standards even more flexibly than before. We need to be clearer with the market about what open standards we expect to see, and share our needs with the groups developing new standards.</p><p>We’ll be providing more clarity for civil servants and the market about what we think good looks like for different types of cloud use. There’s huge variation in the maturity of Software as a Service applications and often that’s good. It’s evidence of a fast moving, innovative marketplace. But it’s important we’re clear about what we need from the market so we can have the right interfaces, the right security, and simplicity for users.</p><p>We’re bringing colleagues from across government together to look at some of our core business processes and the tools that support them. Over the past few years there’s been a lot of smart thinking, but it’s time for much sharper language and thinking about how we label things, what common components can make things more efficient and so on.</p><p>At GDS this involves working together across <a href="https://gds.blog.gov.uk/2016/04/18/what-we-mean-by-service-design/">service design</a>, <a href="https://www.digitalmarketplace.service.gov.uk/">Digital Marketplace</a>, <a href="https://www.gov.uk/government/groups/common-technology-services-cts">Common Technology Services</a> and <a href="https://governmentasaplatform.blog.gov.uk/">Government as a Platform</a> (GaaP).</p><p>The changes in the technology market over the past few years are incredibly exciting. We’re aiming to ensure that the work we do in this area is helpful not just to accelerate our work in government but also to contribute back to the growing field of knowledge about how best to use the tools we now have at our disposal and what they can help us achieve.</p><p>Fundamentally, we’re talking about Cloud because we believe that the change it represents is a huge opportunity to put more focus on meeting users’ needs, more rapidly, more flexibly and more effectively.</p><p>We would like to hear about any obstacles you have encountered in making the transition to the cloud. Your comments will help us develop our work. <a href="/service/mailto:contact.tech@digital.cabinet-office.gov.uk">Contact the Technology Group</a> or comment below.</p><p><em>Originally published at </em><a href="https://governmenttechnology.blog.gov.uk/2016/09/13/we-are-renewing-our-cloud-first-commitment/"><em>governmenttechnology.blog.gov.uk</em></a><em> on September 13, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c3f2eaa0af05" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why ‘security says no’ won’t cut it anymore]]></title>
            <link>https://medium.com/@jystewart/why-security-says-no-won-t-cut-it-anymore-8aea1f0ee943?source=rss-579b9ccb0cc0------2</link>
            <guid isPermaLink="false">https://medium.com/p/8aea1f0ee943</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[cloud]]></category>
            <dc:creator><![CDATA[James Stewart]]></dc:creator>
            <pubDate>Wed, 13 Jul 2016 00:00:00 GMT</pubDate>
            <atom:updated>2016-07-13T12:11:03.394Z</atom:updated>
            <content:encoded><![CDATA[<p>Why ‘security says no’ won’t cut it anymore</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*z0txDrRmpKaKJ2D1J1Cy-g.jpeg" /></figure><p>I spoke recently at the <a href="http://business-reporter.co.uk/our-events/data-security-cloud-2016/">Business Reporter’s Data Security in the Cloud</a> event about how security has changed to face the reality of the modern internet era. The old world of assurance and compliance and ‘<a href="https://governmenttechnology.blog.gov.uk/2015/12/08/security-says-no/">security says no</a>’ won’t cut it anymore. Security thinking has to be holistic and take into account users, culture, context and behaviour not just technology.</p><p>This post will summarise some of the areas I discussed in my talk, detailing these modern realities and how we manage the changing security landscape.</p><p><strong>Thinking beyond the cloud</strong></p><p>The GDS remit has always been about digital transformation, which <a href="https://twitter.com/tomskitomski/status/729974444794494976">our former colleague Tom Loosemore recently expressed</a> as “applying the culture, practices, processes and technologies of the internet-era to respond to people’s raised expectations.” Note the lead-in on culture, practices and processes before we get to technologies.</p><p>All too often, when responding to changing security expectations, there’s a tendency to talk about the cloud and related IT approaches rather than considering the context of broader change that’s happening to organisations.</p><p>We need to think about what’s changing across the whole environment, rather than simply thinking of cloud security in isolation. For example, while adopting cloud technologies, we’ve also seen the ascendency of continuous delivery practices, a shifting skills profile in our organisations and a move to being dependent on a range of small suppliers and contracts rather than large outsourcing contracts.</p><p><strong>Securing while trusting teams</strong></p><p>In the fast paced internet era, we need to move at the pace that’s expected of us and that means devolving lots of responsibility into focused teams. Teams need to be as autonomous as possible and effective teams need context. That starts with understanding what everyone is trying to achieve and ensuring they have the right tools at their disposal to deliver.</p><p>Securing in this type of setting can’t involve blanket lock-downs. This just won’t work; if we block the tools people want to use, we will only get more Shadow IT (people tend to circumvent controls to get their jobs done more efficiently).</p><p>Instead security must be proactive in helping teams work at speed, while selecting and using the most intuitive and secure tools available.</p><p><strong>Transparency is essential</strong></p><p><a href="https://twitter.com/thommeread">Tom Read</a> who led the Cabinet Technology Transformation (now Group CTO at the <a href="https://www.gov.uk/government/organisations/department-for-business-innovation-skills">Department of Business Innovation and Skills</a>) has talked about an experiment his team ran to measure the number of people using non-work devices. The team installed some Wi-Fi access points around government buildings and then kept track of how many people connected to their personal devices. This let them identify people whose needs weren’t being met by their official IT. The team could then talk to those people about how new tools would help them.</p><p>Where there are tradeoffs to be made between how people want to work and what makes for secure behaviour, we can explore those with the users and find the best design. In the old way you may have a secure system that gives you a degree of confidence but the mass of shadow IT and the users working around your security policies means poor visibility into how secure your system really runs. That’s a natural result of a blanket approach and we need to do better.</p><p>Apart from more personalised and targeted security policies, we need tighter auditing. We need to know, for example, who is spinning up virtual machines and if someone has made changes to a server. If we know that we have a better chance of determining whether a change is appropriate or if it’s evidence of tampering. Previously a lot of the work we want to track was done by sysadmins but now the majority of it can be managed through automated auditing systems. Configuration management and infrastructure automation tells you whether there is any deviation in your infrastructure that can indicate compromise. The use of these systems can also vastly reduce the number of people needing direct access to a system, which can be hard to track.</p><p>Auditing’s not just for managing infrastructure, it works at the software as a service level as well. The best cloud productivity tools present us with opportunities to get logs of activity and an understanding of who has copied which documents, who has shared what with whom, and so on. We can get useful data about what’s happening in a way that’s not intrusive to our users and review logs to see unusual patterns.</p><p>There’s also transparency needed from our providers. Now that teams are working across a global network rather than within carefully controlled business networks, we need to gain certain guarantees from cloud hosting providers and dig deep into their security policies. For instance, providers can supply us with a guarantee not to look inside our virtual machines or containers, and we can ask what data encryption mechanisms they have in place to avoid them seeing our data.</p><p>Finally, design for privacy. There are differing public attitudes on privacy and it’s not clear where public expectations will go. At the moment though, principles of good privacy design revolve around making things transparent, ensuring clarity of ownership of data, providing the subjects of data with control, and minimising the amount of duplication and sharing. These are also important tools for building secure systems. If there’s one area to watch in the next few years, it’s privacy engineering.</p><p><strong>Assessing cloud providers</strong></p><p>When we talk to a hosting provider we don’t want to do a complete security audit ourselves. We want to know where they’ve applied industry best practices and how they can assure us of their methodology.</p><p>ThIs means establishing the right level of relationships with providers. When entering into security conversations as government, it’s all too common for us to be met with layers of the provider organisation; first public sector sales, followed by compliance, etc. We should instead first be talking to the actual architects and engineers. We want to talk to them about what systems really do and how they’re composed. Then we can be sure we’re on the right path.</p><p>Our colleagues in <a href="https://www.cesg.gov.uk/about-us">CESG</a> produced these really helpful <a href="https://www.gov.uk/government/publications/cloud-service-security-principles/cloud-service-security-principles">principles on cloud security</a> but we still need to take care in how we assess providers against them and apply them internally ourselves. The security practices for our primary hosting provider needn’t be the same as for our shared calendaring app. Think proportionality, think trust, think context — we’re still working on how we apply this thinking ourselves and we’ll blog more on this soon.</p><p>Apply the principles incrementally and proportionally. When you start, there should be just a basic sanity check. For example, if trialling some Software as a Service, you may look to see if the provider has a clear privacy policy, whether it offers obvious points of contact, if it requires good passwords, and offers everything over strong HTTPS, but you wouldn’t want to go to the effort of understanding how every element of the system is tested or how incidents are handled. As you decide whether the tool is what you need for a given task, you’ll be able to understand whether there are areas you should probe more deeply.</p><p><strong>Preparing for incidents</strong></p><p>However much we prepare, there is always the possibility of an incident. In order to respond quickly, the team on the ground needs context to make decisions, clear leadership and an understanding of their communication channels.</p><p>Incident management is often perceived to involve managing at speed during chaos, but learning from emergency response teams in other realms, we have recognised that response teams that constantly practice, run drills and rehearse their roles are significantly more effective.</p><p>Teams should be running <a href="https://gdstechnology.blog.gov.uk/2015/02/06/running-a-game-day-for-gov-uk/">red team exercises and game days</a> to rehearse incident management practices, and after each incident we recommend that a <a href="https://codeascraft.com/2012/05/22/blameless-postmortems/">blameless post mortem</a> is conducted to identify whether there are actions that could improve the team’s ability to respond.</p><p>All too often we think about incident management through the lens of dealing with the moment. It needs to follow through into action to address systemic issues and this needs to be done proportionally and calmly. That’s something that’s very much in scope of the new <a href="https://www.gov.uk/government/news/new-national-cyber-security-centre-set-to-bring-uk-expertise-together">National Cyber Security Centre (NCSC</a>).</p><p>I ended the talk reiterating that “cloud” is just one area of change impacting our organisations at the moment. When considering security, we need to think about the wider changes taking place to how we work and what we expect from our technology, etc. We’re continually developing our thinking in this area and we’d be interested in your feedback.</p><p>We also plan to update security sections in the Service Design Manual soon on areas such as cloud and information security. In the meantime, the following resources may help:</p><p><a href="https://www.cesg.gov.uk/guidance/principles-effective-cyber-security-risk-management"><strong>Risk management in digital projects</strong></a></p><p><a href="https://www.cesg.gov.uk/guidance/cloud-security-guidance-summary-cloud-security-principles"><strong>Government cloud security principles</strong></a></p><p><a href="https://www.cesg.gov.uk/guidance/security-design-principles-digital-services-0"><strong>Principles for building secure digital systems</strong></a></p><blockquote><em>You can </em><a href="https://twitter.com/jystewart"><em>follow James on Twitter</em></a><em>, </em><a href="https://public.govdelivery.com/accounts/UKGOVUK/subscriber/new?topic_id=UKGOVUK_7538"><em>sign up now for email updates from this blog</em></a><em> or </em><a href="https://gdstechnology.blog.gov.uk/feed/atom/"><em>subscribe to the feed</em></a><em>.</em></blockquote><p><em>Originally published at </em><a href="https://gdstechnology.blog.gov.uk/2016/07/13/why-security-says-no-wont-cut-it-anymore/"><em>gdstechnology.blog.gov.uk</em></a><em> on July 13, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8aea1f0ee943" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing GDS’ architecture approach and principles]]></title>
            <link>https://medium.com/@jystewart/introducing-gds-architecture-approach-and-principles-30320c1da2f4?source=rss-579b9ccb0cc0------2</link>
            <guid isPermaLink="false">https://medium.com/p/30320c1da2f4</guid>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[government]]></category>
            <category><![CDATA[digital]]></category>
            <dc:creator><![CDATA[James Stewart]]></dc:creator>
            <pubDate>Tue, 05 Jul 2016 00:00:00 GMT</pubDate>
            <atom:updated>2016-07-07T14:27:06.655Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Introducing GDS’ architecture principles and approach</strong></p><p>With the number of visitors we have coming through GDS we’re often asked to present various areas of our work, particularly architecture. We’ve usually kept the presentation pretty informal. People mean so many different things by architecture that it’s important to take some time to understand our audience before we dive into explaining our approach.</p><p>Recently though, we’ve noticed some common patterns emerging and have begun pulling our thoughts together as an <a href="https://docs.google.com/presentation/d/1jj8mndjx0ZYXo0ZS9V9AZRlh0-enuZVYF1L44Myj80Q/edit?usp=sharing">introductory slide deck</a>.</p><p>We are sharing the thinking behind our slide deck here. In sharing this, we want to be very clear that this is a snapshot of a conversation starter. It’s very easy for a piece of work like this to switch from “useful starting point” to “expected, fixed approach” but used carefully it will make it easier for us to reduce the learning curve for new members of the team and present our approach.</p><h3>The context</h3><p>Last year Dave Rogers of the Ministry of Justice wrote <a href="https://mojdigital.blog.gov.uk/2015/02/12/technical-architecture-at-moj-digital/">a great blog post talking about their approach to technical architecture</a>. For me the main insight in that post was captured in the comment:</p><blockquote><em>The emergence of a mature infrastructure-as-a-service and platform-as-a-service marketplace has transformed compute, storage and networks into utilities. With this the costs associated with major architectural changes has dropped, in some cases, to near-zero.</em></blockquote><blockquote><em>Technical architects who are able to take advantage of these changes are now working with a single medium: code. The physical infrastructure, the manual processes and their constraints have largely gone.</em></blockquote><p>The world in which we’re operating allows more and more elements of our systems to be defined in software, and our profession has developed practices that make that software easier and cheaper to change.</p><p>At the same time, not only are more and more of our activities digital, but users have come to expect that great services will be regularly improved. Responsive and regularly improved services engender trust, without which government services fail.</p><p>That’s not to say that all architecture is software and at GDS we have architects working on a variety of more “infrastructural” projects, working on <a href="http://crownhostingdc.co.uk/">Crown Hosting</a>, <a href="https://www.gov.uk/government/groups/public-services-network">Public Services Network</a>, blueprints, such as <a href="https://www.gov.uk/guidance/common-technology-services-cts-secure-email-blueprint">secure email</a>, for <a href="https://www.gov.uk/government/groups/common-technology-services-cts">Common Technology Services</a>, and so on. Over time, the interfaces between the hardware and software elements are becoming clearer and more standardised, with software defining more and more.</p><h3>The approach</h3><p>Within a more rapidly evolving environment, architecture has to be a team sport. That doesn’t just mean “architecture teams”, it means architects and architecture as part of a much broader team.</p><p>Teams build systems and services at pace using better tools than we’ve ever had before for. They <a href="https://governmenttechnology.blog.gov.uk/2015/12/10/guest-post-how-automation-and-testing-reduce-risk-in-moving-cloud-vendors/">test the behaviour and performance of our systems</a> every step of the way and iterate as we learn more about our users, their needs, and the interactions between systems. We’ve recognised that to provide great services we need collaborative, diverse and multi-functional teams.</p><p>So too, the economics of how we approach common components has shifted. It is easier than ever for teams to build minimum viable components of their own and then swap them out as more mature alternatives emerge.</p><p>Common capabilities can still speed up delivery and improve services, but the best components emerge rather than being proscribed in abstract organisational designs.</p><p>The GDS architecture community always starts with the same <a href="https://www.gov.uk/design-principles">Design Principles</a> as all other disciplines working on delivering digital services, and draw on other great work like the <a href="https://www.gov.uk/government/publications/cloud-service-security-principles/cloud-service-security-principles">Cloud Security Principles</a>, <a href="https://www.gov.uk/government/publications/open-standards-principles/open-standards-principles">Open Standards Principles</a> and the <a href="https://www.gov.uk/service-manual/technology/code-of-practice.html">Technology Code of Practice</a> but we also have some working principles of our own:</p><h3>Start small and self-contained</h3><p>Focus on understanding the user needs your service needs to meet and how it will do that. Consider whether you can do this using existing tools to keep your technology simple.</p><h3>The unit of delivery is the team</h3><p>When we work in disciplinary silos we can easily reinforce our biases and we cause friction with complex hands-offs. Make space for the team to do the discovery and <a href="https://gdstechnology.blog.gov.uk/2016/02/08/the-role-of-an-architect-in-discovery/">participate in it fully</a>.</p><h3>Work with the grain of the internet and the web</h3><p>The web is the most successful technology platform we have, building from simple protocols to support incredible large-scale applications. It’s our starting point for the vast majority of what we do. That leads us to federated and distributed approaches, and to architectures that make use of resources across the network rather than tightly-integrated technology stacks.</p><h3>Platforms, standards and re-use emerge</h3><p>Design for concrete needs, not for abstract reuse, but look sideways to see opportunities.</p><h3>No undifferentiated heavy lifting</h3><p>Our effort should be put where we really add value. That’s why we have a <a href="https://www.gov.uk/government/news/government-adopts-cloud-first-policy-for-public-sector-it">Cloud First policy</a> and focus on <a href="https://www.gov.uk/service-manual/making-software/open-source.html">open source</a> software.</p><h3>Assume evolution</h3><p>Software is never finished but different elements evolve at different paces. Allow for this in your planning and your management, providing clear interfaces between components and making sure each of them can be changed at the appropriate pace.</p><h3>It’s not real until it has users</h3><p>A project isn’t a success until its users think it is. The only good technology is the technology used by real users.</p><h3>Government is rarely unusual</h3><p>Very little of what we do operates at significant scale, and most of our challenges are common. That should inform how we work, and where we learn from, <a href="https://digital.blogs.coop/2016/06/14/what-we-mean-when-we-say-digital/">seeking out the best examples from across our profession</a>.</p><h3>Design for operability</h3><p>Users need available and resilient services. This requires well maintained technology.</p><h3>Common architectures and mandated components</h3><p>There are areas where GDS is developing common architectures and has controls in place to ensure the use of common components and platforms.</p><p>In the slide deck we state:</p><blockquote><em>There are reasons to mandate use of certain components, but they’re never about conformance to a technical roadmap.</em></blockquote><p><a href="https://identityassurance.blog.gov.uk/">GOV.UK Verify</a> is a good example of this. Government services that need the levels of assurance GOV.UK Verify offers are expected to use GOV.UK Verify.</p><p>That’s not because of any technical purism saying we should only have one, but it’s about a collection of other factors. Such as GOV.UK Verify’s architecture using a federated identity model to help drive industry innovation (people can choose from a number of identity providers to handle their initial registration when they sign into government services) and avoid creating a central database of personal data within a single supplier or within government. GOV.UK Verify has also been rigorously tested with users.</p><p>As time goes on and more common components emerge, we will need to think broadly about the best ways to ensure we can take advantage of platform effects, by concentrating demand in a way that lets us better take advantage of changing technical and commercial options and making things simpler for users.</p><p>Where the technical considerations are dominant we need to ensure that we are always creating “services so good people prefer to use them even where alternatives are available (or could be made by the team)”.</p><p>We have <a href="https://docs.google.com/presentation/d/1jj8mndjx0ZYXo0ZS9V9AZRlh0-enuZVYF1L44Myj80Q/edit?usp=sharing">shared our slide deck as an open google file</a>. We do not recommend using it as a stand-alone presentation and it is purely intended to give an introduction to our thinking at this time. If you want to discuss the presentation <a href="/service/mailto:architecture-requests@digital.cabinet-office.gov.uk">contact the technical architecture team.</a></p><p>All our work is done out in the open so to keep up to date with our way of thinking check out:</p><ul><li><a href="https://gdstechnology.blog.gov.uk/">GDS Technology blog</a></li><li><a href="https://github.com/alphagov">Github</a></li><li><a href="https://government.github.com/community/#uk-central">Github government community</a></li></ul><p><em>Originally published at </em><a href="https://governmenttechnology.blog.gov.uk/2016/07/05/introducing-our-architecture-approach-and-principles/"><em>governmenttechnology.blog.gov.uk</em></a><em> on July 5, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=30320c1da2f4" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>