<?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 Tash Norris on Medium]]></title>
        <description><![CDATA[Stories by Tash Norris on Medium]]></description>
        <link>https://medium.com/@tashjnorris?source=rss-b034f9156771------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*qOLOWWMnWK0LXqDL_HStgA.jpeg</url>
            <title>Stories by Tash Norris on Medium</title>
            <link>https://medium.com/@tashjnorris?source=rss-b034f9156771------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 21:25:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tashjnorris/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[Welcome to our space]]></title>
            <link>https://medium.com/@tashjnorris/https-medium-com-wia-london-welcome-to-our-space-c76bbcfc446c?source=rss-b034f9156771------2</link>
            <guid isPermaLink="false">https://medium.com/p/c76bbcfc446c</guid>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[appsec]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Tash Norris]]></dc:creator>
            <pubDate>Tue, 10 Sep 2019 15:09:15 GMT</pubDate>
            <atom:updated>2019-09-10T15:09:15.806Z</atom:updated>
            <content:encoded><![CDATA[<p>Back in March this year, a group of ladies met in a pub in Farringdon. We’d met at security meet-ups and networking events, bonded over red wine and decided to meet to debate whether all women spaces were needed in the info-sec London world.</p><p>Spoiler: We decided that a space where we focused on helping those that identify as female/ non-binary was needed but that we would endeavour to make sure that space welcomed anyone that wanted to be there. London <a href="https://www.meetup.com/London-Women-in-AppSec-WIA-Meetup-Group/">Women in AppSec (WIA)</a> was born. Influenced by our partnership with OWASP, our logo took shape, and the events started earlier this year.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/759/1*RT6J0bz76VuyLHmk1Rl_ow.jpeg" /></figure><p>So here I am! Ready to quickly introduce the team, our event and a little why on WIA.</p><h4>The Team</h4><p>Who are we?</p><p>We’re a right bunch, a mix of experiences and sectors, unique and yet similar. I’ll let them introduce themselves via this platform over the coming weeks but for now, their names and their twitter handles (how else do you understand someone but over 140 character dad jokes about software engineering? *Cat Banks). So in no particular order:</p><ul><li><a href="https://twitter.com/info_sec_girl">Lauren C</a></li><li><a href="https://twitter.com/ALL_Sec_Geek">Andra L</a></li><li><a href="https://twitter.com/CatTomBanks">Cat B</a></li><li><a href="https://twitter.com/TashJNorris">Me</a></li></ul><p>As you get to know each of us, through blog posts, <a href="https://www.meetup.com/London-Women-in-AppSec-WIA-Meetup-Group/">WIA meetups</a>, London security events and red wine you’ll learn that we all have some different reasons as to why we wanted a Women in AppSec London space, I’ll tell you mine a little further down..</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z8ZUuxHVPk48K_aWV34AjA.jpeg" /><figcaption>Low quality picture due to Malbec..</figcaption></figure><h4>What can you expect from a WIA event?</h4><p>Our events are informal, small to medium size and like many meetups, include food, drinks and an opportunity to learn something new. But here are a few other things that we do (these aren’t unique to us, just extra important):</p><ul><li>We only use venues that have well lit and well populated routes to public transport.</li><li>You can see the guest list (not sure if you’ll come if you don’t know anyone? Take a look — (we do however, allow nicknames to protect those that want/need it).</li><li>Don’t know anyone? Reach out to a member of the team, tell us a bit about you and we’ll introduce you to someone at the event we think you’d like to meet and would like to meet you.</li><li>We serve non-alcoholic drinks that aren’t water.</li><li>We try and live stream (this isn’t always possible, but we really, really try!).</li><li>We always do a panel at the end, so you have a chance to dive into topics and our panels will always contain a mix of experiences and gender identities.</li><li>Everyone is genuinely welcome. Gender isn’t binary. We embrace the differences between gender, sex and sexuality and work to better educate ourselves and each-other on the importance of diverse teams.</li></ul><p>Our events are a bit of a mix, but ultimately they usually have talks, networking and a panel and an opportunity to stick around afterwards somewhere nearby to catch up some more. Most importantly, we’re to have fun, learn and feel safe doing it. Our moto:</p><blockquote>“We just wanna AppSec and Chill”</blockquote><h3>Why on WIA?</h3><p>Towards the beginning of my career I went to a Security Conference with my then manager. We arrived early for the breakfast and coffee and rather than either a) both of us standing in the corner, or b) my manager leaving me to network with his friends he did something else (for which I am so very grateful). My manager was a social butterfly and well connected and so he took me around the room and introduced me — not to just his friends — but to people he thought I would find particularly interesting/ useful at that point in my career. Each introduction was meaningful, not just names, but facts, observations and insight into common problem statements — enough ‘fodder’ to allow me to return later in the day without my manager to continue the conversation.</p><p>The feeling of anxiety I had that morning — where I thought I was going to be left standing nervous and alone next to the pastries, summoning the courage to approach a group of (friendly) dudes in suits has not left me. So when the opportunity for WIA came along, it was, for me, the chance to:</p><ul><li>Create slightly smaller events (&lt;100 people) where there’s an informal and relaxed atmosphere</li><li>Encourage a range of experiences, levels and job types to all meet and learn from each other</li><li>Initiate meaningful introductions that persist to larger scale security/ tech meetups — encouraging more of us to represent at these meetings too</li><li>Promote diverse perspectives and create a space for first time speakers to feel ready to share their unique and valuable perspective in a safe and encouraging space.</li></ul><p><a href="https://www.meetup.com/London-Women-in-AppSec-WIA-Meetup-Group/">Join our meetup here</a> to learn about our next event.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c76bbcfc446c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Are we making our engineers Blue?]]></title>
            <link>https://medium.com/@tashjnorris/are-we-making-our-engineers-blue-ad3653db4275?source=rss-b034f9156771------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad3653db4275</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[appsec]]></category>
            <category><![CDATA[siem]]></category>
            <category><![CDATA[blue-team]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Tash Norris]]></dc:creator>
            <pubDate>Sun, 14 Jul 2019 21:05:47 GMT</pubDate>
            <atom:updated>2019-07-14T21:05:47.078Z</atom:updated>
            <content:encoded><![CDATA[<h4>Free and easy goodies to help bring more visibility and defensive capabilities to your product teams and AWS environment.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*5NA1WT14IC4v4ZTTISSIkA.png" /><figcaption>XKCD</figcaption></figure><p>When we consider our current challenge as security teams; the main one, the one for me that’s always been prevalent, is that we often have some kind of us and them (them being everyone else in the business)mentality. It’s often there in the business too — Security at one point or another has inadvertently caused a delay, or, not been present at all. This challenge, it stops us from scaling, we’re hindered and both security and product teams suffer for it.</p><p>Consider your development team, they’re delivering to production regularly, maybe daily, maybe, <a href="https://medium.com/refraction-tech-everything/how-netflix-works-the-hugely-simplified-complex-stuff-that-happens-every-time-you-hit-play-3a40c9be254b">every 11.7 seconds</a>. Perhaps your company hasn’t had a security team before, perhaps they still don’t, or perhaps it’s just really small or perhaps it’s huge. Regardless, in a world of continuous integration/deployment, of PaaS and SaaS offerings coming out of our ears, we all face the same problem. How do we do this at scale, securely, without impacting our ability to deliver efficiently by introducing a zillion gates and with all the features are customers want?</p><p>The following are some of my favourite free, easy or cheap goodies for your engineering toolbox. These are tools for you; software engineer, product owner, scrum master, project manager, accidental CISO, security person etc. Tools to help you own and manage security for your AWS environment, tools that help you <a href="https://securitybytes.io/blue-team-fundamentals-4ee226368b7b">be more blue team </a>than just a team.</p><ol><li><strong>Be Accessible and get to yes.</strong></li></ol><p>Being a great security team doesn’t mean always saying yes, but it does mean being accessible. Sometimes, you’re not going to be able to get comfortable with that new Wordpress site from marketing with approximately 34012 plugins enabled, or the 8736 third party javascript libraries tech want for tracking customers and other cool stuff on the new website. Not saying yes to stuff can be ok, but you’ve got to earn the trust of your product teams. Explain why, and help those teams get to yes. Take them on the journey of why MFA is powerful, throw in some demo’s on how easy it is to enumerate S3 buckets and find publicly available files and, if you can’t get comfortable with the proposed project/feature, <strong>help contribute to an alternative solution</strong>. Create numerous ways for your teams to ask you questions, create a wiki so you only have to answer each question once and hold regular open door meetings and demo sessions to show what you’re working on.</p><p><strong>2. Recon Scans</strong></p><p><a href="https://github.com/toniblyx/prowler">Prowler</a> is a cli tool that can give a yaml/json output (ELK stack friendly!) that gives you an idea of your security stance at an infrastructure/ environment level. Tools like Prowler can highlight gaps that could impact compliance (PCI/GDPR) and benchmark against the <a href="https://www.cisecurity.org/cis-benchmarks/">CIS standards</a>. You can write custom checks or use the built in ones.</p><p>Use it for: Getting the lay of the land + determining improvements over time/ determining how well new account security config script work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/868/1*qdduUM9oAkgqGTa6IjhGrw.png" /></figure><p>3. <strong>Threat Modelling</strong></p><p>I love threat modelling, this is my jam. For a good overview from the Godfather of threat modelling <a href="https://medium.com/u/642e68c4c9f3">Adam Shostack</a>, <a href="https://www.youtube.com/watch?v=Y3VQpg04vXo">watch this video</a>. FYI — threat models can (and should) be done by everyone involved in the project. And they can be quick! Got 15 minutes during story refinement? Run through these questions whilst utilising some cards from the <a href="https://www.microsoft.com/en-gb/download/details.aspx?id=20303">Elevation of Privilege card game</a>. Also, keep an eye out for some Cloudy EoP cards I’ll be launching soon ;)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_oth2eLfLLlFwoir" /><figcaption>Elevation of Privilege cards</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TZYzxwSjNgLyXbZFTiy0QA.png" /><figcaption>Cloudy EoP (coming soon)</figcaption></figure><p>4. <strong>Tests</strong></p><p>Write tests! I love tests. Why wouldn’t you write a test for your security requirements? We write tests to check for functionality, behaviour, load, why not write tests to validate against security requirements? One of my favourite projects out there for this is the <a href="https://www.owasp.org/index.php/OWASP_Cloud_Security_Project">OWASP Cloud Security Project</a> which utilises BDD to check for security issues.</p><p>You can write tests in whatever your existing tech stack is, they can run locally, part of a pipeline or be automated against your test environment. This can be everything from a local RegEx test to validate there are no keys before you commit to github, to validating your terraform/ cft ensures that S3 bucket utilises KMS encryption with the right key prior to deployment.</p><p>Tests!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gLnjQZ9E18P6rms1" /><figcaption>OWASP Cloud Security project</figcaption></figure><p>5. <strong>Preventative/ Redemptory Measures</strong></p><p>So you know your environment, you’ve been threat modelling to help mould your designs as they evolve and you’ve written tests (maybe even based on your threat model outcomes) to validate your builds as they go. What next?</p><p>Tools like Cloud Custodian can be used to either inform you on issues in your environment, prevent you from building against a standard you set and remediate present issues. Tools like this can be taken to the nuclear (but so very valuable level) — ‘Kill all the instances that don’t have tags!’ to ‘Send a SNS to the email tag to inform the user they have 7 days to get this S3 bucket encrypted’.</p><p>It’s useful, customisable and allows you to feel confident in not only what is happening in your environment, but what is possible in your environment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/725/1*5Qhfzze06bIhTY_uc22MDA.png" /><figcaption>Cloud Custodian</figcaption></figure><p><strong>6. Build a SIEM</strong></p><p>I think this one needs it’s own blog because there’s some custom python/ lambda magic required for multi-region log ingestion(thanks AWS for your lack of cross-region support between kinesis and everything else). The short of it is — there are a load of built-in AWS tools that help you to get more visibility on all the AWS environments you own. Utilising AWS Elasticsearch you can ingest data from sources like CloudTrail, Config and Guard Duty and then build visualisations and alerting on your environment. It’s pretty cool and an easy way to build initial capabilities if some of the cooler out the box tools are out of your price range. Or, if you just want to check your hubbo isn’t accidentally exposing all the dog pictures in S3 to the world via their wildly configured yoga API..</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zAdOZ74AOw9VA-pJ3TbIlQ.png" /><figcaption>ELK data created using Guard Duty sample findings.</figcaption></figure><p>There are a load more favs from me, you can catch a summary of some of the above tools and some additional goodies in this recording of my <a href="https://www.youtube.com/watch?v=vZwcRWIGKjQ">talk on making engineers into your extended blue team at OWASP Global here.</a></p><p>Thanks for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad3653db4275" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why I ran a lock-picking session in my office.]]></title>
            <link>https://medium.com/@tashjnorris/why-i-ran-a-lock-picking-session-in-my-office-a80d49d26565?source=rss-b034f9156771------2</link>
            <guid isPermaLink="false">https://medium.com/p/a80d49d26565</guid>
            <category><![CDATA[lock-picking]]></category>
            <category><![CDATA[appsec]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Tash Norris]]></dc:creator>
            <pubDate>Thu, 04 Jul 2019 13:28:38 GMT</pubDate>
            <atom:updated>2019-07-04T13:28:38.201Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>“What an opportunity to demonstrate the power of collaboration between security and engineering when building a product.”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GKjp1TvrhxwpbXi5q7sULg.jpeg" /></figure><h4>Head to any major security conference, be it B-Sides, BlackHat or DefCon you’re likely to come across a lock picking village. But why?</h4><p>Aside from the fact that it’s good to just sit and be still (see n number of posts on mindfulness), I truly believe lock picking provides a good ice breaker and an avenue to talk about the importance of security.</p><p>Take your standard padlocks (4 pin tumbler locks) are common and meet functional requirements, they’re built for a specific threat model and perform their job well. The padlocks though, are really easy to pick, the tools are easily accessible and tutorials are all over the internet. To me, they’re a good example of building purely to one set of (functional) requirements, and only testing against one set of (functional) requirements. The product works, it sells but it’s not secure. In addition, introducing security now requires a complete re-design of the mechanics, hugely costly.</p><h4><strong>Encourages shifting security left</strong></h4><p>When I run these lock picking sessions I talk about the power of having security (and other SME’s) engaged right from the beginning. We can provide design support, review architectures, test as we go and become trusted advisors. We can also talk about Threat Models, and how security can support even at the design and ideation phase. Threat vectors, the threat landscape and threat actors. For example, in London, a strong 4 pin padlock protecting my bike is more at risk from bolt cutters than lock picks so that should dictate how I decide to protect my asset. That might not be the case everywhere.</p><h4>Introduces the concept of security testing</h4><p>Not just pen testing, but actually testing the security of a product at every stage. When we lock pick we have an opportunity to discuss the mechanics of the lock and why it’s easy to pick, even when we change to other tumbler style locks. Introducing the power of a security engagement in ensuring the vulnerability wouldn’t be passed on to other implementations of the mechanics (hey spring loaded locks). We can draw parallels to discussing engineering patterns and how we can introduce security tests in the same way we use functional/ load/ requirements testing to validate the presence — or fix — of vulnerabilities continuously (e.g. every build).</p><h4>Builds (security team) brand awareness</h4><p>Lock picking sessions are great advertising tools too, I do some up front advertising on Slack, in office newsletters and via word of mouth but there’s nothing like taking over one of the tables in a communal area to catch that drive by traffic with “wanna learn how to pick a lock?”. These types of sessions are disarming, people are intrigued, they want to learn more and now, as they take time learning how to hold the picks and use them, you have a captive audience to talk about security with.</p><p>Most importantly, they know who you are now. You are a contact in a team they may have known little about, a resource they can use to ask questions of, look to for advice or even confide in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*U51FvgomoRFNLBUD" /></figure><p>It’s totally legal, cheaper than running multiple team lunches and good fun. Why not try it?</p><p>As an FYI the best picks I’ve used are by <a href="https://www.madbobpicks.co.uk/">MadBob</a>, these don’t tend to break easily and are much nicer to hold than other cheaper brands. However, there’s nothing wrong with using a cheaper set on <a href="https://www.amazon.co.uk/Lockpicking-22-Piece-Difficulties-Professional-Locksmiths/dp/B07BKN2S3S/ref=asc_df_B07BKN2S3S/?tag=googshopuk-21&amp;linkCode=df0&amp;hvadid=223170773229&amp;hvpos=1o1&amp;hvnetw=g&amp;hvrand=17939161839583517520&amp;hvpone=&amp;hvptwo=&amp;hvqmt=&amp;hvdev=c&amp;hvdvcmdl=&amp;hvlocint=&amp;hvlocphy=1006886&amp;hvtargid=pla-436164894420&amp;psc=1">Amazon</a>, just be prepared for them to break!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a80d49d26565" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using threat models for incidents (and how incidents helped me like attack trees)]]></title>
            <link>https://medium.com/@tashjnorris/using-threat-models-for-incidents-and-how-incidents-helped-me-like-attack-trees-a27eb65f9039?source=rss-b034f9156771------2</link>
            <guid isPermaLink="false">https://medium.com/p/a27eb65f9039</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[soc]]></category>
            <category><![CDATA[appsec]]></category>
            <category><![CDATA[threat-model]]></category>
            <dc:creator><![CDATA[Tash Norris]]></dc:creator>
            <pubDate>Mon, 17 Jun 2019 17:21:00 GMT</pubDate>
            <atom:updated>2019-06-18T13:23:15.293Z</atom:updated>
            <content:encoded><![CDATA[<h4>A run down on how your Security Engineering / Application Security teams can support your incident process.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/803/1*BnZPTPsnTgardKinlHkipQ.png" /></figure><blockquote>My favourite part; when we’re remediating issues during incidents we’re not just fixing the root cause, but also identifying other potential causes and remediating those too.</blockquote><h4>Threat Modeling</h4><p>I really enjoy talking about threat models, they’re kind of like art to me. There are so many different ways to do them, they can look so different and they all provide the owners a unique type of value. However, the one type of modelling I’ve never really got, is attack trees.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*YawI13k4Zssz09v2-J50aA.gif" /><figcaption>Example attack tree, ref Bruce Schneier.</figcaption></figure><p>I understand how to use them, but I’ve never really understood where they fit in a agile threat modelling world. For me, personally, they’ve never really fit into the threat modelling flow, when we have a delivery team together and we’re working through a new feature, following a 4 question structure (+ STRIDE) has allowed for the progression of quick but solid models.</p><p>A reminder on the 4 questions (ref: <a href="https://medium.com/u/642e68c4c9f3">Adam Shostack</a>):</p><ul><li>What are you doing?</li><li>What can go wrong?</li><li>What can you do about it?</li><li>Did you do a good job?</li></ul><p>This structure serves our teams and I well during threat models, we’re able to scale it between quick small feature models, through to much longer evaluations of entire services. We’ve even started to work the questions into some teams definitions of done (future blog post). However, in the last 6 months I’ve been experimenting with using attack tree’s in certain scenarios, and so far, they’re working really well.</p><h3>Intro the incident.</h3><p>We all experience incidents, of different scales and different causes. From infected hosts to clicked links on phishing attempts to worse, we’ve seen them all in the news, on reddit, in the Register and probably even in person. So when we go into full incident response mode, how can threat modelling help your teams? Here’s my 2¢.</p><p>Whilst your SOC team/ IR folk are running their playbook (if you’re lucky enough to have one for your particular scenario) here’s the flow our SecEng/AppSec team take to support.</p><h4>1. Understand the what</h4><p>Pretty straight forward for your normal threat model flow, this is the recap of what you’re building. Except, in incident flow, we’re focusing on what went wrong. It may be limited information at first, but the point of this stage is to understand the initial issue and the scope.</p><p>Don’t underestimate how useful these diagrams can be for teams making decisions during incidents, but DON’T spend too long on it, the intent is to ensure common understanding, not update documentation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/757/1*NLnBVZ6u8Or96pUbVIzxZQ.png" /><figcaption>Example diagram highlighting service impacted, relevant data flows and trust boundaries.</figcaption></figure><h4>2. Determine what could have gone wrong</h4><p>Using just the context of the incident we look at what can go wrong, and this is where I’ve been using attack tree’s.</p><p>First off, I cover potential causes, pulling out any potentials and in this case I follow a common idiom in security; Trust, but verify. This is where you’ll see I’ve either ruled out or accepted certain possibilities and marked them with either a I(mpossible) or P(ossible).</p><blockquote>Why do I cover the impossible? Because I want to write tests, tests to validate it’s still impossible, and tests that can continuously run, to validate that impossibility through every production change.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/803/1*BnZPTPsnTgardKinlHkipQ.png" /><figcaption>Example incident attack tree</figcaption></figure><p>The next round is pulling some characteristics that would allow that vector to be true (or rather, present vulnerabilities that would allow a vector to be exploited). This then allows me to get closer to a possible cause.</p><p>Finally tests, these allow validation of the vulnerability and ultimately the exploit path.</p><h4>3. Keep the SOC team in the loop</h4><p>The reason we do the attack tree is to help guide investigations during incidents. Occasionally (and not always — which importantly, means this isn’t always required) the cause of the incident isn’t clear, so the aim of the attack tree here is to continually guide our SOC team.</p><p>Thus, as we identify characteristics/ vulns for a potential attack vector we’ll be liaising with the SOC team to guide their search through their various sources. The aim is to help guide the investigation as quickly as possible, with the intent of discovering and remediating the cause quickly.</p><h4>4. Evolve the model and update playbooks</h4><p>What’s interesting about this approach is that we can use it to not only update the threat model for the service in question but also the playbooks. We’ve potentially discovered a couple of other attack vectors and now we can write tests to continuously test whether those vectors are still im|possible.</p><p>My favourite part; when we’re remediating issues during incidents we’re not just fixing the root cause, but also identifying other potential causes and remediating those too. Sometimes, there’s just no better way to understand a service than to manage an incident for it..</p><p>Do you use attack trees? Let me know.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a27eb65f9039" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wine and Py; Using Deep Work to learn a new skill]]></title>
            <link>https://medium.com/@tashjnorris/wine-and-py-using-deep-work-to-learn-a-new-skill-739fb52d89ef?source=rss-b034f9156771------2</link>
            <guid isPermaLink="false">https://medium.com/p/739fb52d89ef</guid>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Tash Norris]]></dc:creator>
            <pubDate>Sun, 10 Feb 2019 20:08:23 GMT</pubDate>
            <atom:updated>2019-02-10T20:08:23.597Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ADVDIJqTJDFhBci_Gycarg.png" /></figure><p>I recently read a blog from Azeria over at azeria-labs.com (<a href="http://www.twitter.com/Fox0x01">@Fox0x01</a> on Twitter) on <a href="https://azeria-labs.com/the-importance-of-deep-work-the-30-hour-method-for-learning-a-new-skill/">Deliberate Practice and Deep Work</a> and it really stuck with me. To badly paraphrase; it’s the idea that by investing solid blocks of time (+4 hours but with regular breaks), many times (total of 30 hours minimum), you will increase your chances in learning/ developing a new skill well.</p><p>I’ve been wanting to expand on my Python skills for a little while now but struggled with retaining information when only jumping into the topic for 15–30 minutes at a time. So I thought I’d apply the deep work tactic described in Azeria’s blog to increase my Python knowledge. Now I’ve not yet hit the 30 hour mark but I am seeing benefits already so I thought I’d share some tactics that worked for me, incase you are considering learning a new skill and want to try the approach.</p><p>1. 2–4 hour blocks worked best</p><p>In the blog Azeria mentions 4 hour blocks (with regular breaks). This doesn’t work for my schedule and I actually find I work better if I acknowledge that I’m easily distracted at home and work in blocks of time where I know I have space to cater to the distractions. Basically, if I have 3 hours free then I allocate 2 hours to project time and 1 hour to being distracted by my dog/ mobile device/ Amazon etc.</p><p>2. Minimum 2 hours</p><p>At a minimum I need 2 hours on the project to be productive and to retain data well. Now I’ve been baselining and I tend to hit my good productive spot pretty early on, around the 15 minute of solid concentration mark but I’ve found that when it comes to data retention, I need the 2 solid hours. I’d recommending focusing not only on how long it takes you to hit ‘the zone’ but also how good your information retention is (I do tend to repeat tasks within that 2 hours to help with this).</p><p>3. Ambient noise is a must!</p><p>I cannot sit in silence. If I sit in silence then I feel an unquenchable desire to make noise. A lot of noise. So I need ambient sounds, not tv/ movies (because distractions) but usually classical music (Einaudi is a fav) or dance music (think <a href="https://soundcloud.com/duttymagic/fatboy-slim-recorded-live-at">Ibiza Fat Boy Slim remix</a>). My sweet spot though is if I can get to a bar or coffee shop, I find the ambient noise is perfect for stopping the desire to make loud noises but enough to cover my mini cheers when I get something to execute successfully.</p><p>4. Be specific .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/516/0*R9Zy3G1QKJ0Ja_7_" /></figure><p>Have a task, with a desired outcome at the start. This can be vague/ fluffy ‘e.g. — Learn about compute in Azure and build something’ and can get more specific as your project evolves e.g. ‘Submit Alexa skill’ or ‘Write an Alexa skill that can call an external API’. Having a task with a desired outcome will help you to measure success and whether your time frames are working. Don’t forget to be realistic, you are learning and don’t be disheartened by uncompleted tasks as they equal experience.</p><p>5. Relax</p><p>Learning/ being productive is just not going to work if I’m stressed/ have a bit to do list as that distraction will seep in so keep your priorities in check, appreciate that life gets in the way sometimes and know that free time should sometimes just be free time and not anything else.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/286/0*ncTgInSJQjM2Twmz" /></figure><p>So how did I actually get started? Well I’m on a SANSFIRE course (Defensible Security Architecture — SEC530) and often my days finish at 5 but the evening talks don’t start until 7:15 so this felt like a great opportunity to crack out 2 hour blocks each day and give this a go. I’ve been writing an Alexa skill in Python and re-writing powershell scripts in python (pretend hacker skillz) and have really enjoyed my evenings. I miss the dog and hubby but I’ve been learning a lot and I’m on track for that free tee from AWS for deploying my (serverless) <a href="https://developer.amazon.com/en-gb/alexa-skills-kit/alexa-developer-skill-promotion">Amazon skill in July</a> (check out my<a href="https://github.com/tashjb/suggest-a-flix-alexa"> Github </a>to see progress).</p><p>Next steps? I plan on being a bit extra (inspired by my husbands current side project) and I’m building a pipeline to deploy my skill, complete with security testing using open source tools and I’ve got some plans for my next next project, which will take the form of some security pipeline modules and whether I start breaking the build..</p><p>[Optional step 6 == wine | beer]</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=739fb52d89ef" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>