In the previous parts of our blog ( part I and part II ), we have described the most important parts of the Sunburst backdoor... Cloud Security Sunburst Backdoor, Part III: DGA & Security Software Rony Moshkovich 2 min read Rony Moshkovich Short bio about author here Lorem ipsum dolor sit amet consectetur. Vitae donec tincidunt elementum quam laoreet duis sit enim. Duis mattis velit sit leo diam. Tags Share this article 12/22/20 Published In the previous parts of our blog ( part I and part II ), we have described the most important parts of the Sunburst backdoor functionality and its Domain Generation Algorithm (DGA). This time, let’s have a deeper look into the passive DNS requests reported by Open-Source Context and Zetalytics . The valid DNS requests generated by the malware fall into 2 groups: DNS requests that encode a local domain name DNS requests that encode data The first type of DNS requests allows splitting long domain names into separate requests. These requests are generated by the malware’s functions GetPreviousString() and GetCurrentString() . In general, the format of a DNS request that encodes a domain name may look like: USER_ID.NUM.COMPUTER_DOMAIN[.]appsync-api.us-west-2[.]avsvmcloud[.]com where: USER_ID is an 8-byte user ID that uniquely identifies a compromised host, encoded as a 15-character string NUM is a number of a domain name – either 0 or 1, encoded as a character COMPUTER_DOMAIN is an encoded local computer domain Let’s try decoding the following 3 DNS requests: olc62cocacn7u2q22v02eu.appsync-api.us-west-2.avsvmcloud.com r1qshoj05ji05ac6eoip02jovt6i2v0c.appsync-api.us-west-2.avsvmcloud.com lt5ai41qh5d53qoti3mkmc0.appsync-api.us-west-2.avsvmcloud.com String 1 Let’s start from the 1st string in the list: olc62cocacn7u2q22v02eu.appsync-api.us-west-2.avsvmcloud.com. In this string, the first 15-character string is an encoded USER_ID : “olc62cocacn7u2q” . Once it is base-64 decoded, as explained in the previous post, it becomes a 9-byte byte array: 86 7f 2f be f9 fb a3 ae c4 The first byte in this byte array is a XOR key: 0x86 . Once applied to the 8 bytes that follow it, we get the 8-byte user ID – let’s take a note and write it down, we will need it later: f9 a9 38 7f 7d 25 28 42 Next, let’s take the NUM part of the encoded domain: it’s a character “2” located at the position #15 (starting from 0) of the encrypted domain. In order to decode the NUM number, we have to take the first character of the encrypted domain, take the reminder of its division by 36 , and subtract the NUM ‘s position in the string “0123456789abcdefghijklmnopqrstuvwxyz” : num = domain[0] % 36 – “0123456789abcdefghijklmnopqrstuvwxyz”.IndexOf(domain.Substring(15, 1)); The result is 1 . That means the decrypted domain will be the 2nd part of a full domain name. The first part must have its NUM decoded as 0. The COMPUTER_DOMAIN part of the encrypted domain is “2v02eu” . Once decoded, using the previously explained method, the decoded computer domain name becomes “on.ca” . String 2 Let’s decode the second passive DNS request from our list: r1qshoj05ji05ac6eoip02jovt6i2v0c.appsync-api.us-west-2.avsvmcloud.com Just as before, the decoded 8-byte user ID becomes: f9 a9 38 7f 7d 25 28 42 The NUM part of the encoded domain, located at the position #15 (starting from 0), is a character “6” . Let’s decode it, by taking the first character ( “r” = 114 ), take the reminder of its division by 36 ( 114 % 36 = 6 ), and subtracting the position of the character “6” in the “0123456789abcdefghijklmnopqrstuvwxyz” , which is 6 . The result is 0 . That means the decrypted domain will be the 1st part of the full domain name. The COMPUTER_DOMAIN part of the encrypted domain is “eoip02jovt6i2v0c” . Once decoded, it becomes “city.kingston.” Next, we need to match 2 decrypted domains by the user ID, which is f9 a9 38 7f 7d 25 28 42 in both cases, and concatenate the first and the second parts of the domain. The result will be “city.kingston.on.ca” . String 3 Here comes the most interesting part. Lets try to decrypt the string #3 from our list of passive DNS requests: lt5ai41qh5d53qoti3mkmc0.appsync-api.us-west-2.avsvmcloud.com The decoded user ID is not relevant, as the decoded NUM part is a number -29 . It’s neither 0 nor 1 , so what kind of domain name that is? If we ignore the NUM part and decode the domain name, using the old method, we will get “thx8xb” , which does not look like a valid domain name. Cases like that are not the noise, and are not some artificially encrypted artifacts that showed up among the DNS requests. This is a different type of DNS requests. Instead of encoding local domain names, these types of requests contain data. They are generated by the malware’s function GetNextStringEx() . The encryption method is different as well. Let’s decrypt this request. First, we can decode the encrypted domain, using the same base-64 method, as before . The string will be decoded into 14 bytes: 7c a5 4d 64 9b 21 c1 74 a6 59 e4 5c 7c 7f Let’s decode these bytes, starting from the 2nd byte, and using the first byte as a XOR key. We will get: 7c d9 31 18 e7 5d bd 08 da 25 98 20 00 03 In this array, the bytes marked in yellow are an 8-byte User ID, encoded with a XOR key that is selected from 2 bytes marked in red. Let’s decode User ID: for ( int i = 0 ; i < 8 ; i++) { bytes[i + 1 ] ^= bytes[ 11 - i % 2 ]; } The decoded byte array becomes: 7c f9 a9 38 7f 7d 25 28 42 25 98 20 00 03 The User ID part in marked in yellow. Does it look familiar? Indeed, it’s the same User ID we’ve seen before, when we decoded “city.kingston.on.ca” . The next 3 bytes marked in red are: 25 98 20 . 2 0x59820 The first number 2 stands for the size of data that follows – this data is 00 03 (selected in green). The number 0x59820 , or 366,624 in decimal, is a timestamp. It’s a number of 4-second periods of time since 1 January 2010. To obtain the real time stamp, we need to multiple it by 15 to get minutes, then add those minutes to 1 January 2010: var date = ( new DateTime( 2010 , 1 , 1 , 0 , 0 , 0 , DateTimeKind.Utc)).AddMinutes(timestamp * 15 ); For the number 0x59820 , the time stamp becomes 16 July 2020 12:00:00 AM – that’s the day when the DNS request was made. The remaining 2 bytes, 00 03 , encrypt the state of 8 security products, to indicate whether each one of them is running or whether it is stopped. The 8 security products are: Windows Live OneCare / Windows Defender Windows Defender Advanced Threat Protection Microsoft Defender for Identity Carbon Black CrowdStrike FireEye ESET F-Secure 2 states for 8 products require 2 * 8 = 16 bits = 2 bytes. The 2 bytes 00 03 in binary form are: 00 00 00 00 00 00 00 11 Here, the least-significant bits 11 identify that the first product in the list, Windows Live OneCare / Windows Defender, is reported as ‘running’ ( 1 ) and as ‘stopped’ ( 1 ). Now we know that apart from the local domain, the trojanised SolarWinds software running on the same compromised host on “city.kingston.on.ca” domain has also reported the status of the Windows Defender software. What Does it Mean? As explained in the first part of our description, the malware is capable of stopping the services of security products, be manipulating registry service keys under Administrator account. It’s likely that the attackers are using DNS queries as a C2 channel to first understand what security products are present. Next, the same channel is used to instruct the malware to stop/deactivate these services, before the 2nd stage payload, TearDrop Backdoor, is deployed. Armed with this knowledge, let’s decode other passive DNS requests, printing the cases when the compromised host reports a running security software. NOTES: As a private case, if the data size field is 0 or 1 , the timestamp field is not followed with any data. Such type of DNS request is generated by the malware’s function GetNextString() . It is called ‘a ping’ in the listing below. If the first part of the domain name is missing, the recovered domain name is pre-pended with ‘*’ . The malware takes the time difference in minutes, then divides it by 30 and then converts the result from double type to int type; as a result of such conversion, the time stamps are truncated to the earliest half hour. 2D82B037C060515C SFBALLET Data: Windows Live OneCare / Windows Defender [running] 11/07/2020 12:00:00 AM Pings: 12/07/2020 12:30:00 AM 70DEE5C062CFEE53 ccscurriculum.c Data: ESET [running] 17/04/2020 4:00:00 PM Pings: 20/04/2020 5:00:00 PM AB902A323B541775 mountsinai.hospital Pings: 4/07/2020 12:30:00 AM 9ACC3A3067DC7FD5 *ripta.com Data: ESET [running] 12/09/2020 6:30:00 AM Pings: 13/09/2020 7:30:00 AM 14/09/2020 9:00:00 AM CB34C4EBCB12AF88 DPCITY.I7a Data: ESET [running] 26/06/2020 5:00:00 PM Pings: 27/06/2020 6:30:00 PM 28/06/2020 7:30:00 PM 29/06/2020 8:30:00 PM 29/06/2020 8:30:00 PM E5FAFE265E86088E *scroot.com Data: CrowdStrike [running] 25/07/2020 2:00:00 PM Pings: 26/07/2020 2:30:00 PM 26/07/2020 2:30:00 PM 27/07/2020 3:00:00 PM 27/07/2020 3:00:00 PM 426030B2ED480DED *kcpl.com Data: Windows Live OneCare / Windows Defender [running] 8/07/2020 12:00:00 AM Carbon Black [running] 8/07/2020 12:00:00 AM Full list of decoded pDNS requests can be found here . An example of a working implementation is available at this repo. Schedule a demo Related Articles Q1 at AlgoSec: What innovations and milestones defined our start to 2026? AlgoSec Reviews Mar 19, 2023 · 2 min read 2025 in review: What innovations and milestones defined AlgoSec’s transformative year in 2025? AlgoSec Reviews Mar 19, 2023 · 2 min read Navigating Compliance in the Cloud AlgoSec Cloud Mar 19, 2023 · 2 min read Speak to one of our experts Speak to one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Schedule a call

Fortinet algosec security management suite Download PDF Download PDF Add a Title Add a Title Add a Title Schedule time with one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Continue

Tsippi Dach, Director of Communications at AlgoSec, explores what happened during this past summer’s Fastly outage, and explores how your... Application Connectivity Management The great Fastly outage Tsippi Dach 2 min read Tsippi Dach Short bio about author here Lorem ipsum dolor sit amet consectetur. Vitae donec tincidunt elementum quam laoreet duis sit enim. Duis mattis velit sit leo diam. Tags Share this article 9/29/21 Published Tsippi Dach, Director of Communications at AlgoSec, explores what happened during this past summer’s Fastly outage, and explores how your business can protect itself in the future. The odds are that before June 8th you probably hadn’t heard of Fastly unless you were a customer. It was only when swathes of the internet went down with the 503: Service Unavailable error message that the edge cloud provider started to make headlines . For almost an hour, sites like Amazon and eBay were inaccessible, costing millions of dollars’ worth of revenue. PayPal, which processed roughly $106 million worth of transactions per hour throughout 2020, was also impacted, and disruption at Shopify left thousands of online retail businesses unable to serve customers. While the true cost of losing a significant portion of the internet for almost one hour is yet to be tallied, we do know what caused it. What is Fastly and why did it break the internet? Fastly is a US-based content distribution network (CDN), sometimes referred to as an ‘edge cloud provider.’ CDNs relieve the load on a website’s servers and ostensibly improve performance for end-users by caching copies of web pages on a distributed network of servers that are geographically closer to them. The downside is that when a CDN goes down – due to a configuration error in Fastly’s case – it reveals just how vulnerable businesses are to forces outside of their control. Many websites, perhaps even yours, are heavily dependent on a handful of cloud-based providers. When these providers experience difficulties, the consequences for your business are amplified ten-fold. Not only do you run the risk of long-term and costly disruption, but these weak links can also provide a golden opportunity for bad actors to target your business with malicious software that can move laterally across your network and cause untold damage. How micro-segmentation can help The security and operational risks caused by these outages can be easily mitigated by implementing plans that should already be part of an organization’s cyber resilience strategy. One aspect of this is micro-segmentation , which is regarded as one of the most effective methods to limit the damage of an intrusion or attack and therefore limit large-scale downtime from configuration misfires and cyberattacks. Micro-segmentation is the act of creating secure “zones” in data centers and cloud deployments that allow your company to isolate workloads from one another. In effect, this makes your network security more compartmentalized, so that if a bad actor takes advantage of an outage in order to breach your organization’s network, or user error causes a system malfunction, you can isolate the incident and prevent lateral impact. Simplifying micro-segmentation with AlgoSec Security Management Suite The AlgoSec Security Management Suite employs the power of automation to make it easy for businesses to define and enforce their micro-segmentation strategy, ensuring that it does not block critical business services, and also meets compliance requirements. AlgoSec supports micro-segmentation by: Mapping the applications and traffic flows across your hybrid network Identifying unprotected network flows that do not cross any firewall and are not filtered for an application Automatically identifying changes that will violate the micro-segmentation strategy Ensuring easy management of network security policies across your hybrid network Automatically implementing network security policy changes Automatically validating changes Generating a custom report on compliance with the micro-segmentation policy Find out more about how micro-segmentation can help you boost your security posture, or request your personal demo . Schedule a demo Related Articles Q1 at AlgoSec: What innovations and milestones defined our start to 2026? AlgoSec Reviews Mar 19, 2023 · 2 min read 2025 in review: What innovations and milestones defined AlgoSec’s transformative year in 2025? AlgoSec Reviews Mar 19, 2023 · 2 min read Navigating Compliance in the Cloud AlgoSec Cloud Mar 19, 2023 · 2 min read Speak to one of our experts Speak to one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Schedule a call

AlgoSec ISO/IEC 27001 Certificate Download PDF Download PDF Add a Title Add a Title Add a Title Schedule time with one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Continue

AlgoSec Security Management Solution for Cisco ACI and Cisco Nexus Dashboard Download PDF Download PDF Add a Title Add a Title Add a Title Schedule time with one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Continue

Securely accelerate digital transformation – A joint VMware AlgoSec webinar VMware AlgoSec Webinar Webinars Securely Accelerate Digital Transformation – A Joint VMware & AlgoSec Webinar This past year was an earthquake. The global pandemic amplified the urgent need for businesses to accelerate digital transformation, at the same time that concerns about security achieved heightened levels of urgency. Digital transformation offers the ability to turn these challenges into opportunities. In this joint session by VMware and AlgoSec, you’ll find out how you can maintain both security and agility throughout your digital business transformation project though the AlgoSec integration with VMware NSX-T. Our experts, Brian Heili from VMware and Jeremiah Cornelius from AlgoSec will show you: How VMware simplifies security deployments with NSX Service-defined Firewall by delivering a fundamentally different, “intrinsic” approach to securing east-west traffic at scale — one that’s built into the hypervisor and available at every host. How to gain complete visibility in NSX and across your entire hybrid network with AlgoSec. How to automatically discover, map and manage application connectivity in VMware NSX. How to assess risk in configuration of all network security policy changes and eliminate error with zero-touch automation. How to ensure continuous compliance, by having AlgoSec monitor and track changes to network security policies, whether on VMware NSX firewalls, traditional firewalls or cloud security control February 17, 2021 Brian Heili Network Security Solution Engineer Jeremiah Cornelius Technical Leader for Alliances and Partners at AlgoSec Relevant resources Tips on How to Create Filtering Policies for VMware NSX Keep Reading Partner Solution Brief: AlgoSec and VMware Read Document Network Security for VMware NSX Watch Video Choose a better way to manage your network Choose a better way to manage your network Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Continue

As with all cloud vendors, AWS users share responsibility for securing their infrastructure against risk. Amazon provides the tools you... AWS Security group architecture for AWS: How to overcome security group limits Prof. Avishai Wool 2 min read Prof. Avishai Wool Short bio about author here Lorem ipsum dolor sit amet consectetur. Vitae donec tincidunt elementum quam laoreet duis sit enim. Duis mattis velit sit leo diam. Tags Share this article 8/9/23 Published As with all cloud vendors, AWS users share responsibility for securing their infrastructure against risk. Amazon provides the tools you need to filter traffic, but configuring those tools is up to you. Firewalls are one of the tools you’ll use to filter traffic and secure Virtual Private Cloud (VPC) instances. Instead of using traditional firewalls, Amazon provides users with AWS security groups, which are flexible, stateful firewalls capable of filtering inbound and outbound traffic. However, there are limits to what you can do with AWS security groups. First, they only allow traffic – you can’t configure them to deny traffic. Second, the maximum number of rules you can set for a single group is 60. This isn’t a big issue for an Amazon EC2 instance designed to address inbound traffic. You’ll either want your AWS EC2 to accept ingress from the entire internet or you’ll want to configure access for a few internal IP addresses. But for outbound traffic, 60 rules simply isn’t enough. You’ll use a dozen of them just allowing access to GitHub’s API . Add in a few third-party partners and you’re already well past the limit. Amazon VPC resource limits explained Amazon sets clear limits on the AWS services and resources it makes available to users. In some cases, you can increase these limits by contacting AWS support. These limits are generally assessed on a per-Region basis. Here are some of the limits Amazon places on AWS users: Security group limits 2500 VPC security groups per Region 60 IPv4 rules per security group 60 IPv6 rules per security group 5 security groups per network interface VPC and subnet limits 5 VPCs per Region 200 Subnets per VPC 5 IPv4 CIDR blocks per VPC 5 IPv6 CIDR blocks per VPC Limits to elastic IP addresses and gateways 5 Elastic IP addresses per Region 2 Elastic IP Addresses per public NAT gateway 5 Egress-only internet gateways per Region 5 NAT gateways per Availability Zone One carrier gateway per VPC Prefix list limits 100 prefix lists per Region 1000 versions per prefix list 5000 prefix list references per resource type Network ACL limits 200 Network ACLs per VPC 20 Rules per Network ACL How to manage AWS cloud security group limits effectively Traditional firewalls may have thousands of security rules, including a complex combination of inbound rules and egress filters. Crucially, they can also enforce outbound rules that include denying traffic – something Amazon does not allow regular security groups to do. While AWS offers powerful tools for securing cloud workflows, Amazon VPC users must find ways to overcome these limitations. Fortunately, there are a few things you can do to achieve exactly that. Optimize your VPC security groups. Use Network Access Control Lists to secure assets at the subnet level. Use a domain name filtering system that reduces the number of IP addresses security group rules need to resolve. Optimize your Amazon virtual private cloud configuration Amazon VPC is a virtual network that contains many of the elements you’d expect from a traditional network. It has IP addresses, route tables, subnets, and internet gateways. Unlike a traditional network, you can easily configure many of your VPC environment through a command line interface (CLI). You can establish VPC peering connections, implement identity and access management (IAM) protocols, and configure elastic network interfaces without manually handling any hardware. But first, you need to set up and protect your VPC by setting up and configuring security groups. If you don’t specify a particular group, Amazon EC2 will use the default security group. If you haven’t added new security groups since creating your AWS account, you may only have that one default security group. The first step to optimizing security is expanding the number of security groups you have available. Here’s an example of the code you can use to create a new security group in the AWS console:aws ec2 create-security-group –group-name web-pci-sg –description “allow SSL traffic” –vpc-id vpc-555666777 This creates a new group named web-pci-sg and describes it as a group designed to allow SSL traffic on the network. Remember that security groups don’t support deny rules. Here is the code you would use to add a rule to that group: aws ec2 authorize-security-group-ingress \ –group-name web-pci-sg \ –protocol https \–port 443 \ –cidr This rule specifically allows SSL traffic using the HTTPS protocol to use port 443, which is the standard port for HTTPS traffic. You can use the last argument to specify the cidr block the rule will direct traffic through. This gives you the ability to manage traffic through specific subnets, which is important for the next step. This example focuses on just one type of rule in one context. To take full advantage of the security tools AWS makes available, you’ll want to create custom rules for endpoints, load balancers, nat gateways, and more. Although you’re limited to 60 rules per security group, creating many groups lets you assign hundreds of rules to any particular instance. Security architecture and network ACLs Network Access Control Lists provide AWS users with additional filtering capabilities. Network ACLs are similar to security groups in many ways, but come with a few key differences: Network ACLs can contain deny rules. You can write Network ACL rules to include explicit actions, like blocking particular IP addresses or routing VPN users in a specific way. Network ACLs are enforced at the subnet level. This means they apply to every instance in the subnet, in addition to whatever rules exist at the security group level. As mentioned above, each Network ACL can contain up to 20 rules. However, you can have up to 200 Network ACLs per VPC, which gives you a total of 4000 potential rules. Along with instance-specific security group rules, this offers much more flexibility for setting up robust AWS security architecture. Since Network ACLs can deny traffic, they are a useful tool for managing access to databases and other sensitive assets. For example, you may wish to exclude users who don’t have the appropriate permissions from your Amazon RDS instance. You may also want to filter SSH (Secure Shell) connections coming from unknown sources, or limit connections between different internal instance types. To do this effectively, you need to group these assets under the same subnet and make sure that the appropriate rules are enabled for all of them. You can also write asset-specific rules at the security group level, ensuring every asset has its own optimal configuration. The larger your AWS environment is, the more complex this process may become. Take care to avoid misconfigurations – it’s very easy to accidentally write security group rules and Network ACL rules that aren’t compatible, or that cause problems when you access the instance. To avoid this, try to condense your rules as much as possible. Avoid limits by filtering domain names directly Although you can create a large number of rules by creating additional security groups, you still may want to add more than 60 rules in a single group. There are many scenarios where this makes more sense than arbitrarily adding (and managing) new groups. For example, you might have a production instance that needs updates from several third-party partners. You also need to periodically change and update the technologies this instance relies on, so you’d like to keep its rules in a single security group. This reduces misconfiguration risk by keeping all the relevant rules in one place – not spread out across multiple groups. To overcome this limit, you need to reduce the number of IP addresses that the security group filters. You can do this by deploying a third-party solution that allows security rules to perform DNS resolution. This eliminates the need for AWS to resolve the domain name. Since AWS security groups can’t compute domain names on their own, you’ll need to deploy a third-party NAT gateway on your public VPC to filter outbound traffic in this way. Once you do this, you can write rules that filter outgoing connections based on their domain name. This effectively bypasses the 60 IP limit because you are not referring to specific IP addresses. At the same time, it simplifies management and makes rules much easier to read and understand. Instead of looking up and adding all of Github’s API IP addresses, you can write rules that reference the domain “Github.com”. If Github decides to change its IP infrastructure, your security rules will automatically reference the new addresses – you won’t have to go back and update them. The earlier you address AWS security group limits, the better There is an unlimited number of ways you can arrange your security groups and Network ACLs. Even in a small environment, the prospect may seem daunting. However, the flexibility Amazon provides to its cloud users is a valuable security feature. Those who go the process enjoy clear security performance benefits. If you start to planning for the architecture of your security and filtering policies early, you’ll be better equipped to scale those policies upwards as your organization grows. This will prevent security processes from becoming a growth bottleneck and maintain a high level of efficiency even as those policies become larger and more complex. See me explain this issue in person in my new whiteboard video: Schedule a demo Related Articles Q1 at AlgoSec: What innovations and milestones defined our start to 2026? AlgoSec Reviews Mar 19, 2023 · 2 min read 2025 in review: What innovations and milestones defined AlgoSec’s transformative year in 2025? AlgoSec Reviews Mar 19, 2023 · 2 min read Navigating Compliance in the Cloud AlgoSec Cloud Mar 19, 2023 · 2 min read Speak to one of our experts Speak to one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Schedule a call

The cloud visibility imperative WhitePaper Download PDF Download PDF Add a Title Add a Title Add a Title Schedule time with one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Continue

Webinars Optimize your Juniper Investment with Intelligent Network Security Automation Are you maximizing all the capabilities that your Juniper solutions offer? Expand its potential and maximize your ROI. Discover how to secure your homogeneous and multi-vendor network with intelligent automation. In this webinar, Max Shirshov, EMEA Solutions Architect at AlgoSec, will demonstrate how to assess risk and audit the firewall estate for regulatory compliance, address security breaches caused by misconfigured network devices, and provide fast and efficient change management utilizing the AlgoSec Security Management solution for your Juniper devices. Join the webinar to learn how to: Gain complete visibility into your Juniper-estate as well as multi-vendor and hybrid networks Intelligently push security policy changes to your Netscreen and SRX firewalls, MX routers and Juniper Space, as well as other vendors’ security devices, SDN and public clouds Automate application and user aware security policy management and ensure your Juniper devices are properly configured Assess risk and ensure regulatory compliance across your entire enterprise environment March 24, 2020 Max Shirshov Relevant resources AlgoSec & Juniper Networks Keep Reading The Juniper Networks Vulnerability Does Not Change Network Security Fundamentals Keep Reading Choose a better way to manage your network Choose a better way to manage your network Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Continue

Stay informed with the latest news and updates from Algosec, including product launches, industry insights, and company announcements. In the News Contact sales Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Continue Filter by release year Select Year Manage firewall rules focused on applications December 20, 2023 Prof. Avishai Wool, CTO and Co-founder of AlgoSec: Innovation is key : Have the curiosity and the willingness to learn new things, the ability to ask questions and to not take things for granted December 20, 2023 Efficiently contain cyber risks December 20, 2023 The importance of IT compliance in the digital landscape December 20, 2023 Minimize security risks with micro-segmentation December 20, 2023

In this webinar, Omer Ganot, AlgoSec’s Cloud Security Product Manager, and Stuti Deshpande s, Amazon Web Service’s Partner Solutions Architect, will share security challenges in the hybrid cloud and provide tips to protect your AWS and hybrid environment Webinars Overcoming hybrid environment management challenges | AWS & AlgoSec Webinar Public clouds such as Amazon Web Services (AWS) are a critical part of your hybrid network. It is important to keep out the bad guys (including untrusted insiders) and proactively secure your entire hybrid network. Securing your network is both the responsibility of the cloud providers, as well as your organization’s IT and CISOs – the shared responsibility model. As a result, your organization needs visibility into what needs to be protected, as well as an understanding of the tools that are available to keep them secure. In this webinar, Omer Ganot, AlgoSec’s Cloud Security Product Manager, and Stuti Deshpande’s, Amazon Web Service’s Partner Solutions Architect, will share security challenges in the hybrid cloud and provide tips to protect your AWS and hybrid environment, including how to: Securely migrate workloads from on-prem to public cloud Gain unified visibility into your network topology and traffic flows, including both public cloud and on-premises assets, from a single console. Manage/orchestrate multiple layers of security controls and proactively detect misconfigurations Protect your data, accounts, and workloads from misconfiguration risks Protect web applications in AWS by filtering traffic and blocking common attack patterns, such as SQL injection or cross-site scripting Gain a unified view of your compliance status and achieve continuous compliance September 30, 2020 Stuti Deshpande Partner Solution Architect, AWS Omer Ganot Product Manager Relevant resources Migrating Business Applications to AWS? Tips on Where to Start Keep Reading Tips for auditing your AWS security policies, the right way Keep Reading Choose a better way to manage your network Choose a better way to manage your network Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Continue

Cloud threats increased by 95 percent in 2022 alone! At a time when many organizations are moving their resources to the cloud and security threats are at an all-time high, focusing on your cloud security architecture has never been more critical. While cloud adoption has revolutionized businesses, it has also brought complex challenges. For example, cloud environments can be susceptible to numerous security threats. Besides, there are compliance regulations that you must address. This is... Cloud Security Cloud Security Architecture: Methods, Frameworks, & Best Practices Rony Moshkovich 2 min read Rony Moshkovich Short bio about author here Lorem ipsum dolor sit amet consectetur. Vitae donec tincidunt elementum quam laoreet duis sit enim. Duis mattis velit sit leo diam. Tags Share this article 8/8/23 Published Cloud threats increased by 95 percent in 2022 alone! At a time when many organizations are moving their resources to the cloud and security threats are at an all-time high, focusing on your cloud security architecture has never been more critical. While cloud adoption has revolutionized businesses, it has also brought complex challenges. For example, cloud environments can be susceptible to numerous security threats. Besides, there are compliance regulations that you must address. This is why it’s essential to implement the right methods, frameworks, and best practices in cloud environments. Doing so can protect your organization’s sensitive cloud resources, help you meet compliance regulations, and maintain customer trust. Understanding Cloud Security Architecture Cloud security architecture is the umbrella term that covers all the hardware, software, and technologies used to protect your cloud environment. It encompasses the configurations and secure activities that protect your data, workloads, applications, and infrastructure within the cloud. This includes identity and access management (IAM), application and data protection, compliance monitoring, secure DevOps, governance, and physical infrastructure security. A well-defined security architecture also enables manageable decompositions of cloud deployments, including mixed SaaS, PaaS, and IaaS deployments. This helps you highlight specific security needs in each cloud area. Additionally, it facilitates integration between clouds, zones, and interfaces, ensuring comprehensive coverage of all deployment aspects. Cloud security architects generally use a layered approach when designing cloud security. Not only does this improve security, but it also allows companies to align business needs with technical security practices. As such, a different set of cloud stakeholders, including business teams and technical staff, can derive more value. The Fundamentals of Cloud Security Architecture Every cloud computing architecture has three core fundamental capabilities; confidentiality, integrity, and availability. This is known as the CIA triad. Understanding each capability will guide your efforts to build, design, and implement safer cloud environments. 1. Confidentiality This is the ability to keep information hidden and inaccessible to unauthorized entities, such as attackers, malware, and people in your organization, without the appropriate access level. Privacy and trust are also part of confidentiality. When your organization promises customers to handle their data with utmost secrecy, you’re assuring them of confidentiality. 2. Integrity Integrity means that the services, systems, and applications work and behave exactly how you expect. That is, their output is consistent, accurate, and trustworthy. If these systems and applications are compromised and produce unexpected or misleading results, your organization may suffer irreparable damage. 3. Availability As the name implies, availability assures your cloud resources are consistently accessible and operational when needed. So, suppose an authorized user (whether customers or employees) needs data and applications in the cloud, such as your products or services. In that case, they can access it without interruption or significant downtime. Cybercriminals sometimes use denial-of-service (DoS) attacks to prevent the availability of cloud resources. When this happens, your systems become unavailable to you or your customers, which isn’t ideal. So, how do you stop that from happening and ensure your cloud security architecture provides these core capabilities? Approaches to Cloud Security Architecture There are multiple security architecture approaches, including frameworks and methodologies, to support design and implementation steps. Cloud Security Frameworks and Methodologies A cloud security framework outlines a set of guidelines and controls your organizations can use when securing data, applications, and infrastructures within the cloud computing environment. Frameworks provide a structured approach to detecting risks and implementing appropriate security protocols to prevent them. Without a consistent cloud security framework, your organization exposes itself to more vulnerabilities. You may lack the comprehensive visibility to ensure your data and applications are adequately secure from unauthorized access, data exposure, malware, and other security threats. Plus, you may have limited incident response capabilities, inconsistent security practices, and increased operational risks. A cloud security framework also helps you stay compliant with regulatory requirements. Lastly, failing to have appropriate security frameworks can erode customer trust and confidence in your ability to protect their privacy. This is why you must implement a recognized framework to significantly reduce potential risks associated with cloud security and ensure the CIA of data and systems. There are numerous security frameworks. Some are for governance (e.g., COBIT and COSO), architecture (e.g., SABSA), and the NIST cybersecurity framework. While these generally apply broadly to technology, they may also apply to cloud environments. Other cloud-specific frameworks include the ISO/IEC 27017:2015, Cloud Control Matrix (CCM), Cloud Security Alliance, and the FedRAMP. 1. NIST Cybersecurity Framework (NIST CSF) The National Institute of Standards and Technology’s Cybersecurity Framework (NIST CSF) outlines a set of guidelines for securing security systems. It has five core capabilities: Identify, Protect, Detect, Respond, and Recover. Identify – What processes, assets, and systems need protection? Protect – Develop and implement the right safeguards to ensure critical infrastructure services delivery. Detect – Implement the appropriate mechanisms to enable the timely discovery of cybersecurity incidents. Respond – Develop techniques to contain the impact of potential cybersecurity incidents. Recover – Implement appropriate measures to restore business capabilities and services affected by cybersecurity events. While the NIST CSF is a general framework for the security of your organization’s systems, these five pillars can help you assess and manage cloud-related security risks. 2. ISO/IEC 27017:2015 ISO 27017 is a cloud security framework that defines guidelines on information security issues specific to the cloud. The framework’s security controls add to the ISO/IEC 27002 and ISO/IEC 27001 standards’ recommendations. The framework also offers specific security measures and implementation advice for cloud service providers and applications. 3. Sherwood Applied Business Security Architecture (SABSA) First developed by John Sherwood, SABSA is an Enterprise Security Architecture Framework that provides guidelines for developing business-driven, risk, and opportunity-focused security architectures to support business objectives. The SABSA framework aims to prioritize your business needs, meaning security services are designed and developed to be an integral part of your business and IT infrastructure. Here are some core principles of the Gartner-recommended SABSA framework for enterprises: It is business-driven. SABSA ensures security is integrated into your entire business strategy. This means there’s a strong emphasis on understanding your organization’s business objectives. So, any security measure is aligned with those objectives. SABSA is a risk-based approach. It considers security vulnerabilities, threats, and their potential impacts to prioritize security operations and investments. This helps your organization allocate resources effectively to address the most critical risks first. It promotes a layered security architecture. Earlier, we mentioned how a layered approach can help you align business and technical needs. So, it’s expected that this is a core principle of SABSA. This allows you to deploy multiple security controls across different layers, such as physical security, network security, application security, and data security. Each layer focuses on a specific security aspect and provides special controls and measures. Transparency: SABSA provides two-way traceability; that is, a clear two-way relationship exists between aligning security requirements and business goals. This provides a clear overview of where expenditure is made ad the value that is returned. Modular approach: SABSA offers agility for ease of implementation and management. This can make your business flexible when meeting changing market or economic conditions. 4. MITRE ATT&CK The MITRE ATT&CK framework is a repository of techniques and tactics that threat hunters, defenders, red teams, and security architects can use to classify, identify, and assess attacks. Instead of focusing on security controls and mechanisms to mitigate threats, this framework targets the techniques that hackers and other threat actors use in the cloud. So, using this framework can be excellent if you want to understand how potential attack vectors operate. It can help you become proactive and strengthen your cloud security posture through improved detection and incident response. 5. Cloud Security Alliance Cloud Controls Matrix (CSA CCM) The CSA CCM is a cybersecurity control framework specifically for cloud computing. It contains 197 control objectives structured in 17 domains that cover every critical aspect of cloud technology. Cloud customers and cloud service providers (CSPs) can use this tool to assess cloud implementation systematically. It also guides customers on the appropriate security controls for implementation by which actor in the cloud supply chain. 6. Cloud Security Alliance Security Trust Assurance and Risk (CSA STAR) The CSA STAR framework is for CSPs. It combines the principles of transparency, thorough auditing, and harmonization of standards. What CSA STAR does is to help you, as a cloud customer, assess a cloud service provider’s reliability and security posture. There are two ways this can happen: CSA STAR Certification: This is a rigorous third-party assessment of the CSP’s security controls, posture, and practices. The CSP undergoes a thorough audit based on the CSA’s Cloud Control Matrix (CCM), which is a set of cloud security controls aligned with industry standards. CSA STAR Self-Assessment: The CSA also has a Consensus Assessment Initiative Questionnaire (CAIQ). CSPs can use this to test and report on their security controls and practices. Since it’s a self-assessment procedure, it allows CSPs to be transparent, enabling customers like you to understand a CSP’s security capabilities before adopting their services. Challenges and Considerations in Cloud Security Architecture Before any cloud deployment, it’s important to understand the threats you may face, such as privilege-based attacks and malware, and be prepared for them. Since there are many common threats, we’ll quickly run through the most high-profile ones with the most devastating impacts. It’s important to remember some threats may also be specific to the type of cloud service model. 1. Insider risks This includes the employees in your organization who have access to data, applications, and systems, as well as CSP administrators. Whenever you subscribe to a CSP’s services, you entrust your workloads to the staff who maintain the CSP architecture. 2. DoS attacks Direct denial-of-service (DDoS) attacks are critical issues in cloud environments. Although security perimeters can deflect temporary DDoS attacks to filter out repeated requests, permanent DoS attacks are more damaging to your firmware and render the server unbootable. If this happens, you may need to physically reload the firmware and rebuild the system from the ground up, resulting in business downtime for weeks or longer. 3. Data availability You also want to consider how much of your data is accessible to the government. Security professionals are focusing on laws and examples that demonstrate when and how government authorities can access data in the cloud, whether through legal processes or court rulings. 4. Cloud-connected Edge Systems The concept of “cloud edge” encompasses both edge systems directly connected to the cloud and server architecture that is not directly controlled by the cloud service provider (CSP). To extend their services to smaller or remote locations, global CSPs often rely on partners as they cannot have facilities worldwide. Consequently, CSPs may face limitations in fully regulating hardware monitoring, ensuring physical box integrity, and implementing attack defenses like blocking USB port access. 5. Hardware Limitations Having the most comprehensive cloud security architecture still won’t help you create stronger passwords. While your cloud security architects focus on the firmware, hardware, and software, it’s down to the everyday users to follow best practices for staying safe. Best Practices in Cloud Security Architecture The best practices in Cloud Security Architecture are highlighted below: 1. Understand the shared responsibility model Cloud security is implemented with a shared responsibility model. Although, as the cloud customer, you may have most of the obligation, the cloud provider also shares some of the responsibility. Most vendors, such as Amazon Web Services (AWS) and Microsoft Azure, have documentation that clearly outlines your specific responsibilities depending on the deployment type. It’s important to clearly understand your shared responsibility model and review cloud vendor policies. This will prevent miscommunications and security incidents due to oversight. 2. Secure network design and segmentation This is one of the principles of cloud security architecture – and by extension, a best practice. Secure network design and segmentation involve dividing the network into isolated segments to avoid lateral movements during a breach. Implementing network segmentation allows your organization to contain potential risks and attacks within a specific segment. This can minimize the effects of an incident on your entire network and protect critical assets within the cloud infrastructure. 3. Deploy an Identity and access management (IAM) solution Unauthorized access is one of the biggest problems facing cloud security. Although hackers now use sophisticated tools to gain access to sensitive data, implementing a robust identity and access management (IAM) system can help prevent many threats. Consider access policies like role-based access control (RBAC) permissions, multi-factor authentication (MFA), and continuous threat monitoring. 4. Consider a CASB or Cloud Security Solution (e.g., Cloud-Native Application Protection (CNAPP) and Cloud Workload Protection Platforms (CWPP) Cloud Access Security Brokers (CASBs) provide specialized tools to enforce cloud security policies. Implementing a CASB solution is particularly recommended if you have a multi-cloud environment involving different vendors. Since a CASB acts as an intermediary between your organization’s on-premise infrastructure and CSPs, it allows your business to extend security policies and controls to the cloud. CASBs can enhance your data protection through features like data loss prevention, tokenization, and encryption. Plus, they help you discover and manage shadow IT through visibility into unauthorized cloud services and applications. Besides CASB solutions, you should also consider other solutions for securing your cloud environments. This includes cloud-native application protection (CNAPP) and cloud workload protection platforms (CWPP). For example, a CNAPP like Horizon ACE can improve your cloud security architecture with tailored solutions and automated security management. 5. Conduct Audits, Penetration Testing, and Vulnerability Testing Whether or not you outsource security, performing regular penetration tests and vulnerability is necessary. This helps you assess the effectiveness of your cloud security measures and identify potential weaknesses before hackers exploit them. You should also perform security audits that evaluate cloud security vendors’ capabilities and ensure appropriate access controls are in place. This can be achieved by using the guidelines of some frameworks we mentioned earlier, such as the CSA STAR. 6. Train Your Staff Rather than hiring new hires, training your current staff may be beneficial. Your employees have been at your company for a while and are already familiar with the organization’s culture, values, and processes. This could give them an advantage over new hires. As most existing IT skills can be reused, upskilling employees is more efficient and may help you meet the immediate need for a cloud IT workforce. Train your staff on recognizing simple and complex cybersecurity threats, such as creating strong passwords, identifying social engineering attacks, and advanced topics like risk management. 7. Mitigate Cloud Misconfigurations A misconfigured bucket could give access to anyone on the internet. To minimize cloud misconfigurations and reduce security risks, managing permissions in cloud services carefully is crucial. Misconfigurations, such as granting excessive access permissions to external users, can enable unauthorized access and potential data breaches. Attackers who compromise credentials can escalate their privileges, leading to further data theft and broader attacks within the cloud infrastructure. Therefore, it is recommended that IT, storage, or security teams, with assistance from development teams, personally configure each cloud bucket, ensuring proper access controls and avoiding default permissions. 8. Ensure compliance with regulatory requirements Most organizations today need to comply with strict regulatory requirements. This is especially important if you collect personally identifiable information (PII) or if your business is located in certain regions. Before you adopt a new cloud computing service, assess their compliance requirements and ensure they can fulfill data security needs. Failure to meet compliance requirements can lead to huge penalties. Other best practices for your cloud security include continuous monitoring and threat intelligence, data encryption at rest and in transit, and implementing intrusion detection and intrusion prevention systems. Conclusion When establishing a robust cloud security architecture, aligning business objectives and technical needs is important. Your organization must understand the shared responsibility model, risks, the appropriate implementation framework, and best practices. However, designing and developing cloud computing architectures can be complicated. Horizon ACE can secure your multi-cloud environment in minutes. Want to improve your cloud security configuration management? Horizon ACE’s agentless CNAPP can provide complete visibility over cloud resources, ensure compliance, and provide advanced risk monitoring and threat intelligence. Speak to us now. Schedule a demo Related Articles Q1 at AlgoSec: What innovations and milestones defined our start to 2026? AlgoSec Reviews Mar 19, 2023 · 2 min read 2025 in review: What innovations and milestones defined AlgoSec’s transformative year in 2025? AlgoSec Reviews Mar 19, 2023 · 2 min read Navigating Compliance in the Cloud AlgoSec Cloud Mar 19, 2023 · 2 min read Speak to one of our experts Speak to one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Schedule a call