[{"data":1,"prerenderedAt":1375},["ShallowReactive",2],{"application-flags":3,"navbar":7,"always-visible-banner":36,"navbar-about-highlight":108,"navbar-resource-highlight":182,"blog/how-to-kick-off-an-incident-response-investigation-for-a-compromised-saas":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":785,"faqItemsCollection":786,"faqTitle":62,"featured":6,"hashTags":62,"meta":788,"metaTitle":789,"ogImage":62,"publishedDate":790,"relatedBlogPostsCollection":791,"slug":1349,"stem":1350,"subtitle":62,"summary":1351,"synopsis":1362,"sys":1363,"tagsCollection":1366,"__hash__":1374},"blog/blog/how-to-kick-off-an-incident-response-investigation-for-a-compromised-saas.json","How to kick off an incident response investigation for a compromised SaaS account",{"items":230},[231],{"fullName":232,"firstName":233,"jobTitle":234,"profilePicture":235},"Johann Scheepers","Johann","Senior Security Engineer",{"url":236},"https://images.ctfassets.net/y1cdw1ablpvd/75IEOH93vR0hbvxuqTu1m3/f6222745ee6892ea07bc18727a5a5ae7/T016S22KZ96-U02LU3SKC2D-e1e755770536-512.png",{"json":238,"links":718},{"data":239,"content":240,"nodeType":717},{},[241,252,260,286,294,316,323,330,337,345,352,359,366,373,380,387,394,400,407,414,421,428,449,455,462,468,475,481,488,495,502,547,554,574,581,671,691,698,705,711],{"data":242,"content":243,"nodeType":251},{},[244],{"data":245,"marks":246,"value":249,"nodeType":250},{},[247],{"type":248},"italic","You get a call from your CFO: “Jenkins! ACME just called to find out why we haven’t paid invoices for the last 3 months? Didn’t you make payment last week?”","text","paragraph",{"data":253,"content":254,"nodeType":251},{},[255],{"data":256,"marks":257,"value":259,"nodeType":250},{},[258],{"type":248},"You think back a bit. “Yip! I received another invoice a few days ago and made payment yesterday. I also paid the contractor doing renovations on your house. By the way, congrats on the new kitchen.”",{"data":261,"content":262,"nodeType":251},{},[263,267,282],{"data":264,"marks":265,"value":266,"nodeType":250},{},[],"Many companies have had similar incidents occur over the last couple of years - it’s a classic ",{"data":268,"content":274,"nodeType":281},{"target":269},{"sys":270},{"id":271,"type":272,"linkType":273},"pj2eLZXa4PyrY1DD4NCHt","Link","Entry",[275],{"data":276,"marks":277,"value":280,"nodeType":250},{},[278],{"type":279},"underline","Business Email Compromise","entry-hyperlink",{"data":283,"marks":284,"value":285,"nodeType":250},{},[]," (BEC) scenario. An attacker managed to gain access to Jenkins in accounting’s email and intercepted email from legitimate creditors, replacing their banking details with the attacker's own, and even forging invoices from non-existent suppliers. Forged emails are then sent from the CEO or CFO to approve the payments.",{"data":287,"content":288,"nodeType":251},{},[289],{"data":290,"marks":291,"value":293,"nodeType":250},{},[292],{"type":248},"But how did they manage to gain access to the account? Our security team enforced multi-factor authentication (MFA) a few weeks ago. We’re supposed to be secure!?",{"data":295,"content":296,"nodeType":251},{},[297,301,312],{"data":298,"marks":299,"value":300,"nodeType":250},{},[],"As detailed in our ",{"data":302,"content":306,"nodeType":281},{"target":303},{"sys":304},{"id":305,"type":272,"linkType":273},"1bV8YTSQHvveCTnRc4H8su",[307],{"data":308,"marks":309,"value":311,"nodeType":250},{},[310],{"type":279},"blog post about consent phishing",{"data":313,"marks":314,"value":315,"nodeType":250},{},[],", this attack method will bypass MFA, since the paired malicious third-party integration app (sometimes called OAuth) generates an authentication token. MFA checks are only applied when logging in with your username and password, so in this case, the attacker was able to get a valid access token into Jenkins’ account. ",{"data":317,"content":318,"nodeType":251},{},[319],{"data":320,"marks":321,"value":322,"nodeType":250},{},[],"While this isn’t necessarily the same level of access provided with a username/password combo, it might be, based on the scopes Jenkins granted the third-party integration app access to when they clicked ‘Accept’. ",{"data":324,"content":328,"nodeType":329},{"target":325},{"sys":326},{"id":327,"type":272,"linkType":273},"5BIHqq49jJOHsEHLgc8Tb9",[],"embedded-entry-block",{"data":331,"content":332,"nodeType":251},{},[333],{"data":334,"marks":335,"value":336,"nodeType":250},{},[],"The list of third-party integration scopes can include anything from relatively benign things like retrieving your name, surname, and email address, to more dangerous or excessive permissions such as full access to your mailbox, the ability to configure mail rules to forward or delete email, and full access to your OneDrive or Sharepoint files. Worse case scenario: if you belong to groups with password reset capabilities, the attacker may be able to perform full account takeovers.",{"data":338,"content":339,"nodeType":344},{},[340],{"data":341,"marks":342,"value":343,"nodeType":250},{},[],"How do you detect and respond to such incidents?","heading-2",{"data":346,"content":347,"nodeType":251},{},[348],{"data":349,"marks":350,"value":351,"nodeType":250},{},[],"The main issue is detection. In my experience as an incident responder working with Fortune 500 companies at MWR Infosecurity, I found that BEC attacks are usually detected when associated parties start asking questions about non-payment (or unrecognized payments), which can take weeks or months from the day of compromise. By this point your cloud provider’s logs are likely to have rolled over and you’re unlikely to find much useful information to populate your incident timeline.",{"data":353,"content":354,"nodeType":251},{},[355],{"data":356,"marks":357,"value":358,"nodeType":250},{},[],"Shameless plug alert: Push’s ChatOps functionality can greatly assist here as it detects such malicious rules when created, and sends a message to the owner of the account (Jenkins) asking if they created the rule. Sometimes a user will have a legitimate use for creating mail rules to forward messages to another account, and this allows them to acknowledge the rule and mark it as safe. In case they didn’t create it, they can flag it as such and this will cause an alert to be sent to their security team. This is practically instant detection and invaluable when preventing fraudulent payments. And getting input from the account owner cuts way down on alert fatigue for your team.",{"data":360,"content":361,"nodeType":344},{},[362],{"data":363,"marks":364,"value":365,"nodeType":250},{},[],"\nMitigate the attack \n",{"data":367,"content":368,"nodeType":251},{},[369],{"data":370,"marks":371,"value":372,"nodeType":250},{},[],"Once you’ve detected the incident, your next step is to remediate. Typically, this would require someone on the  security team to find the offending rule in your cloud provider’s control panel to disable it, which can take some time, depending on the team’s availability and other factors. ",{"data":374,"content":375,"nodeType":251},{},[376],{"data":377,"marks":378,"value":379,"nodeType":250},{},[],"Detecting the creation of malicious mail rules would require you to configure policies and alerts in your cloud provider’s control panel, and requires someone from the security team to monitor for notifications. If your IT person is also responsible for security in your organization, it’s unlikely that they would spend an appropriate amount of time looking at alerts and, in many cases, would need to follow up with employees to confirm if they had indeed created the rules. If you’re a larger organization, your dedicated security person will likely have higher priority tasks, too.",{"data":381,"content":382,"nodeType":251},{},[383],{"data":384,"marks":385,"value":386,"nodeType":250},{},[],"Discovering a breach is usually related to someone noticing unrecognized payments, vendors querying a lack of payments, or phishing emails being sent to fellow employees or contacts outside of your organization. If an attacker is careful to avoid causing too much interruption, then it’s likely that you won’t discover the breach until all the damage has been done. Usually by this point, performing an investigation will reveal very little due to important investigation artifacts disappearing due to logs rolling over.",{"data":388,"content":389,"nodeType":251},{},[390],{"data":391,"marks":392,"value":393,"nodeType":250},{},[],"If you’re using Push, we would automatically detect the mail rule, talk to the employee whose email the mail rule was created within, and if they didn’t set the mail rule up themselves, we would assume it was created by an attacker and alert your security team. Push’s ChatOps will disable the offending rule and mark it as suspicious.",{"data":395,"content":399,"nodeType":329},{"target":396},{"sys":397},{"id":398,"type":272,"linkType":273},"6rV4EiwTgmBsmYEaUvv55b",[],{"data":401,"content":402,"nodeType":251},{},[403],{"data":404,"marks":405,"value":406,"nodeType":250},{},[],"If this were a typical credential compromise scenario, the account’s password would be reset and everyone would go about their lives. However, since no credentials were compromised in our example, you’d go onto the next step to…",{"data":408,"content":409,"nodeType":344},{},[410],{"data":411,"marks":412,"value":413,"nodeType":250},{},[],"Remove the app’s permissions and revoke the tokens",{"data":415,"content":416,"nodeType":251},{},[417],{"data":418,"marks":419,"value":420,"nodeType":250},{},[],"As I mentioned earlier, third-party integration apps generate tokens, which can be valid for an hour to sometimes 24 hours or more, depending on the integrating app, how it is being used, and if it makes use of refresh tokens.",{"data":422,"content":423,"nodeType":251},{},[424],{"data":425,"marks":426,"value":427,"nodeType":250},{},[],"Invalidating third-party integration access permissions requires accessing your cloud provider’s control panel. In this example, you need to revoke access for a malicious app in a Microsoft 365 tenant. Microsoft’s guidance on this is very useful, but unfortunately not as simple as just pressing a button.",{"data":429,"content":430,"nodeType":251},{},[431,435,445],{"data":432,"marks":433,"value":434,"nodeType":250},{},[],"To view Microsoft’s recommendations for dealing with a malicious app, you’d need to navigate to the ",{"data":436,"content":438,"nodeType":444},{"uri":437},"https://portal.azure.com/#view/Microsoft_AAD_IAM/StartboardApplicationsMenuBlade/~/AppAppsPreview/menuId~/null",[439],{"data":440,"marks":441,"value":443,"nodeType":250},{},[442],{"type":279},"Enterprise applications","hyperlink",{"data":446,"marks":447,"value":448,"nodeType":250},{},[]," section in Azure, and locate the app by searching for its name or Application ID, which can be found in the Push app’s OAuth integrations page. In the app menu, click on ‘Permissions,’ then ‘Review permissions.’ ",{"data":450,"content":454,"nodeType":329},{"target":451},{"sys":452},{"id":453,"type":272,"linkType":273},"5Z6T2anRIJ1he2phTbcFot",[],{"data":456,"content":457,"nodeType":251},{},[458],{"data":459,"marks":460,"value":461,"nodeType":250},{},[],"On the slide-out menu, select “This application is malicious and I’m compromised.”",{"data":463,"content":467,"nodeType":329},{"target":464},{"sys":465},{"id":466,"type":272,"linkType":273},"2lGnKdKTjXAVYBiOtYrbEl",[],{"data":469,"content":470,"nodeType":251},{},[471],{"data":472,"marks":473,"value":474,"nodeType":250},{},[],"This will provide you with pre-generated PowerShell scripts to 1) Remove all users assigned to the application, 2) Revoke all permissions granted to the application, and 3) Revoke refresh tokens for all users.",{"data":476,"content":480,"nodeType":329},{"target":477},{"sys":478},{"id":479,"type":272,"linkType":273},"3qdGQ12PdZFLEyIpmMkwPi",[],{"data":482,"content":483,"nodeType":344},{},[484],{"data":485,"marks":486,"value":487,"nodeType":250},{},[],"How to prevent similar attacks",{"data":489,"content":490,"nodeType":251},{},[491],{"data":492,"marks":493,"value":494,"nodeType":250},{},[],"A very important step following a compromise is to review what happened, how it happened, and what could be done to prevent the incident from occurring again. The interesting part about this incident is that it wasn’t due to a weak password, or even the lack of MFA that led to compromise. It came down to social engineering: instructing an employee to click a link by an account masquerading as their CFO.",{"data":496,"content":497,"nodeType":251},{},[498],{"data":499,"marks":500,"value":501,"nodeType":250},{},[],"For the purposes of this hypothetical incident, we’ll establish that the following occurred:",{"data":503,"content":504,"nodeType":546},{},[505,516,526,536],{"data":506,"content":507,"nodeType":515},{},[508],{"data":509,"content":510,"nodeType":251},{},[511],{"data":512,"marks":513,"value":514,"nodeType":250},{},[],"Andrew Jenkins was targeted in a phishing attack","list-item",{"data":517,"content":518,"nodeType":515},{},[519],{"data":520,"content":521,"nodeType":251},{},[522],{"data":523,"marks":524,"value":525,"nodeType":250},{},[],"Andrew authenticated via Microsoft 365, which is a legitimate and expected authentication mechanism and occurs almost daily",{"data":527,"content":528,"nodeType":515},{},[529],{"data":530,"content":531,"nodeType":251},{},[532],{"data":533,"marks":534,"value":535,"nodeType":250},{},[],"No attachments were downloaded, thus in this isolated incident there was no code execution on Andrew’s host, meaning that Anti-Virus or Endpoint Detection & Response (EDR) would not have prevented it",{"data":537,"content":538,"nodeType":515},{},[539],{"data":540,"content":541,"nodeType":251},{},[542],{"data":543,"marks":544,"value":545,"nodeType":250},{},[],"The attacker gained full access to Andrew’s mailbox","unordered-list",{"data":548,"content":549,"nodeType":251},{},[550],{"data":551,"marks":552,"value":553,"nodeType":250},{},[],"The malicious app was disabled by Microsoft after some time, so a full investigation into its capabilities was not possible. We don’t know whether another phishing page was presented after the integration took place, thus to be on the safe side we need to assume this happened and led to credential compromise.",{"data":555,"content":556,"nodeType":251},{},[557,561,570],{"data":558,"marks":559,"value":560,"nodeType":250},{},[],"The app was unverified, which has historically been true in most of these scenarios. Publishers need to associate a Microsoft Partner Network (MPN) ID with the app, which follows a ",{"data":562,"content":564,"nodeType":444},{"uri":563},"https://docs.microsoft.com/en-us/partner-center/verification-responses",[565],{"data":566,"marks":567,"value":569,"nodeType":250},{},[568],{"type":279},"verification process",{"data":571,"marks":572,"value":573,"nodeType":250},{},[],", in order to have it appear as a verified app. This Microsoft 365 tenant was configured to allow unverified integrations due to an oversight following an app migration project.",{"data":575,"content":576,"nodeType":251},{},[577],{"data":578,"marks":579,"value":580,"nodeType":250},{},[],"This leads us to the following to help prevent similar attacks from occurring in future, and to make sure there is no opportunity for the attacker to leverage any existing foothold:",{"data":582,"content":583,"nodeType":546},{},[584,594,604,614,635,651,661],{"data":585,"content":586,"nodeType":515},{},[587],{"data":588,"content":589,"nodeType":251},{},[590],{"data":591,"marks":592,"value":593,"nodeType":250},{},[],"Disable the integration and remove the malicious app’s permissions",{"data":595,"content":596,"nodeType":515},{},[597],{"data":598,"content":599,"nodeType":251},{},[600],{"data":601,"marks":602,"value":603,"nodeType":250},{},[],"Reset Andrew Jenkins’ credentials",{"data":605,"content":606,"nodeType":515},{},[607],{"data":608,"content":609,"nodeType":251},{},[610],{"data":611,"marks":612,"value":613,"nodeType":250},{},[],"Be aware of and review newly created mail rules",{"data":615,"content":616,"nodeType":515},{},[617],{"data":618,"content":619,"nodeType":251},{},[620,623,632],{"data":621,"marks":622,"value":29,"nodeType":250},{},[],{"data":624,"content":626,"nodeType":444},{"uri":625},"https://docs.microsoft.com/en-us/azure/active-directory/manage-apps/configure-user-consent?tabs=azure-portal",[627],{"data":628,"marks":629,"value":631,"nodeType":250},{},[630],{"type":279},"Confirm that the Microsoft 365 tenant is set to disallow integrations from unverified apps",{"data":633,"marks":634,"value":29,"nodeType":250},{},[],{"data":636,"content":637,"nodeType":515},{},[638],{"data":639,"content":640,"nodeType":546},{},[641],{"data":642,"content":643,"nodeType":515},{},[644],{"data":645,"content":646,"nodeType":251},{},[647],{"data":648,"marks":649,"value":650,"nodeType":250},{},[],"Note: as of November 9th, 2020, integrations with unverified apps are disabled by default.",{"data":652,"content":653,"nodeType":515},{},[654],{"data":655,"content":656,"nodeType":251},{},[657],{"data":658,"marks":659,"value":660,"nodeType":250},{},[],"Communicate with employees and other affected parties to be weary of these types of attacks",{"data":662,"content":663,"nodeType":515},{},[664],{"data":665,"content":666,"nodeType":251},{},[667],{"data":668,"marks":669,"value":670,"nodeType":250},{},[],"Perform regular audits against your Microsoft 365 tenants to highlight any discrepancies and integrations with unusual or unnecessary permissions.",{"data":672,"content":673,"nodeType":251},{},[674,678,687],{"data":675,"marks":676,"value":677,"nodeType":250},{},[],"Microsoft implementing safe defaults towards limiting integrations from unverified publishers was a step in the right direction. However, there have been ",{"data":679,"content":681,"nodeType":444},{"uri":680},"https://www.proofpoint.com/us/blog/cloud-security/oivavoii-active-malicious-hybrid-cloud-threats-campaign",[682],{"data":683,"marks":684,"value":686,"nodeType":250},{},[685],{"type":279},"cases",{"data":688,"marks":689,"value":690,"nodeType":250},{},[]," where attackers utilized compromised publishers to perform similar attacks. ",{"data":692,"content":693,"nodeType":344},{},[694],{"data":695,"marks":696,"value":697,"nodeType":250},{},[],"Conclusion",{"data":699,"content":700,"nodeType":251},{},[701],{"data":702,"marks":703,"value":704,"nodeType":250},{},[],"While the process isn’t exactly straightforward, catching early indicators like malicious mail rules helps you prevent an attacker from launching additional attacks like phishing campaigns as they try to gain access to sensitive business data. Removing the mail rule is just the start of the process, you really need to revoke permissions and take the other steps we covered in this post to stop an attack from going any further. We’ll publish some more content on SaaS incident response on our blog, so subscribe to get our guidance straight into your inbox.",{"data":706,"content":710,"nodeType":329},{"target":707},{"sys":708},{"id":709,"type":272,"linkType":273},"6oHRbGLus4bstsAc7E0zBD",[],{"data":712,"content":713,"nodeType":251},{},[714],{"data":715,"marks":716,"value":29,"nodeType":250},{},[],"document",{"entries":719},{"inline":720,"hyperlink":721,"block":731},[],[722,727],{"sys":723,"__typename":724,"title":725,"slug":726},{"id":271},"BlogPosts","Case study: Business Email Compromise (BEC) attack nearly cost us millions","case-study-business-email-compromise-bec-attack-nearly-cost-us-millions",{"sys":728,"__typename":724,"title":729,"slug":730},{"id":305},"Consent phishing: the emerging phishing technique that can bypass 2FA","consent-phishing-the-emerging-phishing-technique-that-can-bypass-2fa",[732,740,747,754,761,768],{"sys":733,"__typename":734,"title":735,"caption":62,"layoutMode":62,"file":736},{"id":327},"Image","Consent phishing example",{"url":737,"width":738,"height":739},"https://images.ctfassets.net/y1cdw1ablpvd/4mE1i0PWq5Tns9qbcvglZh/dcd08098c29b9d36e3cd501a83aaa9c9/image4.jpg",500,765,{"sys":741,"__typename":734,"title":742,"caption":62,"layoutMode":62,"file":743},{"id":398},"Mail rules chatops",{"url":744,"width":745,"height":746},"https://images.ctfassets.net/y1cdw1ablpvd/10Yy4SzIegYrYC9fGbVFO8/658e0e608c7f573ad648df4f9cd3a0a8/image2.png",589,169,{"sys":748,"__typename":734,"title":749,"caption":62,"layoutMode":62,"file":750},{"id":453},"Malicious app permissions",{"url":751,"width":752,"height":753},"https://images.ctfassets.net/y1cdw1ablpvd/KPK1ZRkwp1QCzkVpwoeUC/c064b2a4e89264a3bed9c47f45705625/image3.png",787,668,{"sys":755,"__typename":734,"title":756,"caption":62,"layoutMode":62,"file":757},{"id":466},"Push malicious app ",{"url":758,"width":759,"height":760},"https://images.ctfassets.net/y1cdw1ablpvd/5dOX0KB5yAME0gfERMZIij/e4d5e687df890dccf2d13b98904f420e/image5.png",690,419,{"sys":762,"__typename":734,"title":763,"caption":62,"layoutMode":62,"file":764},{"id":479},"Powershell script IR blog",{"url":765,"width":766,"height":767},"https://images.ctfassets.net/y1cdw1ablpvd/4xTQrOxKSTGKpNASlYwiOz/5f121b1f18507492ee0ba671712f3832/image1.png",834,718,{"sys":769,"__typename":770,"content":771,"title":782,"buttonText":783,"buttonUrl":784,"signupRedirectUrl":62},{"id":709},"ActionBlockComponent",{"json":772},{"nodeType":717,"data":773,"content":774},{},[775],{"nodeType":251,"content":776,"data":781},[777],{"nodeType":250,"value":778,"marks":779,"data":780},"Find out if you have any malicious apps that employees have accidentally installed due to consent phishing. Note: you must be logged in to access.",[],{},{},"Detect risky third-party apps and malicious mail rules ","Check now","/app/feature/secure-oauth-permissions-and-applications/","json",{"items":787},[],{},"How to kick off an investigation for a compromised account","2022-09-20T00:00:00.000Z",{"items":792},[793,1001],{"__typename":724,"sys":794,"content":795,"title":729,"synopsis":981,"hashTags":62,"publishedDate":982,"slug":730,"tagsCollection":983,"authorsCollection":993},{"id":305},{"json":796},{"nodeType":717,"data":797,"content":798},{},[799,806,813,819,836,842,849,856,887,893,912,931,950],{"nodeType":251,"data":800,"content":801},{},[802],{"nodeType":250,"value":803,"marks":804,"data":805},"With more platforms adding support for Multi-factor Authentication (MFA) and users increasingly adopting it to secure their accounts, attackers are adapting and moving to new methods of compromising user accounts. In this post we’ll take a look at consent phishing and how it is being used to bypass MFA and also skirt key attributes of phishing that are taught in traditional user awareness campaigns, such as links to untrusted domains.",[],{},{"nodeType":251,"data":807,"content":808},{},[809],{"nodeType":250,"value":810,"marks":811,"data":812},"Imagine yourself sitting down at your desk first thing on a Monday morning, cup of coffee steaming next to your keyboard as you click through your backlog of emails. You open the below email and you see that Karl has shared a financial report with you. ",[],{},{"nodeType":329,"data":814,"content":818},{"target":815},{"sys":816},{"id":817,"type":272,"linkType":273},"7zysXleQdpE6isqi9OU56l",[],{"nodeType":251,"data":820,"content":821},{},[822,826,832],{"nodeType":250,"value":823,"marks":824,"data":825},"Maybe you’ve been waiting for the latest financials or you suspect this was sent erroneously but you’re curious and want to take a peek. When you click the link you are presented with a prompt that with your Monday brain looks just like the “Yes give me access” prompt you’ve clicked through a thousand times. I mean, it's a ",[],{},{"nodeType":250,"value":827,"marks":828,"data":831},"microsoftonline.com",[829],{"type":830},"bold",{},{"nodeType":250,"value":833,"marks":834,"data":835}," domain, it's https and there’s a green tick in the corner so everything looks fine. ",[],{},{"nodeType":329,"data":837,"content":841},{"target":838},{"sys":839},{"id":840,"type":272,"linkType":273},"6nPueTKEjLphqlytbQ0gcx",[],{"nodeType":251,"data":843,"content":844},{},[845],{"nodeType":250,"value":846,"marks":847,"data":848},"If you’d looked closely you may have noticed that this was in fact asking you to approve access rather than granting you access. But with your muscle memory in full control you click “Accept” before even glancing at the screen. You wait for the spreadsheet to open but are presented with a generic “File does not exist” error page. Oh well, apparently Karl realised his mistake and deleted the file or revoked your access. Onto the next email.",[],{},{"nodeType":251,"data":850,"content":851},{},[852],{"nodeType":250,"value":853,"marks":854,"data":855},"And just like that you’ve been consent phished. You’ve just granted the attackers permanent access to your account, which they retain even if you change your password or have MFA enabled. Chances are the attacker’s tools will immediately start downloading every piece of data you just granted them access to, which they can then explore at their leisure. ",[],{},{"nodeType":251,"data":857,"content":858},{},[859,863,871,875,883],{"nodeType":250,"value":860,"marks":861,"data":862},"To spot this you need to audit the apps you’ve approved, something you are doing regularly, right? Seriously though, this isn’t something many people check. These integrations are designed to be as seamless as possible and not to get in your way. But if this has piqued your interest you can check what access you have personally granted on ",[],{},{"nodeType":444,"data":864,"content":866},{"uri":865},"https://myaccount.google.com/permissions",[867],{"nodeType":250,"value":868,"marks":869,"data":870},"Google Workspace",[],{},{"nodeType":250,"value":872,"marks":873,"data":874}," and ",[],{},{"nodeType":444,"data":876,"content":878},{"uri":877},"https://myapps.microsoft.com/",[879],{"nodeType":250,"value":880,"marks":881,"data":882},"Microsoft 365",[],{},{"nodeType":250,"value":884,"marks":885,"data":886},".",[],{},{"nodeType":329,"data":888,"content":892},{"target":889},{"sys":890},{"id":891,"type":272,"linkType":273},"BPIX02LWblUNnkQw1TFWD",[],{"nodeType":251,"data":894,"content":895},{},[896,900,908],{"nodeType":250,"value":897,"marks":898,"data":899},"If you’d been paying attention when you clicked “Accept” you might have noticed that you were granting some pretty serious permissions here. These permissions allow the attackers to read and write any files you have access to - they could download all these files and then delete them. The attackers also got permission to send emails as you. They could send emails to your colleagues from you and phish them too, this isn’t impersonation where the email just “looks” like it came from you, the email DID come from you. Lastly the attackers asked for permission to manipulate your Outlook settings, with this they could set up a ",[],{},{"nodeType":444,"data":901,"content":903},{"uri":902},"/features/detect-malicious-mail-rules/",[904],{"nodeType":250,"value":905,"marks":906,"data":907},"mail forwarding rule",[],{},{"nodeType":250,"value":909,"marks":910,"data":911}," so that they get copies of all your emails forwarded to them directly without even having to log in. And all of this happens until you delete the underlying OAuth app.",[],{},{"nodeType":251,"data":913,"content":914},{},[915,919,927],{"nodeType":250,"value":916,"marks":917,"data":918},"In a ",[],{},{"nodeType":444,"data":920,"content":922},{"uri":921},"https://www.microsoft.com/security/blog/2020/07/08/protecting-remote-workforce-application-attacks-consent-phishing/",[923],{"nodeType":250,"value":924,"marks":925,"data":926},"blog post",[],{},{"nodeType":250,"value":928,"marks":929,"data":930}," Microsoft warns that these attacks are on the rise. One notable example of this comes from the SANS Institute. They reported in August of 2020 that they had fallen victim to one of these attacks. As part of the investigation they produced a report with details on how the attackers managed to convince an employee to install a malicious Microsoft 365 add-in to gain access. ",[],{},{"nodeType":251,"data":932,"content":933},{},[934,938,946],{"nodeType":250,"value":935,"marks":936,"data":937},"So what can you do about this threat today? The only fool proof method of preventing this kind of attack is to prevent users from granting access to third party apps. This is terrible for users though, and you’ll be missing out on all the productivity benefits these apps can bring. A more balanced approach is to let users find and request apps, but have administrators approve the apps. More and more platforms (including Microsoft 365 and Slack) are offering built-in “admin consent” workflows to make getting a second pair of eyes on new apps even easier. You can also make it even easier for users  by pre-approving widely used apps from trusted publishers and users won’t even notice there is new protection in place 99% of the time. We are also actively working on this problem and if you would like to join our ",[],{},{"nodeType":444,"data":939,"content":941},{"uri":940},"/features/secure-oauth-permissions-and-applications/",[942],{"nodeType":250,"value":943,"marks":944,"data":945},"early access program",[],{},{"nodeType":250,"value":947,"marks":948,"data":949}," please get in touch.",[],{},{"nodeType":251,"data":951,"content":952},{},[953,957,965,969,977],{"nodeType":250,"value":954,"marks":955,"data":956},"Consent phishing is still an emerging technique and we believe that it has not reached peak usage by attackers yet. We are actively researching this attack technique as it continues to evolve. Follow us on Twitter ",[],{},{"nodeType":444,"data":958,"content":960},{"uri":959},"https://twitter.com/PushSecurity",[961],{"nodeType":250,"value":962,"marks":963,"data":964},"@pushsecurity",[],{},{"nodeType":250,"value":966,"marks":967,"data":968},", ",[],{},{"nodeType":444,"data":970,"content":972},{"uri":971},"https://www.linkedin.com/company/push-security",[973],{"nodeType":250,"value":974,"marks":975,"data":976},"LinkedIn",[],{},{"nodeType":250,"value":978,"marks":979,"data":980}," or subscribe to our mailing list below to get the latest updates and tips for managing this for your users.",[],{},"Consent phishing is an emerging technique attackers are using to compromise user accounts, even if they have Multi-factor Authentication (MFA or 2FA) enabled.","2021-07-06T00:00:00.000+01:00",{"items":984},[985,989],{"sys":986,"name":988},{"id":987},"6A5RXS31ZQx3PwryGb1IMy","Browser-based attacks",{"sys":990,"name":992},{"id":991},"4ksQNCFeBf8H4QIORqpRLw","Detection & response",{"items":994},[995],{"fullName":996,"firstName":997,"jobTitle":998,"profilePicture":999},"Alex Triaca","Alex","Chief Architect",{"url":1000},"https://images.ctfassets.net/y1cdw1ablpvd/LmC3LyTH5V9NthbqKuqA2/8291887e41c15613bf98f6fd55773817/117-0-2.jpg",{"__typename":724,"sys":1002,"content":1004,"title":1325,"synopsis":1326,"hashTags":1327,"publishedDate":1333,"slug":1334,"tagsCollection":1335,"authorsCollection":1341},{"id":1003},"roVnr9Z2sHDPGtemZUE7u",{"json":1005},{"data":1006,"content":1007,"nodeType":717},{},[1008,1027,1034,1064,1080,1087,1094,1101,1109,1116,1136,1143,1163,1169,1177,1184,1204,1212,1231,1239,1246,1299,1306,1313,1319],{"data":1009,"content":1010,"nodeType":251},{},[1011,1015,1023],{"data":1012,"marks":1013,"value":1014,"nodeType":250},{},[],"Mail rules can be abused by attackers to get stealthy, persistent access to a mailbox, leak data and facilitate high-impact Business Email Compromise (",{"data":1016,"content":1018,"nodeType":444},{"uri":1017},"/blog/email-security-how-hackers-use-mail-rules-to-access-your-inbox/",[1019],{"data":1020,"marks":1021,"value":1022,"nodeType":250},{},[],"read more here",{"data":1024,"marks":1025,"value":1026,"nodeType":250},{},[],"). So, lots of organisations decide to ban external auto-forwarding of email altogether. The question is, is this a good move?",{"data":1028,"content":1029,"nodeType":344},{},[1030],{"data":1031,"marks":1032,"value":1033,"nodeType":250},{},[],"This is damage limitation, not prevention",{"data":1035,"content":1036,"nodeType":251},{},[1037,1041,1046,1050,1060],{"data":1038,"marks":1039,"value":1040,"nodeType":250},{},[],"It’s important to recognise that adding a malicious mail rule to a user’s mailbox is a ",{"data":1042,"marks":1043,"value":1045,"nodeType":250},{},[1044],{"type":830},"post-compromise activity",{"data":1047,"marks":1048,"value":1049,"nodeType":250},{},[],". That is, an attacker has already compromised the victim somehow - compromised their password, deployed malware on their machine, performed consent phishing etc. - they already have access to their mailbox. At this point, you should assume all data in the mailbox is compromised anyway. (See here for “",{"data":1051,"content":1055,"nodeType":281},{"target":1052},{"sys":1053},{"id":1054,"type":272,"linkType":273},"e4805bba-2531-4250-bdcc-ab996dd33519",[1056],{"data":1057,"marks":1058,"value":1059,"nodeType":250},{},[],"what to do if I find a malicious mail rule?",{"data":1061,"marks":1062,"value":1063,"nodeType":250},{},[],"”)",{"data":1065,"content":1066,"nodeType":251},{},[1067,1071,1076],{"data":1068,"marks":1069,"value":1070,"nodeType":250},{},[],"Preventing external auto-forwarding rules therefore reduces",{"data":1072,"marks":1073,"value":1075,"nodeType":250},{},[1074],{"type":830}," further potential impact",{"data":1077,"marks":1078,"value":1079,"nodeType":250},{},[]," to a compromised account - worth doing if no one is using the feature, but what if your users are?",{"data":1081,"content":1082,"nodeType":344},{},[1083],{"data":1084,"marks":1085,"value":1086,"nodeType":250},{},[],"Security vs. user experience",{"data":1088,"content":1089,"nodeType":251},{},[1090],{"data":1091,"marks":1092,"value":1093,"nodeType":250},{},[],"Good security should enable a business and its users to work securely rather than constrain it. Controls that restrict users’ productivity or are seen as a nuisance will be bypassed and although you might prevent a potential attack type, you’ll ultimately cause less secure behaviour from your users.",{"data":1095,"content":1096,"nodeType":251},{},[1097],{"data":1098,"marks":1099,"value":1100,"nodeType":250},{},[],"With that in mind, if external auto-forwarding of email is something your users need - and there are plenty of legitimate scenarios where this may be the case - you should be considering how to manage the risk, rather than eliminate it. The good news is this is totally doable. Equally, if none, or most of your users don’t need this feature, you should of course disable it to reduce your overall risk.",{"data":1102,"content":1103,"nodeType":251},{},[1104],{"data":1105,"marks":1106,"value":1108,"nodeType":250},{},[1107],{"type":830},"Managing the risk on Exchange Online for Microsoft 365 through detection alone",{"data":1110,"content":1111,"nodeType":251},{},[1112],{"data":1113,"marks":1114,"value":1115,"nodeType":250},{},[],"Managing the risk of external auto-forwarding email rules means making sure you’re alerted when one is created. ",{"data":1117,"content":1118,"nodeType":251},{},[1119,1123,1132],{"data":1120,"marks":1121,"value":1122,"nodeType":250},{},[],"If you’re using Exchange Online for Microsoft 365, ",{"data":1124,"content":1126,"nodeType":444},{"uri":1125},"https://protection.office.com/alertpolicies",[1127],{"data":1128,"marks":1129,"value":1131,"nodeType":250},{},[1130],{"type":279},"an informational alert policy",{"data":1133,"marks":1134,"value":1135,"nodeType":250},{},[]," - “Creation of forwarding/redirect rule” - can be enabled so alerts of this type of suspicious rules will be sent to tenant admins when they are created in future. ",{"data":1137,"content":1138,"nodeType":251},{},[1139],{"data":1140,"marks":1141,"value":1142,"nodeType":250},{},[],"/prod",{"data":1144,"content":1145,"nodeType":251},{},[1146,1150,1159],{"data":1147,"marks":1148,"value":1149,"nodeType":250},{},[],"The downside of this approach is it isn’t possible to look retrospectively (",{"data":1151,"content":1153,"nodeType":444},{"uri":1152},"https://gcits.com/knowledge-base/find-inbox-rules-forward-mail-externally-office-365-powershell/",[1154],{"data":1155,"marks":1156,"value":1158,"nodeType":250},{},[1157],{"type":279},"without using PowerShell",{"data":1160,"marks":1161,"value":1162,"nodeType":250},{},[],") so alerts will only fire on future creation of forwarding rules. Additionally, alerts also fire for internal forwarding rules which can generate a lot of noise when looking specifically for malicious rules. ",{"data":1164,"content":1168,"nodeType":329},{"target":1165},{"sys":1166},{"id":1167,"type":272,"linkType":273},"2aafjsTsqy7ljL5hh8c3MO",[],{"data":1170,"content":1171,"nodeType":251},{},[1172],{"data":1173,"marks":1174,"value":1176,"nodeType":250},{},[1175],{"type":830},"Managing the risk on Exchange Online for Microsoft 365  through detection & prevention",{"data":1178,"content":1179,"nodeType":251},{},[1180],{"data":1181,"marks":1182,"value":1183,"nodeType":250},{},[],"In addition to being alerted when rules are created, you can take steps to either disallow external auto-forwarding rules altogether, or prevent them taking effect. You might think disallowing their creation is better but if you can permit creation but stop them from taking effect, you keep a high-fidelity detection of account compromise, without adding any additional risk.",{"data":1185,"content":1186,"nodeType":251},{},[1187,1191,1200],{"data":1188,"marks":1189,"value":1190,"nodeType":250},{},[],"In Exchange Online for Microsoft 365, you can achieve this with ",{"data":1192,"content":1194,"nodeType":444},{"uri":1193},"https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/external-email-forwarding?view=o365-worldwide",[1195],{"data":1196,"marks":1197,"value":1199,"nodeType":250},{},[1198],{"type":279},"outbound spam filter policies",{"data":1201,"marks":1202,"value":1203,"nodeType":250},{},[]," to automatically stop any emails auto-forwarded out of your organisation. If an attacker creates a malicious auto-forwarding rule, any forwarded mail will be blocked by the spam filter; if you have your alerts set up correctly, you’ll still receive an alert about the new malicious rule.",{"data":1205,"content":1206,"nodeType":251},{},[1207],{"data":1208,"marks":1209,"value":1211,"nodeType":250},{},[1210],{"type":830},"Managing the risk on Gmail for Google Workspace",{"data":1213,"content":1214,"nodeType":251},{},[1215,1219,1228],{"data":1216,"marks":1217,"value":1218,"nodeType":250},{},[],"Google Workspace only allows complete prevention, such that your users (and attackers) are not able to create forwarding settings. If you decide that is right for you, you can disable automatic forwarding entirely by ",{"data":1220,"content":1222,"nodeType":444},{"uri":1221},"https://support.google.com/a/answer/2491924?hl=en",[1223],{"data":1224,"marks":1225,"value":1227,"nodeType":250},{},[1226],{"type":279},"following these instructions",{"data":1229,"marks":1230,"value":884,"nodeType":250},{},[],{"data":1232,"content":1233,"nodeType":251},{},[1234],{"data":1235,"marks":1236,"value":1238,"nodeType":250},{},[1237],{"type":830},"Managing the risk using the Push platform",{"data":1240,"content":1241,"nodeType":251},{},[1242],{"data":1243,"marks":1244,"value":1245,"nodeType":250},{},[],"Using the Push platform makes managing this risk a lot easier with less of your time:",{"data":1247,"content":1248,"nodeType":546},{},[1249,1259,1269,1279,1289],{"data":1250,"content":1251,"nodeType":515},{},[1252],{"data":1253,"content":1254,"nodeType":251},{},[1255],{"data":1256,"marks":1257,"value":1258,"nodeType":250},{},[],"Connect your platform with a few clicks and we’ll sweep your estate for any suspicious rules currently in place.",{"data":1260,"content":1261,"nodeType":515},{},[1262],{"data":1263,"content":1264,"nodeType":251},{},[1265],{"data":1266,"marks":1267,"value":1268,"nodeType":250},{},[],"Get alerts via email or ChatOps (Slack or Teams) when new rules are created. Triage and deal with them directly from the email or chat platform.",{"data":1270,"content":1271,"nodeType":515},{},[1272],{"data":1273,"content":1274,"nodeType":251},{},[1275],{"data":1276,"marks":1277,"value":1278,"nodeType":250},{},[],"Use our ChatOps features to ask users directly if they recognise a rule when you’re unsure. You can even automate this so user feedback is already collected by the time you come to triage.",{"data":1280,"content":1281,"nodeType":515},{},[1282],{"data":1283,"content":1284,"nodeType":251},{},[1285],{"data":1286,"marks":1287,"value":1288,"nodeType":250},{},[],"Disable rules directly from the platform for quick response.",{"data":1290,"content":1291,"nodeType":515},{},[1292],{"data":1293,"content":1294,"nodeType":251},{},[1295],{"data":1296,"marks":1297,"value":1298,"nodeType":250},{},[],"Follow our detailed and clear guides for how to respond comprehensively.",{"data":1300,"content":1301,"nodeType":251},{},[1302],{"data":1303,"marks":1304,"value":697,"nodeType":250},{},[1305],{"type":830},{"data":1307,"content":1308,"nodeType":251},{},[1309],{"data":1310,"marks":1311,"value":1312,"nodeType":250},{},[],"If your users don’t use external email auto-forwarding, it makes sense to prevent the feature to limit the impact of a malicious mail rule. However, if there are legitimate business reasons for keeping the feature active, this risk can be sufficiently managed through detection.",{"data":1314,"content":1318,"nodeType":329},{"target":1315},{"sys":1316},{"id":1317,"type":272,"linkType":273},"2y0INxqAi594O7rCAVKhTI",[],{"data":1320,"content":1321,"nodeType":251},{},[1322],{"data":1323,"marks":1324,"value":29,"nodeType":250},{},[],"Should you disable external email auto-forwarding?","External email auto-forwarding is a feature but also a risk; learn whether you should disable it, and, if you can't, how to manage the risk through detection.",[1328,1329,1330,1331,1332],"businessemailcompromise","bec","mailrules","office365","googleworkspace","2021-06-03T00:00:00.000+01:00","should-you-disable-external-email-auto-forwarding",{"items":1336},[1337,1339],{"sys":1338,"name":988},{"id":987},{"sys":1340,"name":992},{"id":991},{"items":1342},[1343],{"fullName":1344,"firstName":1345,"jobTitle":1346,"profilePicture":1347},"Andy Waugh","Andy","VP Product",{"url":1348},"https://images.ctfassets.net/y1cdw1ablpvd/3Rf76rJn6S9inMb4dUnAIJ/0a787f8141d05b95300e2fe77c4493fa/DSC_6868.jpg","how-to-kick-off-an-incident-response-investigation-for-a-compromised-saas","blog/how-to-kick-off-an-incident-response-investigation-for-a-compromised-saas",{"json":1352},{"data":1353,"content":1354,"nodeType":717},{},[1355],{"data":1356,"content":1357,"nodeType":251},{},[1358],{"data":1359,"marks":1360,"value":1361,"nodeType":250},{},[],"Learn how to quickly detect and mitigate business email compromise (BEC).","We'll walk through how to quickly detect and mitigate business email compromise (BEC) and then prevent future attacks.",{"id":1364,"publishedAt":1365},"14NiRrBrLFVkR8h05RCD7F","2024-03-21T09:07:17.261Z",{"items":1367},[1368,1370],{"sys":1369,"name":992},{"id":991},{"sys":1371,"name":1373},{"id":1372},"3pjES4THCIfSAwhGdNwBcy","Browser security","TL_jHdPWERz9TCWnBO8PzIXnOixz9xJ_SZ7r7BFocXk",1784196732216]