[{"data":1,"prerenderedAt":3459},["ShallowReactive",2],{"application-flags":3,"navbar":7,"always-visible-banner":36,"navbar-about-highlight":108,"navbar-resource-highlight":182,"blog/protect-your-data-across-all-your-apps-even-the-ones-employees-use-without":226},[4],{"name":5,"enabled":6},"maintenanceMode",false,[8],{"createdDate":9,"id":10,"name":11,"modelId":12,"published":13,"query":14,"data":15,"variations":20,"lastUpdated":21,"firstPublished":22,"testRatio":23,"createdBy":24,"lastUpdatedBy":25,"folders":26,"meta":27,"rev":35},1742208588866,"1c7a4e423bf54ac1a328bb4063459ef2","Banner","1c6207a5f24948ab82d4a0b17f251193","published",[],{"type":16,"url":17,"text":18,"link":19},"web-banner","https://pushsecurity.com/resources/browser-attacks-report","Get our latest report analyzing browser attack techniques in 2026",{},{},1774258294825,1742208637545,1,"CydmZnOWU1XuAaLhEDCoYNM4Z8W2","jKjF9r5jcvXU8tzZEfFQm31Iyvr2",[],{"kind":28,"lastPreviewUrl":29,"breakpoints":30,"hasAutosaves":34},"data","",{"xsmall":31,"small":32,"medium":33},320,640,768,true,"ga0kpxjhh76",{"createdDate":37,"id":38,"name":39,"modelId":40,"published":13,"stageModifiedSincePublish":6,"query":41,"data":42,"variations":97,"lastUpdated":98,"firstPublished":99,"testRatio":23,"createdBy":100,"lastUpdatedBy":101,"folders":102,"meta":103,"rev":107},1774965361051,"fd266d0172cc47429be7ad10f48c99ad","always visible banner","0678d178ec8b41efb8a23c09dba7874d",[],{"ctaText":43,"text":44,"url":29,"blocks":45,"state":93},"ewrererw","testrfesssssssssss",[46,73,81],{"@type":47,"@version":48,"id":49,"component":50,"responsiveStyles":63},"@builder.io/sdk:Element",2,"builder-ca12c06a52de41d7b8743da53118cd38",{"name":51,"tag":51,"options":52,"isRSC":62},"TopBannerContent",{"text":53,"ctaText":54,"url":55,"mainText":56,"cta":59},"New Webinar Series: Join John Hammond, Troy Hunt, and Matt Johansen for the State of Browser Attacks","Save Your Spot","https://pushsecurity.com/webinar/state-of-browser-security",{"content":57,"fontSize":58},"\u003Cp>Meet Push's browser security experts at BlackHat 2026.\u003C/p>","text-base",{"content":60,"fontSize":58,"url":61},"\u003Cp>Book a meeting →\u003C/p>","https://pushsecurity.com/events/blackhat-2026-meeting",null,{"large":64},{"display":65,"flexDirection":66,"position":67,"flexShrink":68,"boxSizing":69,"marginTop":70,"marginBottom":70,"fontSize":71,"fontWeight":72},"flex","column","relative","0","border-box",".56rem","1.125rem","700",{"@type":47,"@version":48,"id":74,"component":75,"responsiveStyles":79},"builder-a2e1f4b9f30b464bb814d7f5de5b0aa7",{"name":76,"options":77,"isRSC":62},"Custom Code",{"code":78,"scriptsClientOnly":6},"\u003Cstyle>\n  .top-banner.bg-web-orange{background:rgb(114, 79, 255);}\n\u003C/style>\n",{"large":80},{"display":65,"flexDirection":66,"position":67,"flexShrink":68,"boxSizing":69},{"id":82,"@type":47,"tagName":83,"properties":84,"responsiveStyles":88},"builder-pixel-o503s4fpvk","img",{"src":85,"aria-hidden":86,"alt":29,"role":87,"width":68,"height":68},"https://cdn.builder.io/api/v1/pixel?apiKey=f3a1111ff5be48cdbb123cd9f5795a05","true","presentation",{"large":89},{"height":68,"width":68,"display":90,"opacity":68,"overflow":91,"pointerEvents":92},"block","hidden","none",{"deviceSize":94,"location":95},"large",{"path":29,"query":96},{},{},1783541846936,1774968080803,"ST0tXQM8slWpFrmioqKHmENB2qe2","kYgMv6WsbvfmlOUYqR2SFwGzw6e2",[],{"kind":104,"lastPreviewUrl":105,"hasLinks":6,"breakpoints":106,"hasErrors":6,"hasAutosaves":6},"component","https://pushsecurity.com/?builder.space=f3a1111ff5be48cdbb123cd9f5795a05&builder.user.permissions=read%2Ccreate%2Cpublish%2CeditDesigns%2CeditLayouts%2CeditLayers%2CeditContentPriority%2CeditFolders%2CcreateProjects%2CsendPullRequests&builder.user.role.name=Designer&builder.user.role.id=creator&builder.cachebust=true&builder.preview=always-visible-banner&builder.noCache=true&builder.allowTextEdit=true&__builder_editing__=true&builder.overrides.always-visible-banner=fd266d0172cc47429be7ad10f48c99ad&builder.overrides.fd266d0172cc47429be7ad10f48c99ad=fd266d0172cc47429be7ad10f48c99ad&builder.options.locale=Default",{"xsmall":31,"small":32,"medium":33},"kyujw1aptq",[109,145],{"createdDate":110,"id":111,"name":112,"modelId":113,"published":13,"stageModifiedSincePublish":6,"query":114,"data":115,"variations":138,"lastUpdated":139,"firstPublished":140,"testRatio":23,"createdBy":24,"lastUpdatedBy":24,"folders":141,"meta":142,"rev":144},1776247359804,"9136a8f18b3b4a6ba29b8653a99372b1","testimonial-inductive-automation","20d9eaa352304613b3d1a794b400703d",[],{"link":116,"type":117,"testimonialLink":118,"testimonial":119},{},"testimonial","/customer-stories/inductive-automation",{"@type":120,"id":121,"model":117,"value":122},"@builder.io/core:Reference","f028f2b685bb47cd8bf9e82a26dd5a79",{"query":123,"folders":124,"createdDate":125,"id":121,"name":126,"modelId":127,"published":13,"data":128,"variations":132,"lastUpdated":133,"firstPublished":134,"testRatio":23,"createdBy":100,"lastUpdatedBy":100,"meta":135,"rev":137},[],[],1735823466309,"We found Push to be more accurate when compared to competitors and the browser agent offered features that others couldn’t match.","42035571a56940ac98bff4544aa79aa5",{"author":129,"jobTitle":130,"quote":126,"image":131},"Jason Waits","\u003Cp>CISO at Inductive Automation\u003C/p>","https://cdn.builder.io/api/v1/image/assets%2Ff3a1111ff5be48cdbb123cd9f5795a05%2Ff04c0c0689ce4a89ac0f0708d78c0a07",{},1735910703862,1735823501152,{"kind":28,"lastPreviewUrl":29,"breakpoints":136,"hasAutosaves":34},{"small":32,"medium":33},"e8bsg4qrgtu",{},1776247404986,1776247404973,[],{"breakpoints":143,"kind":28,"lastPreviewUrl":29,"hasAutosaves":6},{"xsmall":31,"small":32,"medium":33},"g9lqcuxphw7",{"createdDate":146,"id":147,"name":148,"modelId":113,"published":13,"meta":149,"stageModifiedSincePublish":6,"query":151,"data":152,"variations":178,"lastUpdated":179,"firstPublished":180,"testRatio":23,"createdBy":24,"lastUpdatedBy":24,"folders":181,"rev":144},1776255761419,"05a9322735fc427db12e2740e4302300","Report: 2026 Browser Attack Techniques",{"breakpoints":150,"kind":28,"lastPreviewUrl":29,"hasAutosaves":6},{"xsmall":31,"small":32,"medium":33},[],{"testimonial":153,"link":172,"type":175,"title":148,"description":176,"image":177},{"@type":120,"id":154,"model":117,"value":155},"192acbb1f9ca4cac918c0ec435a8bae3",{"query":156,"folders":157,"createdDate":158,"id":154,"name":159,"modelId":127,"published":13,"data":160,"variations":166,"lastUpdated":167,"firstPublished":168,"testRatio":23,"createdBy":100,"lastUpdatedBy":24,"meta":169,"rev":171},[],[],1728981467463,"Push does for identity what CrowdStrike did for the endpoint",{"video":161,"jobTitle":162,"author":163,"qoute":29,"quote":164,"image":165},"https://cdn.builder.io/o/assets%2Ff3a1111ff5be48cdbb123cd9f5795a05%2F8b30e8ca50064058bbaef0f3c6164575%2Fcompressed?apiKey=f3a1111ff5be48cdbb123cd9f5795a05&token=8b30e8ca50064058bbaef0f3c6164575&alt=media&optimized=true","\u003Cp>Deputy CISO at Microsoft\u003C/p>\u003Cp>Former LinkedIn, Slack, Palantir\u003C/p>","Geoff Belknap","Push does for identity what CrowdStrike did for the endpoint.","https://cdn.builder.io/api/v1/image/assets%2Ff3a1111ff5be48cdbb123cd9f5795a05%2F748f0ad0a5064a00a13f4721fcc8dea1",{},1742902158597,1728981782923,{"kind":28,"lastPreviewUrl":29,"breakpoints":170,"hasAutosaves":34},{"small":32,"medium":33},"ulhc0im1hfo",{"text":173,"url":174},"Download now","/resources/browser-attacks-report","resource","Learn about the latest techniques being used in the wild.","https://cdn.builder.io/api/v1/image/assets%2Ff3a1111ff5be48cdbb123cd9f5795a05%2F7b4a5ebf81d64e8c9d7fc35f6c96c4a9",{},1776255810913,1776255810900,[],[183,205],{"createdDate":184,"id":185,"name":148,"modelId":186,"published":13,"meta":187,"stageModifiedSincePublish":6,"query":189,"data":190,"variations":200,"lastUpdated":201,"firstPublished":202,"testRatio":23,"createdBy":24,"lastUpdatedBy":24,"folders":203,"rev":204},1776256900280,"1f429607996e4e5fae8fe3f9b9610e55","4829faa81e7c4ee8bd2d000e160e8d3c",{"breakpoints":188,"kind":28,"lastPreviewUrl":29,"hasAutosaves":6},{"xsmall":31,"small":32,"medium":33},[],{"testimonial":191,"link":199,"type":175,"title":148,"description":176,"image":177},{"@type":120,"id":154,"model":117,"value":192},{"query":193,"folders":194,"createdDate":158,"id":154,"name":159,"modelId":127,"published":13,"data":195,"variations":196,"lastUpdated":167,"firstPublished":168,"testRatio":23,"createdBy":100,"lastUpdatedBy":24,"meta":197,"rev":171},[],[],{"video":161,"jobTitle":162,"author":163,"qoute":29,"quote":164,"image":165},{},{"kind":28,"lastPreviewUrl":29,"breakpoints":198,"hasAutosaves":34},{"small":32,"medium":33},{"text":173,"url":174},{},1776256937553,1776256937540,[],"xggsv10v1q9",{"createdDate":206,"id":207,"name":208,"modelId":186,"published":13,"stageModifiedSincePublish":6,"query":209,"data":210,"variations":220,"lastUpdated":221,"firstPublished":222,"testRatio":23,"createdBy":24,"lastUpdatedBy":24,"folders":223,"meta":224,"rev":204},1776256949234,"ce043785b71b4ece98eac811ecf4ba10","inductive-automation",[],{"link":211,"type":117,"testimonial":212,"testimonialLink":118},{},{"@type":120,"id":121,"model":117,"value":213},{"query":214,"folders":215,"createdDate":125,"id":121,"name":126,"modelId":127,"published":13,"data":216,"variations":217,"lastUpdated":133,"firstPublished":134,"testRatio":23,"createdBy":100,"lastUpdatedBy":100,"meta":218,"rev":137},[],[],{"author":129,"jobTitle":130,"quote":126,"image":131},{},{"kind":28,"lastPreviewUrl":29,"breakpoints":219,"hasAutosaves":34},{"small":32,"medium":33},{},1776256974140,1776256974130,[],{"breakpoints":225,"kind":28,"lastPreviewUrl":29,"hasAutosaves":6},{"xsmall":31,"small":32,"medium":33},{"id":227,"title":228,"authorsCollection":229,"content":237,"extension":1946,"faqItemsCollection":1947,"faqTitle":62,"featured":6,"hashTags":62,"meta":1949,"metaTitle":1950,"ogImage":1951,"publishedDate":1953,"relatedBlogPostsCollection":1954,"slug":3433,"stem":3434,"subtitle":62,"summary":3435,"synopsis":3446,"sys":3447,"tagsCollection":3450,"__hash__":3458},"blog/blog/protect-your-data-across-all-your-apps-even-the-ones-employees-use-without.json","The no-jargon guide to solving shadow SaaS ",{"items":230},[231],{"fullName":232,"firstName":233,"jobTitle":234,"profilePicture":235},"Jacques Louw","Jacques","Co-founder / CRO",{"url":236},"https://images.ctfassets.net/y1cdw1ablpvd/39m8bektV23lnCRcEq0G8h/2a08f6276a50744f1a4b499b273f6bb2/Push_Founders_at_Cahoots_October_28_2022_by_Doug_Coombe-21.jpg",{"json":238,"links":1815},{"nodeType":239,"data":240,"content":241},"document",{},[242,251,278,285,292,305,312,319,364,371,378,385,392,399,406,412,435,442,449,456,463,470,579,586,593,600,613,620,628,635,642,648,655,662,669,675,683,690,697,704,711,718,725,731,738,745,752,759,765,772,815,821,828,851,858,881,888,895,902,909,916,1028,1034,1041,1050,1057,1064,1071,1078,1085,1092,1098,1105,1112,1132,1139,1146,1153,1159,1166,1173,1180,1213,1220,1227,1234,1241,1248,1255,1262,1269,1276,1283,1326,1333,1339,1361,1368,1375,1382,1389,1396,1403,1410,1417,1424,1431,1438,1445,1452,1494,1501,1508,1524,1540,1547,1554,1561,1568,1575,1582,1589,1596,1603,1609,1616,1623,1629,1636,1643,1650,1657,1666,1673,1680,1743,1749,1756,1763,1769,1776,1783,1790,1796,1808],{"nodeType":243,"data":244,"content":245},"heading-1",{},[246],{"nodeType":247,"value":248,"marks":249,"data":250},"text","Introduction",[],{},{"nodeType":252,"data":253,"content":254},"paragraph",{},[255,259,274],{"nodeType":247,"value":256,"marks":257,"data":258},"Here’s hoping you’ve read my previous blog: ",[],{},{"nodeType":260,"data":261,"content":267},"entry-hyperlink",{"target":262},{"sys":263},{"id":264,"type":265,"linkType":266},"3ic4Ok5kwIE8UuUClhPFPn","Link","Entry",[268],{"nodeType":247,"value":269,"marks":270,"data":273},"SaaS sprawl isn't a problem - if you completely change your approach",[271],{"type":272},"italic",{},{"nodeType":247,"value":275,"marks":276,"data":277},"If you haven’t, the key takeaway of that piece is that SaaS vendors have changed how software is adopted into a business. Now, the majority of SaaS vendors build their products on a product-led growth model - which simply means they want users (your employees) to self-adopt their apps, start using them (and integrating with your data to do so), and become a useful tool for the employee. ",[],{},{"nodeType":252,"data":279,"content":280},{},[281],{"nodeType":247,"value":282,"marks":283,"data":284},"Vendors want to bypass the security and IT software-onboarding processes we’d all gotten used to in the past. They know if they prove their tool is valuable with the user from the start, it’s much easier and quicker for them to gain traction and customers than it was waiting for security and IT teams to audit (and potentially refuse) their software.",[],{},{"nodeType":252,"data":286,"content":287},{},[288],{"nodeType":247,"value":289,"marks":290,"data":291},"This self-adoption has turned the product-adoption process on its head - leaving security and IT teams blind to which apps sensitive company data is flowing into. ",[],{},{"nodeType":252,"data":293,"content":294},{},[295,301],{"nodeType":247,"value":296,"marks":297,"data":300},"How do you make sure your data stays secure in this new software-adoption flow?",[298],{"type":299},"bold",{},{"nodeType":247,"value":302,"marks":303,"data":304}," ",[],{},{"nodeType":252,"data":306,"content":307},{},[308],{"nodeType":247,"value":309,"marks":310,"data":311},"In this book, we’ll offer some practical guidance on how to manage supply chain risk without slowing down the business.",[],{},{"nodeType":252,"data":313,"content":314},{},[315],{"nodeType":247,"value":316,"marks":317,"data":318},"We’ll cover how to:",[],{},{"nodeType":320,"data":321,"content":322},"unordered-list",{},[323,334,344,354],{"nodeType":324,"data":325,"content":326},"list-item",{},[327],{"nodeType":252,"data":328,"content":329},{},[330],{"nodeType":247,"value":331,"marks":332,"data":333},"Split SaaS risk into supply chain risk and account compromise risk so you can tackle them in parallel.",[],{},{"nodeType":324,"data":335,"content":336},{},[337],{"nodeType":252,"data":338,"content":339},{},[340],{"nodeType":247,"value":341,"marks":342,"data":343},"Tap into the SaaS self adoption process in real time so you can manage supply chain risk without being a blocker. ",[],{},{"nodeType":324,"data":345,"content":346},{},[347],{"nodeType":252,"data":348,"content":349},{},[350],{"nodeType":247,"value":351,"marks":352,"data":353},"How to prioritize account security controls and prevent the most common SaaS attacks.",[],{},{"nodeType":324,"data":355,"content":356},{},[357],{"nodeType":252,"data":358,"content":359},{},[360],{"nodeType":247,"value":361,"marks":362,"data":363},"Better choose a SaaS security product by looking at the data these tools are built on.",[],{},{"nodeType":243,"data":365,"content":366},{},[367],{"nodeType":247,"value":368,"marks":369,"data":370},"\nThe two halves of SaaS Security",[],{},{"nodeType":252,"data":372,"content":373},{},[374],{"nodeType":247,"value":375,"marks":376,"data":377},"It’s useful to consider the shared-responsibility model to understand the two main parts of SaaS security. Consider the following diagram that shows the customer’s responsibility in various as-a-Service models:",[],{},{"nodeType":379,"data":380,"content":384},"embedded-entry-block",{"target":381},{"sys":382},{"id":383,"type":265,"linkType":266},"17rMTpxgCAU5ropjkGIIjK",[],{"nodeType":252,"data":386,"content":387},{},[388],{"nodeType":247,"value":389,"marks":390,"data":391},"In this SaaS model, we’re delegating a lot of responsibility for security to the vendor. That’s great because it takes the load off of us - the customer - and the vendor is better placed to secure their software. However, this requires far greater trust in the vendor.",[],{},{"nodeType":252,"data":393,"content":394},{},[395],{"nodeType":247,"value":396,"marks":397,"data":398},"While we’re offloading a lot to the SaaS vendor, we aren’t offloading everything. You still need to take care of your responsibilities, limited as they are!",[],{},{"nodeType":252,"data":400,"content":401},{},[402],{"nodeType":247,"value":403,"marks":404,"data":405},"This gets us to the two halves of SaaS security:",[],{},{"nodeType":379,"data":407,"content":411},{"target":408},{"sys":409},{"id":410,"type":265,"linkType":266},"ToDXz2MBbEygwtJjiIKRX",[],{"nodeType":320,"data":413,"content":414},{},[415,425],{"nodeType":324,"data":416,"content":417},{},[418],{"nodeType":252,"data":419,"content":420},{},[421],{"nodeType":247,"value":422,"marks":423,"data":424},"Supply chain risk - can you trust the product, the vendor, and the vendor’s sub processors to secure your data and the access you grant them to your systems?",[],{},{"nodeType":324,"data":426,"content":427},{},[428],{"nodeType":252,"data":429,"content":430},{},[431],{"nodeType":247,"value":432,"marks":433,"data":434},"Customer responsibility - how can you make sure you’re using the product securely? You’ll need to focus here specifically on account security and application configuration.",[],{},{"nodeType":252,"data":436,"content":437},{},[438],{"nodeType":247,"value":439,"marks":440,"data":441},"Let’s look at each of these in turn.",[],{},{"nodeType":243,"data":443,"content":444},{},[445],{"nodeType":247,"value":446,"marks":447,"data":448},"Manage supply-chain risk",[],{},{"nodeType":252,"data":450,"content":451},{},[452],{"nodeType":247,"value":453,"marks":454,"data":455},"Security due diligence or app risk assessments are typically how you answer the question “should we use this app?” These are standard processes for most organizations as part of a software procurement process.",[],{},{"nodeType":252,"data":457,"content":458},{},[459],{"nodeType":247,"value":460,"marks":461,"data":462},"However, security no longer controls the cadence of software adoption - employees are self-adopting the tools they want without oversight - so we must work to find serious risks as soon as possible once the self-adoption process begins (normally by the first employee creating an account on the app).",[],{},{"nodeType":252,"data":464,"content":465},{},[466],{"nodeType":247,"value":467,"marks":468,"data":469},"The security relevant areas of this risk assessment can typically be broken into:",[],{},{"nodeType":320,"data":471,"content":472},{},[473,506,569],{"nodeType":324,"data":474,"content":475},{},[476,483],{"nodeType":252,"data":477,"content":478},{},[479],{"nodeType":247,"value":480,"marks":481,"data":482},"Product risk ",[],{},{"nodeType":320,"data":484,"content":485},{},[486,496],{"nodeType":324,"data":487,"content":488},{},[489],{"nodeType":252,"data":490,"content":491},{},[492],{"nodeType":247,"value":493,"marks":494,"data":495},"Does the product have the necessary security features (MFA, SSO, etc.) to protect our data, and ",[],{},{"nodeType":324,"data":497,"content":498},{},[499],{"nodeType":252,"data":500,"content":501},{},[502],{"nodeType":247,"value":503,"marks":504,"data":505},"Has the product security been technically verified (e.g. through a third party penetration test)?",[],{},{"nodeType":324,"data":507,"content":508},{},[509,516],{"nodeType":252,"data":510,"content":511},{},[512],{"nodeType":247,"value":513,"marks":514,"data":515},"Vendor risk ",[],{},{"nodeType":320,"data":517,"content":518},{},[519,529,539,549,559],{"nodeType":324,"data":520,"content":521},{},[522],{"nodeType":252,"data":523,"content":524},{},[525],{"nodeType":247,"value":526,"marks":527,"data":528},"Does the vendor have the resources to secure the product? ",[],{},{"nodeType":324,"data":530,"content":531},{},[532],{"nodeType":252,"data":533,"content":534},{},[535],{"nodeType":247,"value":536,"marks":537,"data":538},"Have they invested in a security team and implemented appropriate security processes?",[],{},{"nodeType":324,"data":540,"content":541},{},[542],{"nodeType":252,"data":543,"content":544},{},[545],{"nodeType":247,"value":546,"marks":547,"data":548},"Have those processes been independently audited (e.g. SOC2)? ",[],{},{"nodeType":324,"data":550,"content":551},{},[552],{"nodeType":252,"data":553,"content":554},{},[555],{"nodeType":247,"value":556,"marks":557,"data":558},"Does the vendor operate in a high risk region?",[],{},{"nodeType":324,"data":560,"content":561},{},[562],{"nodeType":252,"data":563,"content":564},{},[565],{"nodeType":247,"value":566,"marks":567,"data":568},"Does the vendor have a history of repeated security incidents?",[],{},{"nodeType":324,"data":570,"content":571},{},[572],{"nodeType":252,"data":573,"content":574},{},[575],{"nodeType":247,"value":576,"marks":577,"data":578},"Vendor sub processors - the majority of SaaS applications are build on other *-as-a-Service platforms. These vendors are also part of your supply chain. Just because you don’t directly use a tool or app doesn’t mean you’re not affected when they’re popped. Realistically, you’re probably not going to be able to go very deep here, but when you’re wondering whether you’re affected by a breach in the news, you may want to know whether your vendors are using the affected SaaS app. ",[],{},{"nodeType":252,"data":580,"content":581},{},[582],{"nodeType":247,"value":583,"marks":584,"data":585},"Ultimately, how much you care about any of the above comes down to the risk of the data in the application or the level of access you grant this application into the rest of your infrastructure (often through integrations with other SaaS apps). ",[],{},{"nodeType":252,"data":587,"content":588},{},[589],{"nodeType":247,"value":590,"marks":591,"data":592},"Therefore, a useful first step to knowing where to prioritize your time is to understand the sensitivity of the data and access granted to the app (or that will likely be granted by employees in future to make the app work as expected).",[],{},{"nodeType":252,"data":594,"content":595},{},[596],{"nodeType":247,"value":597,"marks":598,"data":599},"For self-adopted SaaS apps, aspects that are typically very important for software procurement like legal agreements (terms and conditions, master service agreements etc.), spend (through licensing cost etc.), and uptime and availability (SLAs etc.) are typically dealt with after the app has been adopted. Often, this comes up once employees need to upgrade to a paid account or higher license tier, or once it makes financial sense to commit to longer term agreements. ",[],{},{"nodeType":252,"data":601,"content":602},{},[603,607],{"nodeType":247,"value":604,"marks":605,"data":606},"For that reason, ",[],{},{"nodeType":247,"value":608,"marks":609,"data":612},"I recommend you keep the security risk assessment focused on the direct security aspects initially so you reduce the work required to ask “is there a security reason to stop our employees from using this app right now?”",[610,611],{"type":299},{"type":272},{},{"nodeType":252,"data":614,"content":615},{},[616],{"nodeType":247,"value":617,"marks":618,"data":619},"All of the above is relatively straightforward advice, but there are some very practical non-obvious lessons learned from others who've walked this path already that are worth highlighting, so let’s jump into those.",[],{},{"nodeType":621,"data":622,"content":623},"heading-2",{},[624],{"nodeType":247,"value":625,"marks":626,"data":627},"Focus on the new stuff first",[],{},{"nodeType":252,"data":629,"content":630},{},[631],{"nodeType":247,"value":632,"marks":633,"data":634},"It’s both technically, and politically, very difficult to migrate users away from apps, especially when users have invested significant time into setting up an app and love how it works. It’s hard to spend the goodwill you’ve built up on something like this unless there really is a truly unacceptable risk or compliance issue.",[],{},{"nodeType":252,"data":636,"content":637},{},[638],{"nodeType":247,"value":639,"marks":640,"data":641},"There is an exception to this - if you get in before employees have sunk too much time and effort into an app they are far more open to input and steering. This is why we recommend that you focus your risk assessment efforts on new apps and integrations, rather than spending the majority of your time working through the backlog of already-adopted work apps.",[],{},{"nodeType":379,"data":643,"content":647},{"target":644},{"sys":645},{"id":646,"type":265,"linkType":266},"49tL50Pga47pnhp1WMHfPY",[],{"nodeType":252,"data":649,"content":650},{},[651],{"nodeType":247,"value":652,"marks":653,"data":654},"If you focus on apps that are still in the testing phases, it's much easier to steer the course towards lower-risk alternatives or pump the brakes when there really is significant risk to the business.",[],{},{"nodeType":243,"data":656,"content":657},{},[658],{"nodeType":247,"value":659,"marks":660,"data":661},"Buy yourself time",[],{},{"nodeType":252,"data":663,"content":664},{},[665],{"nodeType":247,"value":666,"marks":667,"data":668},"Remember, even the newest apps will only be new for a brief time. Once employees have invested significant time into an app (learning how it works, putting data into it, etc) they will be resistant to considering alternatives and will push to accept risks rather and make exceptions to policies rather than moving to an alternative app. This is just natural, but it does mean that there is a clock running for you and your team as soon as an employee creates an account on a new SaaS app.",[],{},{"nodeType":379,"data":670,"content":674},{"target":671},{"sys":672},{"id":673,"type":265,"linkType":266},"6HzSQ8wPVn9RfDSFWGaCh8",[],{"nodeType":252,"data":676,"content":677},{},[678],{"nodeType":247,"value":679,"marks":680,"data":682},"Your goal is to give your security team as much time to assess the app before the employee decides for sure they want to use it for work. ",[681],{"type":299},{},{"nodeType":252,"data":684,"content":685},{},[686],{"nodeType":247,"value":687,"marks":688,"data":689},"It’s far less useful if you discover an app once the team is talking to finance about upgrading to a paid subscription. At that point, so much time and effort has been invested that it’s very difficult to motivate employees/teams to move to a lower-risk app. In this scenario, you’ll be stuck in a “let’s do as much as we can to secure this” mode, which isn’t ideal.",[],{},{"nodeType":252,"data":691,"content":692},{},[693],{"nodeType":247,"value":694,"marks":695,"data":696},"The way to give the security team as much time as possible is to reduce the delta between an employee signing up for an account and the IT and security teams finding out about it. You need a way to find out about new apps being adopted in real-time or within hours, rather than days or weeks. The tools to do this exist, but more on how you should choose the right tool in the “importance of choosing the right data source” section.",[],{},{"nodeType":621,"data":698,"content":699},{},[700],{"nodeType":247,"value":701,"marks":702,"data":703},"You need accurate data to take action",[],{},{"nodeType":252,"data":705,"content":706},{},[707],{"nodeType":247,"value":708,"marks":709,"data":710},"To discover SaaS apps and simply inventory which apps are being used for reporting purposes, you won’t need perfect accuracy and you’ll be able to live with some false positives.",[],{},{"nodeType":252,"data":712,"content":713},{},[714],{"nodeType":247,"value":715,"marks":716,"data":717},"Most security teams start out just by getting visibility of what SaaS is being used across their business. Then you know what you’re dealing with. The downside is that you’ll want to use this data to spin off a risk assessment process. If you are kicking off risk assessments based on false positives, that’s just pure wasted effort.",[],{},{"nodeType":252,"data":719,"content":720},{},[721],{"nodeType":247,"value":722,"marks":723,"data":724},"You will likely also want to get in touch with the employee that adopted the app, for example to understand their intended use-case and the data that might be going into the app. Employees will also notice quickly if the security team can’t tell the difference between accessing an app website or using an app and get annoyed with the interruptions from your team.",[],{},{"nodeType":379,"data":726,"content":730},{"target":727},{"sys":728},{"id":729,"type":265,"linkType":266},"5winuguRBMaNKNnkDakMWv",[],{"nodeType":252,"data":732,"content":733},{},[734],{"nodeType":247,"value":735,"marks":736,"data":737},"Many tools will use things like scanning employee email inboxes or network-level data to “discover employee SaaS use,” but this leads to a frustrating rate of false positives for your team. If the security team needs to first confirm if a data point is a false-positive through some unspecified process, then that seriously increases the work needed to take action. ",[],{},{"nodeType":252,"data":739,"content":740},{},[741],{"nodeType":247,"value":742,"marks":743,"data":744},"At the risk of sounding like a broken record, accurate data is the thing that turns this problem from something that’s impossible to something which is manageable, even at scale.",[],{},{"nodeType":243,"data":746,"content":747},{},[748],{"nodeType":247,"value":749,"marks":750,"data":751},"Customer responsibility for self-adopted SaaS",[],{},{"nodeType":252,"data":753,"content":754},{},[755],{"nodeType":247,"value":756,"marks":757,"data":758},"As a reminder, I’m referring in this section to your responsibility as a customer (highlighted in purple) in terms of NCSC’s shared-responsibility model shown below:",[],{},{"nodeType":379,"data":760,"content":764},{"target":761},{"sys":762},{"id":763,"type":265,"linkType":266},"4jeDpoYQzPmg5TFApeopSA",[],{"nodeType":252,"data":766,"content":767},{},[768],{"nodeType":247,"value":769,"marks":770,"data":771},"Let’s start with the bulk of the work, which for self-adopted SaaS is account security. This includes all the usual suspects like ensuring that, you’re:",[],{},{"nodeType":320,"data":773,"content":774},{},[775,785,795,805],{"nodeType":324,"data":776,"content":777},{},[778],{"nodeType":252,"data":779,"content":780},{},[781],{"nodeType":247,"value":782,"marks":783,"data":784},"Enabling MFA for all accounts",[],{},{"nodeType":324,"data":786,"content":787},{},[788],{"nodeType":252,"data":789,"content":790},{},[791],{"nodeType":247,"value":792,"marks":793,"data":794},"Encouraging employees to use strong passwords (ideally through a password manager)",[],{},{"nodeType":324,"data":796,"content":797},{},[798],{"nodeType":252,"data":799,"content":800},{},[801],{"nodeType":247,"value":802,"marks":803,"data":804},"Using SSO, where possible and practical",[],{},{"nodeType":324,"data":806,"content":807},{},[808],{"nodeType":252,"data":809,"content":810},{},[811],{"nodeType":247,"value":812,"marks":813,"data":814},"Reviewing access delegated to third-parties (through e.g. OAuth integrations) ",[],{},{"nodeType":379,"data":816,"content":820},{"target":817},{"sys":818},{"id":819,"type":265,"linkType":266},"2T7DtBRBBITb4Wy8unQHZV",[],{"nodeType":252,"data":822,"content":823},{},[824],{"nodeType":247,"value":825,"marks":826,"data":827},"In contrast to SaaS apps like Office 365 or Salesforce that are extraordinarily configurable and often have teams managing and securing them, there’s some mixed news when it comes to self-adopted SaaS apps. The bad news is that many of these apps provide virtually no security features or configurable settings that can be hardened. The good news is that this means there is now very little work to do here. When they exist, configuration settings are typically around:",[],{},{"nodeType":320,"data":829,"content":830},{},[831,841],{"nodeType":324,"data":832,"content":833},{},[834],{"nodeType":252,"data":835,"content":836},{},[837],{"nodeType":247,"value":838,"marks":839,"data":840},"Forcing the above controls for all users (e.g. force MFA)",[],{},{"nodeType":324,"data":842,"content":843},{},[844],{"nodeType":252,"data":845,"content":846},{},[847],{"nodeType":247,"value":848,"marks":849,"data":850},"Configuring external or public-sharing settings",[],{},{"nodeType":252,"data":852,"content":853},{},[854],{"nodeType":247,"value":855,"marks":856,"data":857},"Finally, though not mentioned explicitly in the NCSC’s version of the shared-responsibility model, it’s worth remembering that things go wrong even if all the above is in place. That’s where security monitoring comes in. In practice, though, few self-adopted SaaS apps offer audit trails or similar options that can be integrated with SIEM infrastructure. However, you can monitor things like:",[],{},{"nodeType":320,"data":859,"content":860},{},[861,871],{"nodeType":324,"data":862,"content":863},{},[864],{"nodeType":252,"data":865,"content":866},{},[867],{"nodeType":247,"value":868,"marks":869,"data":870},"Breached passwords in passwords dumps (think haveibeenpwned.com)",[],{},{"nodeType":324,"data":872,"content":873},{},[874],{"nodeType":252,"data":875,"content":876},{},[877],{"nodeType":247,"value":878,"marks":879,"data":880},"Typical post-exploitation or persistence techniques (e.g. OAuth integrations or API keys being created, forwarding rules, etc.)",[],{},{"nodeType":252,"data":882,"content":883},{},[884],{"nodeType":247,"value":885,"marks":886,"data":887},"These are the controls that fall into that “easy to understand, easy to recommend, but pretty hard to do at scale” category. Very few organizations have account security controls in place across the bulk of SaaS apps, and especially the apps that were self-adopted. The reality is that most companies still don’t even know about those self-adopted apps. So where should we start?",[],{},{"nodeType":252,"data":889,"content":890},{},[891],{"nodeType":247,"value":892,"marks":893,"data":894},"I think the most sane approach is to avoid speculation and focus on the techniques that are actually being used to attack SaaS apps today. I’ll cut to the chase - it’s credential stuffing we need to prevent. ",[],{},{"nodeType":621,"data":896,"content":897},{},[898],{"nodeType":247,"value":899,"marks":900,"data":901},"Start with preventing credential stuffing",[],{},{"nodeType":252,"data":903,"content":904},{},[905],{"nodeType":247,"value":906,"marks":907,"data":908},"The most common attack against SaaS today is credential stuffing – where attackers use tools that automate the process of taking a list of breached passwords (from public password dumps or traded on underground crime marketplaces) and retargeting those credentials against different apps. ",[],{},{"nodeType":252,"data":910,"content":911},{},[912],{"nodeType":247,"value":913,"marks":914,"data":915},"Slightly more sophisticated attackers might even try expanding their targets by using marketing and advertising services to match private accounts to work accounts in case employees re-used similar passwords. In the example for acme.com in the graphic below, we see how this plays out to get access to a company’s MailChimp. At this point, attackers are able to start sending scam emails to your customers from your domain in emails that look completely legit. This type of attack where compromised SaaS apps are used to send customers malicious emails are something we’ve seen play out a few times recently:",[],{},{"nodeType":320,"data":917,"content":918},{},[919,943,964,986,1007],{"nodeType":324,"data":920,"content":921},{},[922],{"nodeType":252,"data":923,"content":924},{},[925,929,940],{"nodeType":247,"value":926,"marks":927,"data":928},"In this ",[],{},{"nodeType":930,"data":931,"content":933},"hyperlink",{"uri":932},"https://www.bleepingcomputer.com/news/security/chipotle-s-marketing-account-hacked-to-send-phishing-emails/",[934],{"nodeType":247,"value":935,"marks":936,"data":939},"Chipotle attack",[937],{"type":938},"underline",{},{"nodeType":247,"value":29,"marks":941,"data":942},[],{},{"nodeType":324,"data":944,"content":945},{},[946],{"nodeType":252,"data":947,"content":948},{},[949,952,961],{"nodeType":247,"value":926,"marks":950,"data":951},[],{},{"nodeType":930,"data":953,"content":955},{"uri":954},"https://www.bleepingcomputer.com/news/security/doordash-discloses-new-data-breach-tied-to-twilio-hackers/",[956],{"nodeType":247,"value":957,"marks":958,"data":960},"DoorDash attack",[959],{"type":938},{},{"nodeType":247,"value":29,"marks":962,"data":963},[],{},{"nodeType":324,"data":965,"content":966},{},[967],{"nodeType":252,"data":968,"content":969},{},[970,974,983],{"nodeType":247,"value":971,"marks":972,"data":973},"In this",[],{},{"nodeType":930,"data":975,"content":977},{"uri":976},"https://www.bleepingcomputer.com/news/security/namecheaps-email-hacked-to-send-metamask-dhl-phishing-emails/",[978],{"nodeType":247,"value":979,"marks":980,"data":982}," attack against domain registrar NameCheap",[981],{"type":938},{},{"nodeType":247,"value":29,"marks":984,"data":985},[],{},{"nodeType":324,"data":987,"content":988},{},[989],{"nodeType":252,"data":990,"content":991},{},[992,995,1004],{"nodeType":247,"value":926,"marks":993,"data":994},[],{},{"nodeType":930,"data":996,"content":998},{"uri":997},"https://www.bleepingcomputer.com/news/security/hacked-sendgrid-accounts-used-in-phishing-attacks-to-steal-logins/",[999],{"nodeType":247,"value":1000,"marks":1001,"data":1003},"SendGrid attack",[1002],{"type":938},{},{"nodeType":247,"value":29,"marks":1005,"data":1006},[],{},{"nodeType":324,"data":1008,"content":1009},{},[1010],{"nodeType":252,"data":1011,"content":1012},{},[1013,1016,1025],{"nodeType":247,"value":926,"marks":1014,"data":1015},[],{},{"nodeType":930,"data":1017,"content":1019},{"uri":1018},"https://www.bleepingcomputer.com/news/security/mailchimp-discloses-new-breach-after-employees-got-hacked/",[1020],{"nodeType":247,"value":1021,"marks":1022,"data":1024},"MailChimp attack",[1023],{"type":938},{},{"nodeType":247,"value":29,"marks":1026,"data":1027},[],{},{"nodeType":379,"data":1029,"content":1033},{"target":1030},{"sys":1031},{"id":1032,"type":265,"linkType":266},"o6eDG116P2tdWdq4oNllR",[],{"nodeType":252,"data":1035,"content":1036},{},[1037],{"nodeType":247,"value":1038,"marks":1039,"data":1040},"PLG and the increase in employee-adopted apps has led to employees creating more accounts, on more apps and without the guiding hand of security to make sure strong identity and access controls are in place. ",[],{},{"nodeType":252,"data":1042,"content":1043},{},[1044],{"nodeType":247,"value":1045,"marks":1046,"data":1049},"Opportunistic attackers now have a huge, unmonitored attack surface to target using low effort/cost techniques that generate reliable results for them. ",[1047,1048],{"type":299},{"type":272},{},{"nodeType":621,"data":1051,"content":1052},{},[1053],{"nodeType":247,"value":1054,"marks":1055,"data":1056},"Why SSO is not the answer to our SaaS account security prayers",[],{},{"nodeType":252,"data":1058,"content":1059},{},[1060],{"nodeType":247,"value":1061,"marks":1062,"data":1063},"Many security teams are leaning on SSO to address this issue. They’ll require that apps used in their company use SSO, specifically SAML (Security Assertion Markup Language) before they can be approved or used. This works really, really well for the apps that provide this functionality. It’s the gold standard for authentication. ",[],{},{"nodeType":252,"data":1065,"content":1066},{},[1067],{"nodeType":247,"value":1068,"marks":1069,"data":1070},"With SAML SSO, there’s just one account, just one password, and you can centrally deprovision accounts when employees leave the organization. In fact, you’re probably already paying for a SAML IdP (Identity Provider) like Google Directory or Azure AD. Many others are using tools like Okta.   ",[],{},{"nodeType":252,"data":1072,"content":1073},{},[1074],{"nodeType":247,"value":1075,"marks":1076,"data":1077},"There’s one obvious point we need to make here: SSO isn’t going to help you discover which apps employees are using. But, once you discover them and determine they support SAML, you can integrate them with your solution.",[],{},{"nodeType":252,"data":1079,"content":1080},{},[1081],{"nodeType":247,"value":1082,"marks":1083,"data":1084},"But here lies the problem…when we reviewed 500 of the most popular apps that Push supports, we found that: ",[],{},{"nodeType":621,"data":1086,"content":1087},{},[1088],{"nodeType":247,"value":1089,"marks":1090,"data":1091},"Only around 30% of apps offer SSO and, of those, very few make it available on their lower-priced tiers.",[],{},{"nodeType":379,"data":1093,"content":1097},{"target":1094},{"sys":1095},{"id":1096,"type":265,"linkType":266},"56nd8Na4I0efwOf9pfmB8s",[],{"nodeType":252,"data":1099,"content":1100},{},[1101],{"nodeType":247,"value":1102,"marks":1103,"data":1104},"We also noticed that the more modern, newer apps were less likely to offer SAML support than the larger, more established business apps. So if your strategy is to block access to any app that doesn’t offer SSO integrations, you’re going to have to block the majority of self-adopted apps your employees are using. ",[],{},{"nodeType":252,"data":1106,"content":1107},{},[1108],{"nodeType":247,"value":1109,"marks":1110,"data":1111},"There are some other complications and nuances around SAML. Sometimes the SAML integration will only cover one tenant or instance and not the entire app. In this case, every time you find a new workspace or instance, you need to integrate it again. Worse, you can often only integrate one workspace or instance with your SAML IdP. ",[],{},{"nodeType":252,"data":1113,"content":1114},{},[1115,1119,1128],{"nodeType":247,"value":1116,"marks":1117,"data":1118},"Then there’s the ethically dubious issue of “",[],{},{"nodeType":930,"data":1120,"content":1122},{"uri":1121},"https://sso.tax/",[1123],{"nodeType":247,"value":1124,"marks":1125,"data":1127},"SSO tax",[1126],{"type":938},{},{"nodeType":247,"value":1129,"marks":1130,"data":1131},"” where vendors that do offer SSO reserve it only for their enterprise tiers designed for organizations buying huge volumes of licenses, which makes this impractical for many if not most of us.",[],{},{"nodeType":621,"data":1133,"content":1134},{},[1135],{"nodeType":247,"value":1136,"marks":1137,"data":1138},"A game plan for preventing credential stuffing",[],{},{"nodeType":252,"data":1140,"content":1141},{},[1142],{"nodeType":247,"value":1143,"marks":1144,"data":1145},"I like the idea of going passwordless as much as the next security person, but that’s not practical for many apps right now. So we’re going to rely on passwords as well, at least for the foreseeable future. Strong, unique passwords, coupled with MFA, are very effective identity and access controls, so it’s not the end of the world.",[],{},{"nodeType":252,"data":1147,"content":1148},{},[1149],{"nodeType":247,"value":1150,"marks":1151,"data":1152},"To prevent credential stuffing attacks (and a whole host of other attacks to boot) you will need to implement the following controls:",[],{},{"nodeType":379,"data":1154,"content":1158},{"target":1155},{"sys":1156},{"id":1157,"type":265,"linkType":266},"JU64Zj7eiqS1s5OfWmZyo",[],{"nodeType":252,"data":1160,"content":1161},{},[1162],{"nodeType":247,"value":1163,"marks":1164,"data":1165},"It’s useful to note from the requirements that you must be in a position to discover SaaS apps being onboarded, but also discover how these apps are accessed.",[],{},{"nodeType":252,"data":1167,"content":1168},{},[1169],{"nodeType":247,"value":1170,"marks":1171,"data":1172},"There’s only one place where we can get data about who is using which SaaS apps, as well as the ability to inspect passwords and check MFA status for each user. And that’s in the employee’s browsers.",[],{},{"nodeType":252,"data":1174,"content":1175},{},[1176],{"nodeType":247,"value":1177,"marks":1178,"data":1179},"This is the reason we have chosen to build our solution using a browser extension. It allows us to:",[],{},{"nodeType":320,"data":1181,"content":1182},{},[1183,1193,1203],{"nodeType":324,"data":1184,"content":1185},{},[1186],{"nodeType":252,"data":1187,"content":1188},{},[1189],{"nodeType":247,"value":1190,"marks":1191,"data":1192},"Observe username and password logins, ",[],{},{"nodeType":324,"data":1194,"content":1195},{},[1196],{"nodeType":252,"data":1197,"content":1198},{},[1199],{"nodeType":247,"value":1200,"marks":1201,"data":1202},"Assess their strength and whether they are being shared or reused, and ",[],{},{"nodeType":324,"data":1204,"content":1205},{},[1206],{"nodeType":252,"data":1207,"content":1208},{},[1209],{"nodeType":247,"value":1210,"marks":1211,"data":1212},"Allow security teams to fix any accounts that don’t meet their policies or expectations.",[],{},{"nodeType":252,"data":1214,"content":1215},{},[1216],{"nodeType":247,"value":1217,"marks":1218,"data":1219},"More on that in a moment, but first, the last piece of advice:",[],{},{"nodeType":243,"data":1221,"content":1222},{},[1223],{"nodeType":247,"value":1224,"marks":1225,"data":1226},"Tackle risk assessment and account security in parallel",[],{},{"nodeType":252,"data":1228,"content":1229},{},[1230],{"nodeType":247,"value":1231,"marks":1232,"data":1233},"Quite often when I talk to security leaders, they’re fixated on supply chain risk and the risk of account compromise is an afterthought. This is understandable - these are the attacks that are widely reported, and require high-level decision making, so this feels like the natural first step. They’re aware that employees are using unvetted apps, but they don’t feel like they’re in a position to secure the employee account until they have identified and vetted all the apps in use. ",[],{},{"nodeType":252,"data":1235,"content":1236},{},[1237],{"nodeType":247,"value":1238,"marks":1239,"data":1240},"It seems logical to want to approve apps first and then secure the accounts. It might make sense if you are starting from zero, however, when organizations get visibility of SaaS apps in use, they usually see hundreds on the list that employees are already using. In this case, waiting to get through the entire backlog of app risk assessment first is counter productive. Regardless of whether an app is approved yet, if it’s in use there is the risk of an attacker compromising a weak employee account with a credential stuffing attack, which is arguably a greater risk than a SaaS vendor being compromised in a supply chain attack. That’s because attacks against employee SaaS accounts are more common, just reported less often than supply chain attacks.",[],{},{"nodeType":252,"data":1242,"content":1243},{},[1244],{"nodeType":247,"value":1245,"marks":1246,"data":1247},"The best way to bring down as much SaaS risk as quickly as possible is to tackle both streams independently and in parallel. But to do this, you need the right tools.  ",[],{},{"nodeType":252,"data":1249,"content":1250},{},[1251],{"nodeType":247,"value":1252,"marks":1253,"data":1254},"Push collects usage data from the same place we collect account security data so we can also identify password and MFA data about the employee’s SaaS account. We don’t require you to integrate Push with each app you discover. Instead, usage and security data are collected at the same time we’re discovering the app because we’re using a browser extension. The extension gives us relevant security context so you can address both risks together. On that note, let’s dig into the data that SaaS security tools use.",[],{},{"nodeType":243,"data":1256,"content":1257},{},[1258],{"nodeType":247,"value":1259,"marks":1260,"data":1261},"Choose the right data source",[],{},{"nodeType":252,"data":1263,"content":1264},{},[1265],{"nodeType":247,"value":1266,"marks":1267,"data":1268},"Since we’ve moved from a world in which we as security teams got visibility through process (IT or procurement) to a world where we rely on technology to give us that visibility (for e.g. self-adopted apps) - we’re going to need tooling, and that’s where things get complicated.",[],{},{"nodeType":252,"data":1270,"content":1271},{},[1272],{"nodeType":247,"value":1273,"marks":1274,"data":1275},"The list of SaaS security product categories and tools is growing almost weekly, from Cloud Access Security Broker (CASBs), Security Service Edge (SSEs), SaaS Security Posture Management (SSPMs) and any number of other new buzzwords. The only thing growing faster is the promises they make, so it’s no surprise that it’s very difficult to identify solutions that can actually deliver what’s required.",[],{},{"nodeType":252,"data":1277,"content":1278},{},[1279],{"nodeType":247,"value":1280,"marks":1281,"data":1282},"One critical factor to consider when choosing tooling is the data that these tools build on. The requirements we’ve identified for doing SaaS security in the previous section are that we need to be able to:",[],{},{"nodeType":320,"data":1284,"content":1285},{},[1286,1296,1306,1316],{"nodeType":324,"data":1287,"content":1288},{},[1289],{"nodeType":252,"data":1290,"content":1291},{},[1292],{"nodeType":247,"value":1293,"marks":1294,"data":1295},"Discover new SaaS apps being adopted (and self-adopted).",[],{},{"nodeType":324,"data":1297,"content":1298},{},[1299],{"nodeType":252,"data":1300,"content":1301},{},[1302],{"nodeType":247,"value":1303,"marks":1304,"data":1305},"Keep a low rate of false positives, in other words we need to be able to tell the difference between, for example, accessing a SaaS app website or actually login into the app.",[],{},{"nodeType":324,"data":1307,"content":1308},{},[1309],{"nodeType":252,"data":1310,"content":1311},{},[1312],{"nodeType":247,"value":1313,"marks":1314,"data":1315},"Get insight into the identities or accounts used to access these apps - we need to know which users are authenticating to these apps and how (SSO, Social Logins, Local passwords)",[],{},{"nodeType":324,"data":1317,"content":1318},{},[1319],{"nodeType":252,"data":1320,"content":1321},{},[1322],{"nodeType":247,"value":1323,"marks":1324,"data":1325},"Identify account security issues such as disabled MFA, weak, reused and breached passwords.",[],{},{"nodeType":252,"data":1327,"content":1328},{},[1329],{"nodeType":247,"value":1330,"marks":1331,"data":1332},"The following is a summary of the most common data sources SaaS security tools are built on, and how they stack up in terms of the requirements above:",[],{},{"nodeType":379,"data":1334,"content":1338},{"target":1335},{"sys":1336},{"id":1337,"type":265,"linkType":266},"E8ThSCqbNNa9nggaKE3p1",[],{"nodeType":252,"data":1340,"content":1341},{},[1342,1346,1357],{"nodeType":247,"value":1343,"marks":1344,"data":1345},"Each data source has pros and cons, but let’s take a look at the most common sources to see what the high-level trade-offs are. We’ve got a short ",[],{},{"nodeType":260,"data":1347,"content":1351},{"target":1348},{"sys":1349},{"id":1350,"type":265,"linkType":266},"45iZ69EdPF4629gZ6yf7p5",[1352],{"nodeType":247,"value":1353,"marks":1354,"data":1356},"blog post ",[1355],{"type":938},{},{"nodeType":247,"value":1358,"marks":1359,"data":1360},"on this topic if you want to share with your teammates and peers.",[],{},{"nodeType":621,"data":1362,"content":1363},{},[1364],{"nodeType":247,"value":1365,"marks":1366,"data":1367},"Financial records",[],{},{"nodeType":252,"data":1369,"content":1370},{},[1371],{"nodeType":247,"value":1372,"marks":1373,"data":1374},"Looking through invoices can provide some visibility into paid SaaS apps, which is why it has a very low false positive rate. However, there are blind spots - you won’t see any free tier or trial accounts, nor will you get any useful business context about who’s using it, how they’re using it, if logins are secure, and what data it has access to. That said, it’s a quick and dirty way to get a partial view of SaaS usage and might be the best place to start. ",[],{},{"nodeType":252,"data":1376,"content":1377},{},[1378],{"nodeType":247,"value":1379,"marks":1380,"data":1381},"The main downside of using finance as a data source is that it will discover apps very slowly, most apps will only move to a paid tier once employees have already been using the app for a while on free-tier and have become reliant enough on it that they need additional features or users. This is often too late to steer these users to a different app if there are critical risks identified with the app or vendor.",[],{},{"nodeType":621,"data":1383,"content":1384},{},[1385],{"nodeType":247,"value":1386,"marks":1387,"data":1388},"Email analytics",[],{},{"nodeType":252,"data":1390,"content":1391},{},[1392],{"nodeType":247,"value":1393,"marks":1394,"data":1395},"You can look at all the emails every employee receives and match these emails to different SaaS apps and vendors and based on that information make some statistical guesses about which employees are using which apps. This improves on finance records in a significant metric - speed of detection, but the trade-off is a high rate of false positives. One aspect that email detection is great for that isn’t included in the table is the ability to detect historic SaaS apps.",[],{},{"nodeType":252,"data":1397,"content":1398},{},[1399],{"nodeType":247,"value":1400,"marks":1401,"data":1402},"Unfortunately, except for some very limited edge cases it’s not possible to broadly detect account security issues using email, so at best this is a first-step data source.",[],{},{"nodeType":621,"data":1404,"content":1405},{},[1406],{"nodeType":247,"value":1407,"marks":1408,"data":1409},"Network data",[],{},{"nodeType":252,"data":1411,"content":1412},{},[1413],{"nodeType":247,"value":1414,"marks":1415,"data":1416},"This is the old-school approach that tools like CASBs use to do SaaS discovery, taking data from edge devices like firewalls, proxies, or DNS relays. This makes it very difficult to implement for companies that are distributed and cloud-native. There are now solutions that are more appropriate for distributed teams that work either by collecting network data from the endpoint with an agent, or perhaps your organization is very office-based and has excellent network telemetry - in which case these solutions might be easier to deploy.",[],{},{"nodeType":252,"data":1418,"content":1419},{},[1420],{"nodeType":247,"value":1421,"marks":1422,"data":1423},"While network data is relatively well understood, it’s not a great source for discovering SaaS use (as opposed to detecting when an employee simply accesses SaaS app websites - false positives galore) or for finding account security issues. It’s useful to get an idea of which apps might be used and indications on who might be using the app. But network data doesn’t provide the level of detail needed to discover account security issues. This is why CASB solutions have almost all started including API integrations to augment this data and make it useful - though this has its own problems.",[],{},{"nodeType":252,"data":1425,"content":1426},{},[1427],{"nodeType":247,"value":1428,"marks":1429,"data":1430},"If you’re looking to get a quick outline of which SaaS may be in use, a finance or email-based solution would likely be much easier to deploy and more cost effective. If you want to discover and remediate problems and actually reduce SaaS risk, you need to look elsewhere.",[],{},{"nodeType":621,"data":1432,"content":1433},{},[1434],{"nodeType":247,"value":1435,"marks":1436,"data":1437},"Application API data",[],{},{"nodeType":252,"data":1439,"content":1440},{},[1441],{"nodeType":247,"value":1442,"marks":1443,"data":1444},"Many of the more established SaaS apps (especially those that are almost Platform-as-a-Service or PaaS) like 365, Salesforce, Slack, Github etc. offer APIs that expose security-relevant data. However, for apps that do support these APIs, this is an amazing data source that typically provides the ability to extract user-lists or check account security controls like MFA are enabled for all users, or list third-party integrations. Audit log feeds also provide a useful data source for ingestion into SIEM systems. ",[],{},{"nodeType":252,"data":1446,"content":1447},{},[1448],{"nodeType":247,"value":1449,"marks":1450,"data":1451},"However, APIs as a data source for doing SaaS security has 2 major limitations:",[],{},{"nodeType":1453,"data":1454,"content":1455},"ordered-list",{},[1456,1475],{"nodeType":324,"data":1457,"content":1458},{},[1459],{"nodeType":252,"data":1460,"content":1461},{},[1462,1466,1471],{"nodeType":247,"value":1463,"marks":1464,"data":1465},"No discovery features. ",[],{},{"nodeType":247,"value":1467,"marks":1468,"data":1470},"You must already know that an app is in use",[1469],{"type":299},{},{"nodeType":247,"value":1472,"marks":1473,"data":1474}," (or more specifically know about every app tenant in use) before you can integrate it with your SaaS security solutions (typically SSPM tools). This means you need some other data source to discover SaaS apps and tenants.",[],{},{"nodeType":324,"data":1476,"content":1477},{},[1478],{"nodeType":252,"data":1479,"content":1480},{},[1481,1485,1490],{"nodeType":247,"value":1482,"marks":1483,"data":1484},"Lack of support. These APIs are typically available ",[],{},{"nodeType":247,"value":1486,"marks":1487,"data":1489},"only for “core” SaaS platforms",[1488],{"type":299},{},{"nodeType":247,"value":1491,"marks":1492,"data":1493},", and a very small minority of the types of SaaS apps employees might self-adopt will other these security monitoring integrations.",[],{},{"nodeType":621,"data":1495,"content":1496},{},[1497],{"nodeType":247,"value":1498,"marks":1499,"data":1500},"Browser extensions",[],{},{"nodeType":252,"data":1502,"content":1503},{},[1504],{"nodeType":247,"value":1505,"marks":1506,"data":1507},"The idea behind using browser extensions for SaaS security is simple: if all the data you care about monitoring exists in your employees’ browsers, let’s analyze the data in the browser. Browser extensions allow you to deeply inspect users' interactions with SaaS apps. This means you can get close to perfect accuracy in terms of discovering which apps are in-use (vs browser the website) because you can actually observe the login process directly. ",[],{},{"nodeType":252,"data":1509,"content":1510},{},[1511,1515,1520],{"nodeType":247,"value":1512,"marks":1513,"data":1514},"Since you observe the login process with the extension, it’s easy to discover account security issues like weak passwords or missing MFA. You can also tell when employees are logging into apps without using SSO. Best of all you don’t need to create a dragnet and collect all this data centrally creating a privacy nightmare, instead ",[],{},{"nodeType":247,"value":1516,"marks":1517,"data":1519},"you can analyze this data where it already exists, inside the safe confines of the browser sandbox",[1518],{"type":299},{},{"nodeType":247,"value":1521,"marks":1522,"data":1523},". The only data you report out is a flag when you find an issue.",[],{},{"nodeType":252,"data":1525,"content":1526},{},[1527,1531,1536],{"nodeType":247,"value":1528,"marks":1529,"data":1530},"Another benefit of browser extensions is that they are not passive. ",[],{},{"nodeType":247,"value":1532,"marks":1533,"data":1535},"You can easily add active features to extensions that do things like warn users before they even set bad passwords",[1534],{"type":299},{},{"nodeType":247,"value":1537,"marks":1538,"data":1539}," - preventing these issues from occurring in the first place.",[],{},{"nodeType":252,"data":1541,"content":1542},{},[1543],{"nodeType":247,"value":1544,"marks":1545,"data":1546},"The downside is that you need to deploy these browser extensions to employees. This used to be a much bigger issue in the past, but these days it’s easy to deploy extensions to your whole fleet of Chrome, Edge, Firefox, Safari, Brave and Opera browsers using an MDM or GPO policy. Another nice thing about extensions, is that unlike endpoint agents, extensions are cross platform (they don’t care if you are on Windows, Mac or Linux), are isolated to the browser and automatically update through the browser extension store.",[],{},{"nodeType":252,"data":1548,"content":1549},{},[1550],{"nodeType":247,"value":1551,"marks":1552,"data":1553},"I’m sure I’m not doing a great job of hiding my enthusiasm for browser extensions as a platform to build SaaS security tools on, but they truly do provide the kind of fast, accurate and detailed data we need to solve both the supply-chain and customer responsibility sides of SaaS security.",[],{},{"nodeType":621,"data":1555,"content":1556},{},[1557],{"nodeType":247,"value":1558,"marks":1559,"data":1560},"Push uses a browser extension and APIs ",[],{},{"nodeType":252,"data":1562,"content":1563},{},[1564],{"nodeType":247,"value":1565,"marks":1566,"data":1567},"That’s why we decided to build Push on a browser extension. To discover and provide security-relevant data about the integrations to your core cloud platforms, we also use APIs. Together, these two data sources provided a full view of the SaaS apps employees are using.",[],{},{"nodeType":243,"data":1569,"content":1570},{},[1571],{"nodeType":247,"value":1572,"marks":1573,"data":1574},"How can Push help?",[],{},{"nodeType":252,"data":1576,"content":1577},{},[1578],{"nodeType":247,"value":1579,"marks":1580,"data":1581},"It probably won’t come as a surprise to find out that we’ve designed Push so security teams can get a handle on employee-adopted SaaS apps without needing to block them.",[],{},{"nodeType":252,"data":1583,"content":1584},{},[1585],{"nodeType":247,"value":1586,"marks":1587,"data":1588},"Here’s a quick rundown of how Push can help you:",[],{},{"nodeType":621,"data":1590,"content":1591},{},[1592],{"nodeType":247,"value":1593,"marks":1594,"data":1595},"Get visibility of shadow SaaS apps and unmanaged cloud accounts",[],{},{"nodeType":252,"data":1597,"content":1598},{},[1599],{"nodeType":247,"value":1600,"marks":1601,"data":1602},"If you’re going to get a handle on employee-adopted SaaS apps, you need to get visibility of them first. Push uses data from our browser extension to find SaaS apps that are logged into with usernames and passwords and SSO (OIDC). This gives you complete visibility of your SaaS environment, including shadow SaaS apps and cloud accounts that are not managed by IT. ",[],{},{"nodeType":379,"data":1604,"content":1608},{"target":1605},{"sys":1606},{"id":1607,"type":265,"linkType":266},"2PW9tNBBo0ohoqXYZ04kxA",[],{"nodeType":621,"data":1610,"content":1611},{},[1612],{"nodeType":247,"value":1613,"marks":1614,"data":1615},"Detect the new apps and integrations employees are adopting in real time",[],{},{"nodeType":252,"data":1617,"content":1618},{},[1619],{"nodeType":247,"value":1620,"marks":1621,"data":1622},"Push detects employees signing up to new apps, or integrating third-party apps to your core work platforms in real-time. That allows you to step in at the earliest opportunity to vet the app for critical issues and guide the employee through the appropriate app onboarding steps. This allows you to focus on the new stuff and buy yourself time as I recommended earlier. ",[],{},{"nodeType":379,"data":1624,"content":1628},{"target":1625},{"sys":1626},{"id":1627,"type":265,"linkType":266},"1hqMZl60NhvhHIfnO7FttV",[],{"nodeType":621,"data":1630,"content":1631},{},[1632],{"nodeType":247,"value":1633,"marks":1634,"data":1635},"Avoid wasting time on false-positives",[],{},{"nodeType":252,"data":1637,"content":1638},{},[1639],{"nodeType":247,"value":1640,"marks":1641,"data":1642},"You need to trust your data if you want to take action based on the visibility you have of what apps employees are using and how they’re using them. Doing risk assessments or chasing employees about apps they’re not using wastes time and burns goodwill. ",[],{},{"nodeType":252,"data":1644,"content":1645},{},[1646],{"nodeType":247,"value":1647,"marks":1648,"data":1649},"Throughout this piece I’ve banged on about how critical it is to have the right data. Good data allows you to quickly and accurately identify new SaaS apps and integrations as employees adopt them. Good data is also required to identify the security issues that attackers can exploit to compromise your data through common attacks like Credential Stuffing. The best foundational data to lean on for SaaS visibility and risk is browser extension data.",[],{},{"nodeType":252,"data":1651,"content":1652},{},[1653],{"nodeType":247,"value":1654,"marks":1655,"data":1656},"Push collects data directly from the app using a browser extension, rather than guessing possible use from other sources like network traffic or email. ",[],{},{"nodeType":252,"data":1658,"content":1659},{},[1660],{"nodeType":247,"value":1661,"marks":1662,"data":1665},"That makes Push the only SaaS security solution that can directly observe all SaaS use and the only solution that can identify account security issues across hundreds of apps - completely automatically. No need for API support, no need for an admin account. It just works.",[1663,1664],{"type":299},{"type":272},{},{"nodeType":621,"data":1667,"content":1668},{},[1669],{"nodeType":247,"value":1670,"marks":1671,"data":1672},"Identify account security risks and discover shadow SaaS at the same time",[],{},{"nodeType":252,"data":1674,"content":1675},{},[1676],{"nodeType":247,"value":1677,"marks":1678,"data":1679},"Supply chain risk is important, but I’d argue account compromise risks are greater for most organizations. Push can identify account security issues that make it possible for attackers to compromise your employees accounts using credential stuffing, brute forcing and phishing attacks. These include:",[],{},{"nodeType":320,"data":1681,"content":1682},{},[1683,1693,1703,1713,1723,1733],{"nodeType":324,"data":1684,"content":1685},{},[1686],{"nodeType":252,"data":1687,"content":1688},{},[1689],{"nodeType":247,"value":1690,"marks":1691,"data":1692},"Compromised passwords",[],{},{"nodeType":324,"data":1694,"content":1695},{},[1696],{"nodeType":252,"data":1697,"content":1698},{},[1699],{"nodeType":247,"value":1700,"marks":1701,"data":1702},"Guessable passwords",[],{},{"nodeType":324,"data":1704,"content":1705},{},[1706],{"nodeType":252,"data":1707,"content":1708},{},[1709],{"nodeType":247,"value":1710,"marks":1711,"data":1712},"Account-sharing between multiple employees",[],{},{"nodeType":324,"data":1714,"content":1715},{},[1716],{"nodeType":252,"data":1717,"content":1718},{},[1719],{"nodeType":247,"value":1720,"marks":1721,"data":1722},"Sharing passwords across multiple accounts",[],{},{"nodeType":324,"data":1724,"content":1725},{},[1726],{"nodeType":252,"data":1727,"content":1728},{},[1729],{"nodeType":247,"value":1730,"marks":1731,"data":1732},"Missing MFA",[],{},{"nodeType":324,"data":1734,"content":1735},{},[1736],{"nodeType":252,"data":1737,"content":1738},{},[1739],{"nodeType":247,"value":1740,"marks":1741,"data":1742},"Password manager use",[],{},{"nodeType":379,"data":1744,"content":1748},{"target":1745},{"sys":1746},{"id":1747,"type":265,"linkType":266},"3hR2N6WoP5WDyD6O6zdJP1",[],{"nodeType":252,"data":1750,"content":1751},{},[1752],{"nodeType":247,"value":1753,"marks":1754,"data":1755},"We identify these issues at the same time we discover shadow SaaS apps, so you can tackle account compromise at the same time as supply chain risk to reduce your SaaS security risk exposure faster.",[],{},{"nodeType":252,"data":1757,"content":1758},{},[1759],{"nodeType":247,"value":1760,"marks":1761,"data":1762},"How do we actually reduce the risks? We engage employees directly via Slack or MS Teams, explain the account security issue we’ve identified in a way they’ll understand, and help them understand how it’s putting them and the business at risk. Then we guide them on how to fix it...",[],{},{"nodeType":379,"data":1764,"content":1768},{"target":1765},{"sys":1766},{"id":1767,"type":265,"linkType":266},"7Hgf81IlfZKoUMOp26ZXmq",[],{"nodeType":621,"data":1770,"content":1771},{},[1772],{"nodeType":247,"value":1773,"marks":1774,"data":1775},"Use Push to secure accounts that aren’t under SSO",[],{},{"nodeType":252,"data":1777,"content":1778},{},[1779],{"nodeType":247,"value":1780,"marks":1781,"data":1782},"In an ideal world, you could stick all your SaaS under your SSO solution, but we’ve already explained why that’s not practical for all apps. For apps and accounts that can’t use SSO, Push makes sure employees are using strong, unique passwords that aren’t published on a password breach list. We’ll also guide employees to use MFA when possible. ",[],{},{"nodeType":252,"data":1784,"content":1785},{},[1786],{"nodeType":247,"value":1787,"marks":1788,"data":1789},"In some instances, we can prevent account security issues from occurring in the first place. When Push detects an employee creating a new account in their browser, we’ll guide them to set up strong identity and access controls on their account, at the first signup...",[],{},{"nodeType":379,"data":1791,"content":1795},{"target":1792},{"sys":1793},{"id":1794,"type":265,"linkType":266},"44U1ByoQns6vTqCSS3XrJf",[],{"nodeType":621,"data":1797,"content":1798},{},[1799,1803],{"nodeType":247,"value":1800,"marks":1801,"data":1802},"Get a handle on employee-adopted apps ",[],{},{"nodeType":247,"value":1804,"marks":1805,"data":1807},"without being a blocker",[1806],{"type":272},{},{"nodeType":252,"data":1809,"content":1810},{},[1811],{"nodeType":247,"value":1812,"marks":1813,"data":1814},"By using Push, you can have complete visibility of all SaaS apps in your environment, including those adopted by employees without the oversight of IT and Security. We’ll automatically find the security issues that put your data at risk and enlist the support of employees to fix them. This allows you to embrace app self-adoption and adopt a default allow approach that enables your business while scaling security so you don’t lose control of SaaS security risks.  ",[],{},{"entries":1816},{"inline":1817,"hyperlink":1818,"block":1827},[],[1819,1823],{"sys":1820,"__typename":1821,"title":269,"slug":1822},{"id":264},"BlogPosts","saas-has-changed-how-we-adopt-software-how-should-security-adapt",{"sys":1824,"__typename":1821,"title":1825,"slug":1826},{"id":1350},"How to roll-your-own SaaS discovery","rolling-your-own-saas-discovery",[1828,1838,1845,1853,1861,1869,1876,1884,1891,1899,1906,1914,1920,1926,1934,1940],{"sys":1829,"__typename":1830,"title":1831,"caption":1832,"layoutMode":1833,"file":1834},{"id":383},"Image","Shared responsibility model NCSC","Source: https://www.ncsc.gov.uk/collection/cloud/understanding-cloud-services/cloud-security-shared-responsibility-model","Centre aligned",{"url":1835,"width":1836,"height":1837},"https://images.ctfassets.net/y1cdw1ablpvd/2QR4exoDHiiI32zLx7MBOL/d169ba9438f1782aba60c5c35413706d/image7.png",1662,992,{"sys":1839,"__typename":1830,"title":1840,"caption":1840,"layoutMode":1833,"file":1841},{"id":410},"Two parts of SaaS security",{"url":1842,"width":1843,"height":1844},"https://images.ctfassets.net/y1cdw1ablpvd/2dRhaTc75s2mHGYmreOZDS/8d0c2dddbabfeaddd99f3f9aa781e718/image3.png",1999,806,{"sys":1846,"__typename":1830,"title":1847,"caption":1848,"layoutMode":1833,"file":1849},{"id":646},"Focus on the new stuff PLG","By focusing on newly-tested/adopted apps, you have more sway with employees on their app choices.",{"url":1850,"width":1851,"height":1852},"https://images.ctfassets.net/y1cdw1ablpvd/3qFd7mDWRzdyySkgAOmr14/5d4fd61bb45b4ff8a8780a6ec543d493/image1.png",1976,1100,{"sys":1854,"__typename":1830,"title":1855,"caption":1856,"layoutMode":1833,"file":1857},{"id":673},"Risk assessment timeline PLG","When security can make the most impact on assessing employee-adopted SaaS apps",{"url":1858,"width":1859,"height":1860},"https://images.ctfassets.net/y1cdw1ablpvd/5Vxv5h3OpO3DXpsil5GBUa/d1ca5df575cb5e9cfc612b8b757411ff/image15.png",2000,1118,{"sys":1862,"__typename":1830,"title":1863,"caption":1864,"layoutMode":1833,"file":1865},{"id":729},"False positives employee interaction","Interacting with employees about apps they're not even using burns goodwill and wastes everyones' time",{"url":1866,"width":1867,"height":1868},"https://images.ctfassets.net/y1cdw1ablpvd/5LRJyodNqCidY9UlUIY5Jw/ad795b2e44bff77f9d746e2ccb910f18/image2.png",1192,884,{"sys":1870,"__typename":1830,"title":1871,"caption":62,"layoutMode":1833,"file":1872},{"id":763},"Customer responsibility for SaaS apps PLG",{"url":1873,"width":1874,"height":1875},"https://images.ctfassets.net/y1cdw1ablpvd/6jaP9nk2U89Y1TidafgXLB/9c3af2cd634ea0621b3e2ac05739582d/image7.png",1980,1214,{"sys":1877,"__typename":1830,"title":1878,"caption":1879,"layoutMode":1833,"file":1880},{"id":819},"Shared responsibility model - customer responsibilities - PLG","The security controls customers are responsible for",{"url":1881,"width":1882,"height":1883},"https://images.ctfassets.net/y1cdw1ablpvd/5NHny8Lh0CQjkK3N6WEbAM/ae9ee10605795c547d25177061b42391/image6.png",1966,1096,{"sys":1885,"__typename":1830,"title":1886,"caption":1887,"layoutMode":1833,"file":1888},{"id":1032},"Supply chain attack timeline - PLG"," An example of a credential stuffing attack to compromise cloud identities",{"url":1889,"width":1843,"height":1890},"https://images.ctfassets.net/y1cdw1ablpvd/4dw9aikRRKmga5pVWBAXWU/0649644e0f0aaf29510738307546d5b1/image16.png",1104,{"sys":1892,"__typename":1830,"title":1893,"caption":1894,"layoutMode":1833,"file":1895},{"id":1096},"SSO only available for a small subset of apps","SSO is the gold standard, but a lack of universal support means we'll still need to deal with passwords for the foreseeable future.",{"url":1896,"width":1897,"height":1898},"https://images.ctfassets.net/y1cdw1ablpvd/7FDQf7atru96r1DRAjb52k/213136ebecccb073334878befc0c3dc8/image12.png",1790,1002,{"sys":1900,"__typename":1830,"title":1901,"caption":1902,"layoutMode":1833,"file":1903},{"id":1157},"Controls to prevent credential stuffing attacks - PLG","Controls to prevent credential stuffing attacks",{"url":1904,"width":1843,"height":1905},"https://images.ctfassets.net/y1cdw1ablpvd/7b0CDfnOLHjOAZgp9UMzlZ/8bdf95a1e66162f155c22db703f40048/image16.png",782,{"sys":1907,"__typename":1830,"title":1908,"caption":1909,"layoutMode":1833,"file":1910},{"id":1337},"SaaS discovery data source comparison","Strengths and weaknesses for finding employee SaaS use via commonly-used discovery data sources ",{"url":1911,"width":1912,"height":1913},"https://images.ctfassets.net/y1cdw1ablpvd/7FRyXaw4o4baUqG1cta41n/57a9476e83daf0386600c5bb8d4e827b/Screenshot_2023-04-24_at_9.09.16_AM.png",1796,1010,{"sys":1915,"__typename":1830,"title":1916,"caption":1916,"layoutMode":1833,"file":1917},{"id":1607},"Push SaaS dashboard",{"url":1918,"width":1843,"height":1919},"https://images.ctfassets.net/y1cdw1ablpvd/OsnXflsAKGaZU9Dl4lUTA/a49ef3631a4c35d259950dd395abc662/image9.png",1034,{"sys":1921,"__typename":1830,"title":1922,"caption":1923,"layoutMode":1833,"file":1924},{"id":1627},"Slack message new app alert for Security team","Channel message to security team via Slack about new app ",{"url":1925,"width":1843,"height":1919},"https://images.ctfassets.net/y1cdw1ablpvd/6CKhrva6Jh3jpHfnt0Maq5/edeeac0b00f1109e8601016f5a6e0c63/image17.png",{"sys":1927,"__typename":1830,"title":1928,"caption":1929,"layoutMode":1833,"file":1930},{"id":1747},"Push's account security dashboard","Push's account security dashboard shows you which accounts need attention",{"url":1931,"width":1932,"height":1933},"https://images.ctfassets.net/y1cdw1ablpvd/2LmWdqq57ZdIXHUSublBLK/eed71e0fa5c3039ae06f780c64057651/image4.png",1580,945,{"sys":1935,"__typename":1830,"title":1936,"caption":1937,"layoutMode":1833,"file":1938},{"id":1767},"Slack message to employee about MFA","Slack message to employee about enabling MFA for their SaaS account",{"url":1939,"width":1843,"height":1919},"https://images.ctfassets.net/y1cdw1ablpvd/1vWInHTSFEwt2kTXj0SK1I/5312ff9147b78837a71e367c9a59492f/image11.png",{"sys":1941,"__typename":1830,"title":1942,"caption":1943,"layoutMode":1833,"file":1944},{"id":1794},"Dropbox signin guidance","Push browser extension helping an employee securely sign up for Dropbox",{"url":1945,"width":1843,"height":1919},"https://images.ctfassets.net/y1cdw1ablpvd/7aqfsVnZS2LP1ur6SUdc4h/fc4cfddfa625af478238bc9303c34cf1/image8.png","json",{"items":1948},[],{},"How to find and secure shadow SaaS",{"url":1952},"https://images.ctfassets.net/y1cdw1ablpvd/2G9eUljiJXW11zOTpqRSUk/0e41dc83190b8be5d6ea8ec58d83da90/blog_image.png","2023-06-27T00:00:00.000Z",{"items":1955},[1956],{"__typename":1821,"sys":1957,"content":1958,"title":269,"synopsis":3417,"hashTags":62,"publishedDate":3418,"slug":1822,"tagsCollection":3419,"authorsCollection":3429},{"id":264},{"json":1959},{"nodeType":239,"data":1960,"content":1961},{},[1962,1968,1975,1982,1989,1996,2003,2010,2017,2060,2067,2074,2081,2088,2095,2101,2108,2115,2122,2130,2137,2144,2151,2158,2165,2172,2179,2199,2205,2212,2219,2231,2239,2246,2252,2259,2266,2272,2279,2288,2304,2327,2334,2341,2348,2355,2361,2368,2375,2382,2389,2396,2403,2423,2430,2437,2444,2451,2467,2500,2509,2516,2523,2530,2537,2544,2551,2558,2564,2571,2578,2585,2592,2599,2606,2626,2633,2638,2645,2668,2675,2682,2715,2722,2729,2736,2743,2756,2763,2834,2841,2848,2871,2876,2883,2890,2897,2930,2937,3338,3345,3364,3371,3380,3396,3403,3410],{"nodeType":243,"data":1963,"content":1964},{},[1965],{"nodeType":247,"value":248,"marks":1966,"data":1967},[],{},{"nodeType":252,"data":1969,"content":1970},{},[1971],{"nodeType":247,"value":1972,"marks":1973,"data":1974},"Employees using a new work app used to be the final step of the software-onboarding process. ",[],{},{"nodeType":252,"data":1976,"content":1977},{},[1978],{"nodeType":247,"value":1979,"marks":1980,"data":1981},"Now it's the first. ",[],{},{"nodeType":252,"data":1983,"content":1984},{},[1985],{"nodeType":247,"value":1986,"marks":1987,"data":1988},"SaaS vendors bypass IT and security and hook employees with free apps and trials. This has led to sensitive data on shadow SaaS applications (more on this later) that is accessible via unmanaged cloud accounts (accounts that aren’t protected by SSO or logged into via social login accounts). Attackers exploit this unmonitored attack surface with new takes on old techniques that are going undetected.",[],{},{"nodeType":252,"data":1990,"content":1991},{},[1992],{"nodeType":247,"value":1993,"marks":1994,"data":1995},"Employees self-adopting apps might sound like a security nightmare, but it doesn’t have to be. In fact, it can be a really good thing that enables employees to be more productive and your business to be more competitive. And, frankly, there’s no way to stop it without causing a SaaS sprawl issue. ",[],{},{"nodeType":252,"data":1997,"content":1998},{},[1999],{"nodeType":247,"value":2000,"marks":2001,"data":2002},"What’s clear is that this new landscape has fundamentally changed the way software is brought into the business. The days of security acting as a gatekeeper that all apps must pass through before they can touch live data are over. The market forces driving self-service apps aren’t stopping, so the security industry needs to adapt.",[],{},{"nodeType":252,"data":2004,"content":2005},{},[2006],{"nodeType":247,"value":2007,"marks":2008,"data":2009},"Security teams need to regain visibility and control over company data and how it’s secured. ",[],{},{"nodeType":252,"data":2011,"content":2012},{},[2013],{"nodeType":247,"value":2014,"marks":2015,"data":2016},"In this guide I’ll show security teams: ",[],{},{"nodeType":320,"data":2018,"content":2019},{},[2020,2030,2040,2050],{"nodeType":324,"data":2021,"content":2022},{},[2023],{"nodeType":252,"data":2024,"content":2025},{},[2026],{"nodeType":247,"value":2027,"marks":2028,"data":2029},"What’s driving employee app self-adoption and the impact on security teams",[],{},{"nodeType":324,"data":2031,"content":2032},{},[2033],{"nodeType":252,"data":2034,"content":2035},{},[2036],{"nodeType":247,"value":2037,"marks":2038,"data":2039},"Why the go-to solutions of policies and tools that block access to unsanctioned apps don’t work",[],{},{"nodeType":324,"data":2041,"content":2042},{},[2043],{"nodeType":252,"data":2044,"content":2045},{},[2046],{"nodeType":247,"value":2047,"marks":2048,"data":2049},"What new approaches can work and how to apply them",[],{},{"nodeType":324,"data":2051,"content":2052},{},[2053],{"nodeType":252,"data":2054,"content":2055},{},[2056],{"nodeType":247,"value":2057,"marks":2058,"data":2059},"The two aspects to address when securing SaaS and managing risk ",[],{},{"nodeType":252,"data":2061,"content":2062},{},[2063],{"nodeType":247,"value":2064,"marks":2065,"data":2066},"At the end of this book, we’ll link to a guide filled with practical guidance on how to manage those risks and quickly reduce your risk exposure. In that guide, we’ll also cover which data sources are available for SaaS security and why the choice is crucial.",[],{},{"nodeType":252,"data":2068,"content":2069},{},[2070],{"nodeType":247,"value":2071,"marks":2072,"data":2073},"The guidance provided here has been developed after talking with security leaders and CISOs that are already successfully embracing SaaS self-adoption while keeping a handle on risks. There are too many folks here to thank personally, but if you recognize some of this from our discussions, please accept my thanks, and hopefully there’s something new and useful here for you as well!",[],{},{"nodeType":243,"data":2075,"content":2076},{},[2077],{"nodeType":247,"value":2078,"marks":2079,"data":2080},"Why is it so easy for employees to self-adopt new apps without IT?",[],{},{"nodeType":621,"data":2082,"content":2083},{},[2084],{"nodeType":247,"value":2085,"marks":2086,"data":2087},"Memories of a simpler time",[],{},{"nodeType":252,"data":2089,"content":2090},{},[2091],{"nodeType":247,"value":2092,"marks":2093,"data":2094},"Before cloud computing was a thing, IT teams procured and managed hardware, software, networks and services for their businesses. The business was dependent on IT deploying new software across their on-prem network and managing it, so it was nearly impossible to bypass them. They became, in effect, the gatekeepers to the business’ IT environment. The onboarding process typically looked something like this:",[],{},{"nodeType":379,"data":2096,"content":2100},{"target":2097},{"sys":2098},{"id":2099,"type":265,"linkType":266},"1Dw4V0Fd0wI8yB6juzyWjg",[],{"nodeType":252,"data":2102,"content":2103},{},[2104],{"nodeType":247,"value":2105,"marks":2106,"data":2107},"IT asked Security to review a new app and its vendor to identify risks and determine if it should be adopted. At this point, security would specify which controls were required for it to be used securely. This all happened  before an app touched their network and interacted with any live data.",[],{},{"nodeType":252,"data":2109,"content":2110},{},[2111],{"nodeType":247,"value":2112,"marks":2113,"data":2114},"In return, Security could rely on IT to give them accurate information about all the businesses’ technology assets that needed to be protected. This process gave both teams great visibility across their total IT environment. Security and IT could maintain a high degree of control over how technology was used. ",[],{},{"nodeType":252,"data":2116,"content":2117},{},[2118],{"nodeType":247,"value":2119,"marks":2120,"data":2121},"In other words, life was wonderful and no one ever got hacked (maybe, it’s hard to remember now). Then the cloud happened and ruined everything.",[],{},{"nodeType":252,"data":2123,"content":2124},{},[2125],{"nodeType":247,"value":2126,"marks":2127,"data":2129},"Clearly I’m joking, but while very few orgs got it perfect, it was “good enough” at providing process-driven visibility of what enterprise software was being deployed for most.",[2128],{"type":272},{},{"nodeType":621,"data":2131,"content":2132},{},[2133],{"nodeType":247,"value":2134,"marks":2135,"data":2136},"The birth of the “as-a-Service” era",[],{},{"nodeType":252,"data":2138,"content":2139},{},[2140],{"nodeType":247,"value":2141,"marks":2142,"data":2143},"I jest, the cloud hasn’t ruined everything. It gave organizations the opportunity to be faster, more flexible and more efficient. Businesses no longer had to buy and manage all their own infrastructure and apps, they could just pay for what they used when they needed it. It led to a wave of “as-a-service” business models that stretched across infrastructure, platforms and software. ",[],{},{"nodeType":252,"data":2145,"content":2146},{},[2147],{"nodeType":247,"value":2148,"marks":2149,"data":2150},"Thousands of new software-as-a-service (SaaS) companies emerged with high quality apps that were easy to use over the internet. Essentially SaaS created software employees could use on-demand, which was a huge departure from the old days when IT and Security would do loads of security vetting upfront because they knew they’d be stuck with the software for years after deploying.",[],{},{"nodeType":252,"data":2152,"content":2153},{},[2154],{"nodeType":247,"value":2155,"marks":2156,"data":2157},"Leveraging great on-demand software tools boosted employee productivity and made their businesses more competitive. Tech-savvy employees, used to subscribing to on-demand software services in their personal lives, started to demand more autonomy over the technology they use at work. They were no longer satisfied with the generic suite of programs that IT could provide for them. Instead, they wanted the specialist tools designed and built for people like them by people like them. ",[],{},{"nodeType":252,"data":2159,"content":2160},{},[2161],{"nodeType":247,"value":2162,"marks":2163,"data":2164},"Despite users loving the software once they tried it, SaaS vendors were struggling to sell into large organizations with complicated procurement processes - it was too difficult to get their software in user's hands, and got more difficult the more niche and specialized the app was.",[],{},{"nodeType":621,"data":2166,"content":2167},{},[2168],{"nodeType":247,"value":2169,"marks":2170,"data":2171},"The rise of Product-Led Growth",[],{},{"nodeType":252,"data":2173,"content":2174},{},[2175],{"nodeType":247,"value":2176,"marks":2177,"data":2178},"Enter Wes Bush, a young SaaS marketer who published his book Product Led Growth in 2019. In it, he showed SaaS vendors how they can increase their sales revenues while reducing their sales cycles and costs by using their products as their primary go-to-market vehicle, as opposed to traditional sales teams. ",[],{},{"nodeType":252,"data":2180,"content":2181},{},[2182,2186,2195],{"nodeType":247,"value":2183,"marks":2184,"data":2185},"The premise is simple; prospective customers prefer to experience the value of a product rather than be told about it by sales people. Back in 2015 Forrester ",[],{},{"nodeType":930,"data":2187,"content":2189},{"uri":2188},"https://www.forrester.com/blogs/15-04-14-death_of_a_b2b_salesman/",[2190],{"nodeType":247,"value":2191,"marks":2192,"data":2194},"reported",[2193],{"type":938},{},{"nodeType":247,"value":2196,"marks":2197,"data":2198}," that 75% of B2B buyers prefer a sales-rep-free buying process. The book became a phenomenon within the SaaS industry. Product-led growth (PLG) is now the norm for SaaS companies, and around 60% of SaaS companies now use PLG and that’s only going to increase.",[],{},{"nodeType":379,"data":2200,"content":2204},{"target":2201},{"sys":2202},{"id":2203,"type":265,"linkType":266},"747PuaJ26IbolPB1ugxd2h",[],{"nodeType":252,"data":2206,"content":2207},{},[2208],{"nodeType":247,"value":2209,"marks":2210,"data":2211},"Why is PLG turning software adoption on its head? In order to establish a PLG go-to-market motion, SaaS vendors need end users to try their product, either as a free trial or a free version of the app, and quickly experience value from it so  they’re motivated to champion the internal business case through to a successful purchase. ",[],{},{"nodeType":252,"data":2213,"content":2214},{},[2215],{"nodeType":247,"value":2216,"marks":2217,"data":2218},"PLG not only relies upon end users as the initial adopters of a new app, but for them to experience meaningful value during that initial experience. This nearly always necessitates that the new app interacts with real data in a live environment. What’s more, it’s only the apps that end users want to use in a paid tier that are likely to ever get submitted to the app-onboarding process. The freemium and trial versions of apps that are just tried out are unlikely to ever be presented to IT and security. ",[],{},{"nodeType":252,"data":2220,"content":2221},{},[2222,2226],{"nodeType":247,"value":2223,"marks":2224,"data":2225},"This obviously poses a problem from an IT and security standpoint.",[],{},{"nodeType":247,"value":2227,"marks":2228,"data":2230}," ",[2229],{"type":299},{},{"nodeType":252,"data":2232,"content":2233},{},[2234],{"nodeType":247,"value":2235,"marks":2236,"data":2238},"SaaS vendors are deliberately bypassing the traditional software procurement processes that used to give IT and security teams visibility of the third party apps that had their data. ",[2237],{"type":299},{},{"nodeType":252,"data":2240,"content":2241},{},[2242],{"nodeType":247,"value":2243,"marks":2244,"data":2245},"Instead, SaaS vendors are directly targeting employees with their apps and encouraging them to plug them straight into live environments before they’ve been vetted. Software onboarding now looks a lot more like this:",[],{},{"nodeType":379,"data":2247,"content":2251},{"target":2248},{"sys":2249},{"id":2250,"type":265,"linkType":266},"61Oj6GzX4amLxEJ5fPDJCq",[],{"nodeType":621,"data":2253,"content":2254},{},[2255],{"nodeType":247,"value":2256,"marks":2257,"data":2258},"IT and security teams might be the last to know about PLG and miss the scale of the change",[],{},{"nodeType":252,"data":2260,"content":2261},{},[2262],{"nodeType":247,"value":2263,"marks":2264,"data":2265},"IT & security folks are usually ahead of the curve when it comes to technology shifts, but in this case many might have missed the scale or speed of the change. That’s because IT and security tools are among the least product-led of any sector. Most of our industry’s tools require heavy integrations, complicated setup, agent deployments, and so on. ",[],{},{"nodeType":379,"data":2267,"content":2271},{"target":2268},{"sys":2269},{"id":2270,"type":265,"linkType":266},"2ldVELsUQIU0xaPSPJyXBR",[],{"nodeType":252,"data":2273,"content":2274},{},[2275],{"nodeType":247,"value":2276,"marks":2277,"data":2278},"Unfortunately, few security companies are making products as easy to set up and use as new tools for marketing, sales, finance, development, engineering design, legal, HR, and basically every other sector that can’t rely on a technical first user. ",[],{},{"nodeType":252,"data":2280,"content":2281},{},[2282],{"nodeType":247,"value":2283,"marks":2284,"data":2287},"This leads to a misconception in IT and Security teams that self-adopted apps are fringe and don’t contain significant sensitive data.",[2285,2286],{"type":272},{"type":299},{},{"nodeType":252,"data":2289,"content":2290},{},[2291,2295,2300],{"nodeType":247,"value":2292,"marks":2293,"data":2294},"Most concerning for security teams is that ",[],{},{"nodeType":247,"value":2296,"marks":2297,"data":2299},"the sheer number of apps in use has increased dramatically",[2298],{"type":299},{},{"nodeType":247,"value":2301,"marks":2302,"data":2303}," and will continue to do so. There are a couple reasons for this: ",[],{},{"nodeType":1453,"data":2305,"content":2306},{},[2307,2317],{"nodeType":324,"data":2308,"content":2309},{},[2310],{"nodeType":252,"data":2311,"content":2312},{},[2313],{"nodeType":247,"value":2314,"marks":2315,"data":2316},"The big old monolithic on-prem software is being replaced not by a single SaaS app, but an ecosystem of specialized apps. Each new app integrates and extends the functionality as the team using the stack learns what they need, so there is a one-to-many shift happening. ",[],{},{"nodeType":324,"data":2318,"content":2319},{},[2320],{"nodeType":252,"data":2321,"content":2322},{},[2323],{"nodeType":247,"value":2324,"marks":2325,"data":2326},"Since apps are virtually zero-maintenance these days, the operating cost (if not the licensing cost) of running multiple apps is almost the same as one (compared to on-prem apps), so duplicate apps are far less of a problem. This also makes them pretty common and further multiplies the number of apps and vendors.",[],{},{"nodeType":243,"data":2328,"content":2329},{},[2330],{"nodeType":247,"value":2331,"marks":2332,"data":2333},"The impact of self-adoption on security",[],{},{"nodeType":621,"data":2335,"content":2336},{},[2337],{"nodeType":247,"value":2338,"marks":2339,"data":2340},"Loss of visibility",[],{},{"nodeType":252,"data":2342,"content":2343},{},[2344],{"nodeType":247,"value":2345,"marks":2346,"data":2347},"We’ve seen how SaaS vendors' move to PLG has led to greater employee self-adoption of work apps that don’t require IT or Security to be involved. The direct consequence of this is that Security teams have lost process-driven visibility of their company’s SaaS estate. This problem is often called “Shadow SaaS.” It is also the first problem to solve -  the old adage “you can’t secure what you don’t know about” is as true in the SaaS world as it is in any other security domain.",[],{},{"nodeType":252,"data":2349,"content":2350},{},[2351],{"nodeType":247,"value":2352,"marks":2353,"data":2354},"The lack of visibility means many IT and security teams missed the explosion of SaaS apps, plugins, extensions, and integrations that make up the modern IT stack.  More crucially, they’ve missed the movement of company data into these apps. Complicating matters further, many of these apps are duplicate, abandoned or unmanaged - an issue often called “SaaS sprawl.”",[],{},{"nodeType":379,"data":2356,"content":2360},{"target":2357},{"sys":2358},{"id":2359,"type":265,"linkType":266},"5NfrrDeIPs7TE213UYly7E",[],{"nodeType":621,"data":2362,"content":2363},{},[2364],{"nodeType":247,"value":2365,"marks":2366,"data":2367},"Increasing incidents and impacts",[],{},{"nodeType":252,"data":2369,"content":2370},{},[2371],{"nodeType":247,"value":2372,"marks":2373,"data":2374},"Though security teams have lost direct visibility, they’ve not lost complete visibility and many are finding out about at least a fraction of these apps - typically by working with finance teams once employees want apps to go from free-tier to licensed plans. And all too often, security teams find out about shadow SaaS apps in the worst way possible - when something has already gone wrong and security is asked to respond to an incident on a SaaS platform.",[],{},{"nodeType":252,"data":2376,"content":2377},{},[2378],{"nodeType":247,"value":2379,"marks":2380,"data":2381},"In both cases, security is getting visibility too late to be of much value. Once a team has been using an app (even on a free tier) for a year, there is very little Security can do that will convince them to move to a more secure app, or for multiple teams to use a single app. Typically, this intervention from Security needs to happen very early - long before finance is involved - in order to make a positive impact. ",[],{},{"nodeType":252,"data":2383,"content":2384},{},[2385],{"nodeType":247,"value":2386,"marks":2387,"data":2388},"Incident Response is necessary, of course, when a SaaS account is breached (or an ex-employee SaaS account that was never properly offboarded), but cannot recover the lost data after the proverbial horse has bolted. It’s now possible to get into the process early, so security teams can get ahead of the problem to reduce the risk.",[],{},{"nodeType":252,"data":2390,"content":2391},{},[2392],{"nodeType":247,"value":2393,"marks":2394,"data":2395},"Another situation that is increasingly pressing, and difficult for security teams to deal with is the increasingly regular: “App X has just had a major breach, are we using AppX, is any of our data there?” It’s an embarrassing situation to not be able to answer these questions.",[],{},{"nodeType":621,"data":2397,"content":2398},{},[2399],{"nodeType":247,"value":2400,"marks":2401,"data":2402},"Core problem",[],{},{"nodeType":252,"data":2404,"content":2405},{},[2406,2410,2419],{"nodeType":247,"value":2407,"marks":2408,"data":2409},"Once teams get visibility into the scope of the Shadow SaaS and sprawl problem, they find that Security no longer dictates the pace of adoption. They’re also typically surprised by the sheer volume of apps employees have adopted. A ",[],{},{"nodeType":930,"data":2411,"content":2413},{"uri":2412},"https://ascendixtech.com/number-saas-companies-statistics/",[2414],{"nodeType":247,"value":2415,"marks":2416,"data":2418},"report from Ascendix",[2417],{"type":938},{},{"nodeType":247,"value":2420,"marks":2421,"data":2422}," claims that “by the end of 2023, there will be anywhere from 30,000-72,000 SaaS companies in operation.” Clearly these aren’t all work apps or hyper specialized, but there should be no doubt that we aren’t talking about a few dozen apps being adopted.",[],{},{"nodeType":252,"data":2424,"content":2425},{},[2426],{"nodeType":247,"value":2427,"marks":2428,"data":2429},"Once teams get visibility of the pace that news apps are added they realize they need to risk assess dozens of apps a month instead of the dozen a year that were going through IT in the old, managed and controlled process. To deal with this massive influx of new apps, security teams feel they must either radically increase the headcount, cut corners or drastically increase acceptable risk levels for data security. None of these are pleasant options.",[],{},{"nodeType":621,"data":2431,"content":2432},{},[2433],{"nodeType":247,"value":2434,"marks":2435,"data":2436},"Temptation to revert to the old ways of block-first",[],{},{"nodeType":252,"data":2438,"content":2439},{},[2440],{"nodeType":247,"value":2441,"marks":2442,"data":2443},"When the idea of the options above proves daunting or impossible, Security often tries to revert to the old process - regain the ability to set the pace of adoption by re-establishing the gate. Practically, this means that you’re deploying technical controls to try block all SaaS apps until they are approved (and marked as allowed) by IT or Security. Cloud Access Security Brokers (CASBs) were built to do exactly this - help security teams control (and block) access to “unsanctioned” SaaS that IT hasn’t approved (incidentally I think this explains why the CASB segment has failed). ",[],{},{"nodeType":252,"data":2445,"content":2446},{},[2447],{"nodeType":247,"value":2448,"marks":2449,"data":2450},"Technically, this makes total sense. But the unforeseen consequence is that it positions Security as blockers (aka the “department of no”), and puts them at odds with the rest of the business, rather than working towards a shared goal. ",[],{},{"nodeType":252,"data":2452,"content":2453},{},[2454,2458,2463],{"nodeType":247,"value":2455,"marks":2456,"data":2457},"This block-everything-until-security-approves-it position requires incredible executive support to maintain. For all but the most risk-sensitive organizations (read .gov), this position also normalizes employee behavior to bypass Security in favor of working quickly and effectively. In the end, Security actually ",[],{},{"nodeType":247,"value":2459,"marks":2460,"data":2462},"loses visibility",[2461],{"type":272},{},{"nodeType":247,"value":2464,"marks":2465,"data":2466}," into employee SaaS use and effectively loses control, rather than locking it down. On behalf of all the employees out there, I want to make a point to say employees aren’t trying to break rules Security put in place, they’re just trying to get their jobs done, and might try and find ways around things they see as unreasonably slowing them down or preventing them from reaching their targets. Seen in this light, it’s no surprise that:",[],{},{"nodeType":320,"data":2468,"content":2469},{},[2470,2480,2490],{"nodeType":324,"data":2471,"content":2472},{},[2473],{"nodeType":252,"data":2474,"content":2475},{},[2476],{"nodeType":247,"value":2477,"marks":2478,"data":2479},"If you block websites, employees bypass network controls, ",[],{},{"nodeType":324,"data":2481,"content":2482},{},[2483],{"nodeType":252,"data":2484,"content":2485},{},[2486],{"nodeType":247,"value":2487,"marks":2488,"data":2489},"if you block social logins, employees use passwords, ",[],{},{"nodeType":324,"data":2491,"content":2492},{},[2493],{"nodeType":252,"data":2494,"content":2495},{},[2496],{"nodeType":247,"value":2497,"marks":2498,"data":2499},"if you stop them using work devices to sign up to apps, they use personal devices.",[],{},{"nodeType":252,"data":2501,"content":2502},{},[2503],{"nodeType":247,"value":2504,"marks":2505,"data":2508},"Each blocking action leads to a worse security outcome, and blinds the security team further - losing control rather than regaining it.",[2506,2507],{"type":272},{"type":299},{},{"nodeType":252,"data":2510,"content":2511},{},[2512],{"nodeType":247,"value":2513,"marks":2514,"data":2515},"You can attempt to delay this process by blocking, or you can adapt.",[],{},{"nodeType":621,"data":2517,"content":2518},{},[2519],{"nodeType":247,"value":2520,"marks":2521,"data":2522},"Surely there’s a better way",[],{},{"nodeType":252,"data":2524,"content":2525},{},[2526],{"nodeType":247,"value":2527,"marks":2528,"data":2529},"Of course we think there’s a better way, or we wouldn’t have written this. And don’t call me Shirley. ",[],{},{"nodeType":252,"data":2531,"content":2532},{},[2533],{"nodeType":247,"value":2534,"marks":2535,"data":2536},"The first thing we need to do as an industry is agree that we don’t want to be the blockers. We don’t want to stop employees from self-adopting apps. We understand they are best placed to find and select the tools that are going to allow them to be more productive and help your company succeed. We need to embrace SaaS app self-adoption. Stop asking employees to adapt to fit our legacy processes and meet them halfway. Security can no longer be a gate with a default stance of “No, until.” Instead Security needs to be a business enablement partner that says “Yes, unless.”",[],{},{"nodeType":621,"data":2538,"content":2539},{},[2540],{"nodeType":247,"value":2541,"marks":2542,"data":2543},"Yes, unless?",[],{},{"nodeType":252,"data":2545,"content":2546},{},[2547],{"nodeType":247,"value":2548,"marks":2549,"data":2550},"To adapt to this new SaaS-first world, security must move from saying “No, until we’ve had time to fully vet and onboard this app officially” to “Yes! You can use that app, unless we quickly identify security risks that outweigh the value of the tool.” I understand this is deeply uncomfortable for many security practitioners (as it still is for me), but let me explain why I think this leads to a better long-term outcome.",[],{},{"nodeType":252,"data":2552,"content":2553},{},[2554],{"nodeType":247,"value":2555,"marks":2556,"data":2557},"Obviously, self-adoption of SaaS is fundamentally different to IT/Security adopted and managed from a risk perspective. With SaaS, there’s no giant commitment upfront. SaaS apps aren’t forever - quite the opposite! Apps aren’t just unused and not-adopted and then suddenly fully-adopted. Just like adopting software was a process for Security and IT back in the day, employees follow a (less rigid) process with SaaS - from testing > to using > to finding value > to inviting teammates, etc. The risk grows as we proceed through the adoption process as employees add more data into the app and integrate it with other apps. ",[],{},{"nodeType":379,"data":2559,"content":2563},{"target":2560},{"sys":2561},{"id":2562,"type":265,"linkType":266},"2nzyuXDxjBGZN0YMvskGak",[],{"nodeType":252,"data":2565,"content":2566},{},[2567],{"nodeType":247,"value":2568,"marks":2569,"data":2570},"The upside for Security is that because SaaS adoption is a process over time, we can use that time to assess the risk of the app before it’s fully adopted, as long as we know about the app from the start. Luckily, many apps employees are using might ultimately be very low risk, so not every app will require a full security vetting like you would have done in the old-school process.",[],{},{"nodeType":252,"data":2572,"content":2573},{},[2574],{"nodeType":247,"value":2575,"marks":2576,"data":2577},"Our role as Security is to catch those apps that are high risk, either because the data going into them (or that will be) is high risk or because the app can perform some high-risk action (like managing your inventory or sending emails to customers or your behalf). Security can focus their efforts on these high-risk vendors and apps to make sure they can be trusted with their data. But the key thing is that Security needs to get involved early in the adoption process. ",[],{},{"nodeType":252,"data":2579,"content":2580},{},[2581],{"nodeType":247,"value":2582,"marks":2583,"data":2584},"I’m getting into the details now - so this feels like a good time to take a step back and think about the elements that make up a SaaS security program.",[],{},{"nodeType":243,"data":2586,"content":2587},{},[2588],{"nodeType":247,"value":2589,"marks":2590,"data":2591},"What’s a good SaaS security program?",[],{},{"nodeType":252,"data":2593,"content":2594},{},[2595],{"nodeType":247,"value":2596,"marks":2597,"data":2598},"The shared-responsibility model between cloud platforms and their customers is a great place to start, as it helps customers understand what their responsibilities are, and which responsibilities they’re delegating to their cloud provider.",[],{},{"nodeType":621,"data":2600,"content":2601},{},[2602],{"nodeType":247,"value":2603,"marks":2604,"data":2605},"Delegate to the cloud provider when you can ",[],{},{"nodeType":252,"data":2607,"content":2608},{},[2609,2613,2622],{"nodeType":247,"value":2610,"marks":2611,"data":2612},"It’s ",[],{},{"nodeType":930,"data":2614,"content":2616},{"uri":2615},"https://www.ncsc.gov.uk/collection/cloud/understanding-cloud-services/cloud-security-shared-responsibility-model",[2617],{"nodeType":247,"value":2618,"marks":2619,"data":2621},"generally preferable",[2620],{"type":938},{},{"nodeType":247,"value":2623,"marks":2624,"data":2625}," to delegate as much responsibility as possible to the cloud provider, so it’s no surprise that the SaaS model is the most common and fastest growing sector.",[],{},{"nodeType":252,"data":2627,"content":2628},{},[2629],{"nodeType":247,"value":2630,"marks":2631,"data":2632},"The following summary table produced by the National Cyber Security Centre (NCSC) does a great job at showing how much of the balance of security responsibility is outsourced to the SaaS provider. For reference, IaaS = infrastructure-as-a-service; PaaS = platform-as-a-service; SaaS = software-as-a-service:",[],{},{"nodeType":379,"data":2634,"content":2637},{"target":2635},{"sys":2636},{"id":383,"type":265,"linkType":266},[],{"nodeType":252,"data":2639,"content":2640},{},[2641],{"nodeType":247,"value":2642,"marks":2643,"data":2644},"According to NCSC, the customer is responsible only for:",[],{},{"nodeType":1453,"data":2646,"content":2647},{},[2648,2658],{"nodeType":324,"data":2649,"content":2650},{},[2651],{"nodeType":252,"data":2652,"content":2653},{},[2654],{"nodeType":247,"value":2655,"marks":2656,"data":2657},"The configuration of the SaaS app and ",[],{},{"nodeType":324,"data":2659,"content":2660},{},[2661],{"nodeType":252,"data":2662,"content":2663},{},[2664],{"nodeType":247,"value":2665,"marks":2666,"data":2667},"Making sure that the identity and access control features provided by the vendor are used properly.",[],{},{"nodeType":252,"data":2669,"content":2670},{},[2671],{"nodeType":247,"value":2672,"marks":2673,"data":2674},"It’s worth pointing out here that the way application configuration is presented here is a bit of a red herring. The vast majority of SaaS apps (and especially self-adopted apps) allow very little, if any, configuration. Sure, the big core apps like Salesforce, Google Workspace, Microsoft 365 do (and often require a dedicated team or partner to run them), but they are highly unlikely to be self-adopted by employees.  As far as configuration is concerned, Security teams will often be limited to enabling “force MFA for all users” or “disallow public sharing” type of controls that are accessible even to non-technical users.",[],{},{"nodeType":252,"data":2676,"content":2677},{},[2678],{"nodeType":247,"value":2679,"marks":2680,"data":2681},"For the vast majority of apps in the organization, Security’s responsibility will boil down to:",[],{},{"nodeType":320,"data":2683,"content":2684},{},[2685,2695,2705],{"nodeType":324,"data":2686,"content":2687},{},[2688],{"nodeType":252,"data":2689,"content":2690},{},[2691],{"nodeType":247,"value":2692,"marks":2693,"data":2694},"Account security, i.e. making sure MFA and SSO (where available) is in place. ",[],{},{"nodeType":324,"data":2696,"content":2697},{},[2698],{"nodeType":252,"data":2699,"content":2700},{},[2701],{"nodeType":247,"value":2702,"marks":2703,"data":2704},"Ensuring  employees are using strong passwords, especially if MFA and/or SSO aren’t available.",[],{},{"nodeType":324,"data":2706,"content":2707},{},[2708],{"nodeType":252,"data":2709,"content":2710},{},[2711],{"nodeType":247,"value":2712,"marks":2713,"data":2714},"Removing external accounts (and accounts for those that have left the company) when no longer needed.",[],{},{"nodeType":252,"data":2716,"content":2717},{},[2718],{"nodeType":247,"value":2719,"marks":2720,"data":2721},"Isn’t it risky to delegate responsibility? While delegating security responsibilities is great and takes a huge load off your team, we do, unfortunately, need to consider who we’re delegating it to. Those gray boxes in the diagram above need to be taken care of.",[],{},{"nodeType":252,"data":2723,"content":2724},{},[2725],{"nodeType":247,"value":2726,"marks":2727,"data":2728},"This is what’s sometimes understood as “supply chain” security. You need to trust the SaaS vendor to uphold their end of the bargain and, more often than not, also the SaaS/cloud vendors they use (their sub-processors) as well.",[],{},{"nodeType":252,"data":2730,"content":2731},{},[2732],{"nodeType":247,"value":2733,"marks":2734,"data":2735},"This sounds a lot scarier than it is and in practice many SaaS vendors do a great job, with many providing easy-to-audit, externally-verified, policies through a framework such as SOC2, and most do regular penetration tests and have bug bounty programs etc.",[],{},{"nodeType":252,"data":2737,"content":2738},{},[2739],{"nodeType":247,"value":2740,"marks":2741,"data":2742},"There are exceptions when it makes sense to think more carefully about whether a third party can be trusted. Common reasons Push customers have cited for not trusting third parties include; ",[],{},{"nodeType":320,"data":2744,"content":2745},{},[2746],{"nodeType":324,"data":2747,"content":2748},{},[2749],{"nodeType":252,"data":2750,"content":2751},{},[2752],{"nodeType":247,"value":2753,"marks":2754,"data":2755},"The data going into these apps is simply too high risk. Many organizations have very sensitive customer information or intellectual property that they simply aren’t willing to entrust to a third party. Many don’t trust a third party with administrative access to the systems where this data is held.",[],{},{"nodeType":252,"data":2757,"content":2758},{},[2759],{"nodeType":247,"value":2760,"marks":2761,"data":2762},"If the data in the app, or the access the app has represents some significant (but not unacceptable) risk, you may also care about:",[],{},{"nodeType":320,"data":2764,"content":2765},{},[2766,2814,2824],{"nodeType":324,"data":2767,"content":2768},{},[2769],{"nodeType":252,"data":2770,"content":2771},{},[2772,2776,2785,2789,2798,2801,2810],{"nodeType":247,"value":2773,"marks":2774,"data":2775},"Vendors who’ve had a string of repeated breaches or security incidents. This is troubling because it’s a fairly common pattern for attackers to breach apps in ways that don’t impact customer information, but then use the information they learn from these breaches to launch far more successful breaches in future. Consider the string of breaches at ",[],{},{"nodeType":930,"data":2777,"content":2779},{"uri":2778},"https://www.bleepingcomputer.com/search/?q=lastpass+breach",[2780],{"nodeType":247,"value":2781,"marks":2782,"data":2784},"LastPass",[2783],{"type":938},{},{"nodeType":247,"value":2786,"marks":2787,"data":2788},", ",[],{},{"nodeType":930,"data":2790,"content":2792},{"uri":2791},"https://www.bleepingcomputer.com/search/?q=okta+breach",[2793],{"nodeType":247,"value":2794,"marks":2795,"data":2797},"Okta",[2796],{"type":938},{},{"nodeType":247,"value":2786,"marks":2799,"data":2800},[],{},{"nodeType":930,"data":2802,"content":2804},{"uri":2803},"https://www.bleepingcomputer.com/search/?q=twilio+breach",[2805],{"nodeType":247,"value":2806,"marks":2807,"data":2809},"Twilio",[2808],{"type":938},{},{"nodeType":247,"value":2811,"marks":2812,"data":2813}," (and many others) or as a typical example of this.",[],{},{"nodeType":324,"data":2815,"content":2816},{},[2817],{"nodeType":252,"data":2818,"content":2819},{},[2820],{"nodeType":247,"value":2821,"marks":2822,"data":2823},"Products that don’t offer adequate security features. Customers expect features such as MFA, SSO (either social login through OIDC or, ideally, SAML), and the ability to enforce these controls. This is especially important on platforms where the data is high-risk.",[],{},{"nodeType":324,"data":2825,"content":2826},{},[2827],{"nodeType":252,"data":2828,"content":2829},{},[2830],{"nodeType":247,"value":2831,"marks":2832,"data":2833},"The vendor operates in a sanctioned country or may not have the resources to adequately protect your data. Clearly vendors operating from (or that have close ties with) sanctioned or politically-complicated countries represent additional risk, as do vendors that are “one man bands” or are so small that it is hard to imagine they can afford to spend significant resources on security.",[],{},{"nodeType":621,"data":2835,"content":2836},{},[2837],{"nodeType":247,"value":2838,"marks":2839,"data":2840},"The two questions you need to ask to assess risk ",[],{},{"nodeType":252,"data":2842,"content":2843},{},[2844],{"nodeType":247,"value":2845,"marks":2846,"data":2847},"The essence of the shared-responsibility model can summarized as two questions:",[],{},{"nodeType":1453,"data":2849,"content":2850},{},[2851,2861],{"nodeType":324,"data":2852,"content":2853},{},[2854],{"nodeType":252,"data":2855,"content":2856},{},[2857],{"nodeType":247,"value":2858,"marks":2859,"data":2860},"Should we be using this app?",[],{},{"nodeType":324,"data":2862,"content":2863},{},[2864],{"nodeType":252,"data":2865,"content":2866},{},[2867],{"nodeType":247,"value":2868,"marks":2869,"data":2870},"Are we using it securely?",[],{},{"nodeType":379,"data":2872,"content":2875},{"target":2873},{"sys":2874},{"id":410,"type":265,"linkType":266},[],{"nodeType":252,"data":2877,"content":2878},{},[2879],{"nodeType":247,"value":2880,"marks":2881,"data":2882},"A successful SaaS security program must address both these questions. We can’t spend all our time doing risk assessments and due diligence exercises on our supply chain while dropping the ball on account security. Similarly, we can’t just focus on making sure all accounts have MFA in place when the vendor is leaving the back door open.",[],{},{"nodeType":243,"data":2884,"content":2885},{},[2886],{"nodeType":247,"value":2887,"marks":2888,"data":2889},"When shared responsibility goes wrong",[],{},{"nodeType":252,"data":2891,"content":2892},{},[2893],{"nodeType":247,"value":2894,"marks":2895,"data":2896},"The following is an extract of some well-covered recent(ish) breaches of SaaS companies. As we go through it, pay attention to which side is dropping the ball in terms of the shared responsibility. The same organization can be:",[],{},{"nodeType":320,"data":2898,"content":2899},{},[2900,2910,2920],{"nodeType":324,"data":2901,"content":2902},{},[2903],{"nodeType":252,"data":2904,"content":2905},{},[2906],{"nodeType":247,"value":2907,"marks":2908,"data":2909},"the source of a breach, ",[],{},{"nodeType":324,"data":2911,"content":2912},{},[2913],{"nodeType":252,"data":2914,"content":2915},{},[2916],{"nodeType":247,"value":2917,"marks":2918,"data":2919},"the ultimate target that motivated a breach at a partner that was a softer target, ",[],{},{"nodeType":324,"data":2921,"content":2922},{},[2923],{"nodeType":252,"data":2924,"content":2925},{},[2926],{"nodeType":247,"value":2927,"marks":2928,"data":2929},"or simply the unlucky victim of a breach further down its supply chain.",[],{},{"nodeType":252,"data":2931,"content":2932},{},[2933],{"nodeType":247,"value":2934,"marks":2935,"data":2936},"That’s the thing about supply chain attacks, organizations are the attacker’s stepping stones. Where they are in the attack chain determines how we label their victims. ",[],{},{"nodeType":2938,"data":2939,"content":2940},"table",{},[2941,2968,3049,3106,3149,3275],{"nodeType":2942,"data":2943,"content":2944},"table-row",{},[2945,2957],{"nodeType":2946,"data":2947,"content":2948},"table-cell",{},[2949],{"nodeType":252,"data":2950,"content":2951},{},[2952],{"nodeType":247,"value":2953,"marks":2954,"data":2956},"Date",[2955],{"type":299},{},{"nodeType":2946,"data":2958,"content":2959},{},[2960],{"nodeType":252,"data":2961,"content":2962},{},[2963],{"nodeType":247,"value":2964,"marks":2965,"data":2967},"SaaS attack",[2966],{"type":299},{},{"nodeType":2942,"data":2969,"content":2970},{},[2971,2981],{"nodeType":2946,"data":2972,"content":2973},{},[2974],{"nodeType":252,"data":2975,"content":2976},{},[2977],{"nodeType":247,"value":2978,"marks":2979,"data":2980},"April 2021",[],{},{"nodeType":2946,"data":2982,"content":2983},{},[2984,3012],{"nodeType":252,"data":2985,"content":2986},{},[2987,2990,2999,3003,3008],{"nodeType":247,"value":29,"marks":2988,"data":2989},[],{},{"nodeType":930,"data":2991,"content":2993},{"uri":2992},"https://about.codecov.io/security-update/",[2994],{"nodeType":247,"value":2995,"marks":2996,"data":2998},"Backdoors inserted into some Codecov.io",[2997],{"type":938},{},{"nodeType":247,"value":3000,"marks":3001,"data":3002}," (a software development SaaS) tools after a credential breach grants access to their ",[],{},{"nodeType":247,"value":3004,"marks":3005,"data":3007},"Google Cloud Project",[3006],{"type":299},{},{"nodeType":247,"value":3009,"marks":3010,"data":3011}," (cloud infrastructure SaaS).  ",[],{},{"nodeType":252,"data":3013,"content":3014},{},[3015,3019,3028,3032,3037,3041,3045],{"nodeType":247,"value":3016,"marks":3017,"data":3018},"This breach ",[],{},{"nodeType":930,"data":3020,"content":3022},{"uri":3021},"https://www.twilio.com/blog/response-to-the-codecov-vulnerability",[3023],{"nodeType":247,"value":3024,"marks":3025,"data":3027},"affected multiple customers",[3026],{"type":938},{},{"nodeType":247,"value":3029,"marks":3030,"data":3031},", including ",[],{},{"nodeType":247,"value":3033,"marks":3034,"data":3036},"Atlassian",[3035],{"type":299},{},{"nodeType":247,"value":3038,"marks":3039,"data":3040}," (a developer and collaboration SaaS platform) and ",[],{},{"nodeType":247,"value":2806,"marks":3042,"data":3044},[3043],{"type":299},{},{"nodeType":247,"value":3046,"marks":3047,"data":3048}," (communications tooling SaaS company).  ",[],{},{"nodeType":2942,"data":3050,"content":3051},{},[3052,3062],{"nodeType":2946,"data":3053,"content":3054},{},[3055],{"nodeType":252,"data":3056,"content":3057},{},[3058],{"nodeType":247,"value":3059,"marks":3060,"data":3061},"Jan 2022",[],{},{"nodeType":2946,"data":3063,"content":3064},{},[3065],{"nodeType":252,"data":3066,"content":3067},{},[3068,3072,3076,3085,3089,3094,3098,3102],{"nodeType":247,"value":2794,"marks":3069,"data":3071},[3070],{"type":299},{},{"nodeType":247,"value":3073,"marks":3074,"data":3075}," (identity provider SaaS) ",[],{},{"nodeType":930,"data":3077,"content":3079},{"uri":3078},"https://www.okta.com/blog/2022/03/oktas-investigation-of-the-january-2022-compromise/",[3080],{"nodeType":247,"value":3081,"marks":3082,"data":3084},"systems breached",[3083],{"type":938},{},{"nodeType":247,"value":3086,"marks":3087,"data":3088}," through a breach at ",[],{},{"nodeType":247,"value":3090,"marks":3091,"data":3093},"Sitel",[3092],{"type":299},{},{"nodeType":247,"value":3095,"marks":3096,"data":3097},", a support partner - attackers got access to Okta’s instances of ",[],{},{"nodeType":247,"value":3033,"marks":3099,"data":3101},[3100],{"type":299},{},{"nodeType":247,"value":3103,"marks":3104,"data":3105}," Jira, Slack, Splunk, RingCentral, and support tickets through Salesforce.  ",[],{},{"nodeType":2942,"data":3107,"content":3108},{},[3109,3119],{"nodeType":2946,"data":3110,"content":3111},{},[3112],{"nodeType":252,"data":3113,"content":3114},{},[3115],{"nodeType":247,"value":3116,"marks":3117,"data":3118},"March 2022",[],{},{"nodeType":2946,"data":3120,"content":3121},{},[3122],{"nodeType":252,"data":3123,"content":3124},{},[3125,3129,3133,3137,3146],{"nodeType":247,"value":3126,"marks":3127,"data":3128},"“0ktapus” phishing toolkit targeting ",[],{},{"nodeType":247,"value":2794,"marks":3130,"data":3132},[3131],{"type":299},{},{"nodeType":247,"value":3134,"marks":3135,"data":3136}," customers ",[],{},{"nodeType":930,"data":3138,"content":3140},{"uri":3139},"https://www.bleepingcomputer.com/news/security/twilio-hackers-hit-over-130-orgs-in-massive-okta-phishing-attack/",[3141],{"nodeType":247,"value":3142,"marks":3143,"data":3145},"is released",[3144],{"type":938},{},{"nodeType":247,"value":29,"marks":3147,"data":3148},[],{},{"nodeType":2942,"data":3150,"content":3151},{},[3152,3162],{"nodeType":2946,"data":3153,"content":3154},{},[3155],{"nodeType":252,"data":3156,"content":3157},{},[3158],{"nodeType":247,"value":3159,"marks":3160,"data":3161},"Aug 2022",[],{},{"nodeType":2946,"data":3163,"content":3164},{},[3165,3206,3233,3248,3268],{"nodeType":252,"data":3166,"content":3167},{},[3168,3172,3176,3180,3184,3193,3197,3202],{"nodeType":247,"value":2806,"marks":3169,"data":3171},[3170],{"type":299},{},{"nodeType":247,"value":3173,"marks":3174,"data":3175}," (one such ",[],{},{"nodeType":247,"value":2794,"marks":3177,"data":3179},[3178],{"type":299},{},{"nodeType":247,"value":3181,"marks":3182,"data":3183}," customer) ",[],{},{"nodeType":930,"data":3185,"content":3187},{"uri":3186},"https://www.twilio.com/blog/august-2022-social-engineering-attack",[3188],{"nodeType":247,"value":3189,"marks":3190,"data":3192},"was again breached",[3191],{"type":938},{},{"nodeType":247,"value":3194,"marks":3195,"data":3196}," and attackers used access to one of their products (",[],{},{"nodeType":247,"value":3198,"marks":3199,"data":3201},"Authy",[3200],{"type":299},{},{"nodeType":247,"value":3203,"marks":3204,"data":3205},", an MFA mobile app) to bypass MFA for some of their customers. ",[],{},{"nodeType":252,"data":3207,"content":3208},{},[3209,3213,3217,3220,3229],{"nodeType":247,"value":3210,"marks":3211,"data":3212},"Attackers appear to also have used ",[],{},{"nodeType":247,"value":2806,"marks":3214,"data":3216},[3215],{"type":299},{},{"nodeType":247,"value":2227,"marks":3218,"data":3219},[],{},{"nodeType":930,"data":3221,"content":3223},{"uri":3222},"https://www.bleepingcomputer.com/news/security/okta-one-time-mfa-passcodes-exposed-in-twilio-cyberattack/",[3224],{"nodeType":247,"value":3225,"marks":3226,"data":3228},"to gain access to SMS’s",[3227],{"type":938},{},{"nodeType":247,"value":3230,"marks":3231,"data":3232}," that were delivering Okta MFA codes to customers: ",[],{},{"nodeType":252,"data":3234,"content":3235},{},[3236,3240,3244],{"nodeType":247,"value":3237,"marks":3238,"data":3239},"This leads to a breach at",[],{},{"nodeType":247,"value":2227,"marks":3241,"data":3243},[3242],{"type":299},{},{"nodeType":247,"value":3245,"marks":3246,"data":3247},"Mailchimp (email marketing SaaS), which in turn affects many upstream customers like Digital Ocean (infrastructure hosting SaaS) and Signal Messenger",[],{},{"nodeType":252,"data":3249,"content":3250},{},[3251,3255,3264],{"nodeType":247,"value":3252,"marks":3253,"data":3254},"Klaviyo (another email marketing SaaS) ",[],{},{"nodeType":930,"data":3256,"content":3258},{"uri":3257},"https://www.bleepingcomputer.com/news/security/email-marketing-firm-hacked-to-steal-crypto-focused-mailing-lists/",[3259],{"nodeType":247,"value":3260,"marks":3261,"data":3263},"is also impacted",[3262],{"type":938},{},{"nodeType":247,"value":3265,"marks":3266,"data":3267},". ",[],{},{"nodeType":252,"data":3269,"content":3270},{},[3271],{"nodeType":247,"value":3272,"marks":3273,"data":3274},"Breaches on these email marketing SaaS apps lead to even more downstream breaches for customers in finance and crypto spaces, such as Trezor, Edge Wallet, Cointelegraph, Ethereum FESP, Messari and Decrypt.",[],{},{"nodeType":2942,"data":3276,"content":3277},{},[3278,3288],{"nodeType":2946,"data":3279,"content":3280},{},[3281],{"nodeType":252,"data":3282,"content":3283},{},[3284],{"nodeType":247,"value":3285,"marks":3286,"data":3287},"Sept and Dec 2022",[],{},{"nodeType":2946,"data":3289,"content":3290},{},[3291],{"nodeType":252,"data":3292,"content":3293},{},[3294,3298,3307,3311,3315,3319,3334],{"nodeType":247,"value":3295,"marks":3296,"data":3297},"Product source code ",[],{},{"nodeType":930,"data":3299,"content":3301},{"uri":3300},"https://www.bleepingcomputer.com/news/security/oktas-source-code-stolen-after-github-repositories-hacked/",[3302],{"nodeType":247,"value":3303,"marks":3304,"data":3306},"stolen from the Github repositories",[3305],{"type":938},{},{"nodeType":247,"value":3308,"marks":3309,"data":3310}," of ",[],{},{"nodeType":247,"value":2794,"marks":3312,"data":3314},[3313],{"type":299},{},{"nodeType":247,"value":3316,"marks":3317,"data":3318}," and ",[],{},{"nodeType":930,"data":3320,"content":3322},{"uri":3321},"https://www.bleepingcomputer.com/news/security/auth0-warns-that-some-source-code-repos-may-have-been-stolen/",[3323,3329],{"nodeType":247,"value":3324,"marks":3325,"data":3328},"Auth0",[3326,3327],{"type":938},{"type":299},{},{"nodeType":247,"value":3330,"marks":3331,"data":3333}," (an Okta subsidiary",[3332],{"type":938},{},{"nodeType":247,"value":3335,"marks":3336,"data":3337}," that is also an identity provider SaaS platform)",[],{},{"nodeType":252,"data":3339,"content":3340},{},[3341],{"nodeType":247,"value":3342,"marks":3343,"data":3344},"This is a very shallow summary of a small sample of events during this time frame, but it’s interesting how interrelated these SaaS services are. Many are part of each other’s supply chains (for example, Twilio is targeted as an Okta customer itself, and used to compromise Okta customer MFA codes that are delivered by Twilio to other Okta customers) and so breaches in one SaaS have rippling effects that sometimes take months or even years to materialize after a breach occurs.",[],{},{"nodeType":252,"data":3346,"content":3347},{},[3348,3352,3360],{"nodeType":247,"value":3349,"marks":3350,"data":3351},"There’s an interesting trend to call out here: breaches at a SaaS vendor appear to lead to (or correlate with) further breaches, such as the string of breaches at ",[],{},{"nodeType":930,"data":3353,"content":3355},{"uri":3354},"https://thehackernews.com/2023/02/lastpass-reveals-second-attack.html",[3356],{"nodeType":247,"value":2781,"marks":3357,"data":3359},[3358],{"type":938},{},{"nodeType":247,"value":3361,"marks":3362,"data":3363},". But it’s incredibly unclear how to balance the risk of using these vendors, especially when some of these companies (like Okta) are a big part of many organization’s security strategies.",[],{},{"nodeType":252,"data":3365,"content":3366},{},[3367],{"nodeType":247,"value":3368,"marks":3369,"data":3370},"Ultimately, though… ",[],{},{"nodeType":252,"data":3372,"content":3373},{},[3374],{"nodeType":247,"value":3375,"marks":3376,"data":3379},"The root of most of these networks of supply chain attacks are simple account compromises. ",[3377,3378],{"type":299},{"type":272},{},{"nodeType":252,"data":3381,"content":3382},{},[3383,3387,3392],{"nodeType":247,"value":3384,"marks":3385,"data":3386},"While most organizations think of the supply chain aspect (should we be using this app?) as the majority of the problem, or at least the first problem to solve - ",[],{},{"nodeType":247,"value":3388,"marks":3389,"data":3391},"account security",[3390],{"type":272},{},{"nodeType":247,"value":3393,"marks":3394,"data":3395}," is ultimately at the heart of the problem. A developer or support engineer with a weak password or missing MFA is all it takes for them to get phished, kicking off this string of attacks. Unlike the complex supply chain risk questions, account security issues are straightforward to fix. We’d be a whole lot closer to securing the whole supply chain if we could improve account security for all employees across all the SaaS apps they use. ",[],{},{"nodeType":243,"data":3397,"content":3398},{},[3399],{"nodeType":247,"value":3400,"marks":3401,"data":3402},"Where do we go from here?",[],{},{"nodeType":252,"data":3404,"content":3405},{},[3406],{"nodeType":247,"value":3407,"marks":3408,"data":3409},"So we’ve discussed the domino-like string of effects from SaaS sales, to PLG, to self-adoption, to shadow SaaS, to growing SaaS risks and the news stories we read about.",[],{},{"nodeType":252,"data":3411,"content":3412},{},[3413],{"nodeType":247,"value":3414,"marks":3415,"data":3416},"We’ve unpacked the shared responsibility model - and I hope I’ve convinced you that we need to look at both the supply chain and account security side equally (and in parallel!) to manage this risk. ",[],{},"Employees using a new work app used to be the final step of the software-onboarding process. Now it's the first. Security must adapt to secure business data. \n","2023-06-22T00:00:00.000Z",{"items":3420},[3421,3425],{"sys":3422,"name":3424},{"id":3423},"6A5RXS31ZQx3PwryGb1IMy","Browser-based attacks",{"sys":3426,"name":3428},{"id":3427},"3SA5H01UkKauuiTdt0KC6q","Shadow IT",{"items":3430},[3431],{"fullName":232,"firstName":233,"jobTitle":234,"profilePicture":3432},{"url":236},"protect-your-data-across-all-your-apps-even-the-ones-employees-use-without","blog/protect-your-data-across-all-your-apps-even-the-ones-employees-use-without",{"json":3436},{"data":3437,"content":3438,"nodeType":239},{},[3439],{"data":3440,"content":3441,"nodeType":252},{},[3442],{"data":3443,"marks":3444,"value":3445,"nodeType":247},{},[],"SaaS vendors want your employees to self-adopt their apps and start using them (and integrating with your data to do so). This leaves security and IT teams blind to which apps sensitive company data is flowing into. We’ll offer some practical guidance on how to manage supply chain risk without slowing down the business.","Adapt your thinking to secure your data. Security needs to move from being the Department of No to the Department of Yes, Unless... ",{"id":3448,"publishedAt":3449},"tkUfN6TKuYyVNYDpsGWrE","2026-01-30T09:37:41.871Z",{"items":3451},[3452,3456],{"sys":3453,"name":3455},{"id":3454},"1gZi8NrRy2v9OqPV7C4dwD","Risk management",{"sys":3457,"name":3428},{"id":3427},"4_qn9eHV4eSpjV9npQy2d59ntCzeD3vqMRVQSlfdvcQ",1784196716935]