As organizations respond to an ever-evolving set of security threats, network teams are scrambling to find new ways to keep up with... Auditing and Compliance Continuous compliance monitoring best practices 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 3/19/23 Published As organizations respond to an ever-evolving set of security threats, network teams are scrambling to find new ways to keep up with numerous standards and regulations to dodge their next compliance audit violation. Can this nightmare be avoided? Yes, and it’s not as complex as one might think if you take a “compliance first” approach . It may not come as a surprise to many, but the number of cyber attacks is increasing every year and with it the risk to companies’ financial, organizational, and reputational standing. What’s at stake? The stakes are high when it comes to cyber security compliance. A single data breach can result in massive financial losses, damage to a company’s reputation, and even jail time for executives. Data breaches: Data breaches are expensive and becoming even more so by the day. According to the Ponemon Institute’s 2022 Cost of a Data Breach Report , the average cost of a data breach is $4.35 million. Fraud: Identity fraud is one of the most pressing cybersecurity threats today. In large organizations, the scale of fraud is also usually large, resulting in huge losses causing depletion of profitability. In a recent survey done by PwC, nearly one in five organizations said that their most disruptive incident cost over $50 million*. Theft: Identity theft is on the rise and can be the first step towards compromising a business. According a study from Javelin Strategy & Research found that identity fraud costs US businesses an estimated total of $56 billion* in 2021. What’s the potential impact? The potential impact of non-compliance can be devastating to an organization. Financial penalties, loss of customers, and damage to reputation are just a few of the possible consequences. To avoid these risks, organizations must make compliance a priority and take steps to ensure that they are meeting all relevant requirements. Legal impact:  Regulatory or legal action brought against the organization or its employees that could result in fines, penalties, imprisonment, product seizures, or debarment.  Financial impact:  Negative impacts with regard to the organization’s bottom line, share price, potential future earnings, or loss of investor confidence.  Business impact:  Adverse events, such as embargos or plant shutdowns, could significantly disrupt the organization’s ability to operate.  Reputational impact:  Damage to the organization’s reputation or brand—for example, bad press or social-media discussion, loss of customer trust, or decreased employee morale.  How can this be avoided? In order to stay ahead of the ever-expanding regulatory requirements, organizations must adopt a “compliance first” approach to cyber security. This means enforcing strict compliance criteria and taking immediate action to address any violations to ensure data is protected. Some of these measures include the following: Risk assessment: Conduct ongoing monitoring of compliance posture (risk assessment) and conduct regular internal audits (ensuring adherence with regulatory and legislative requirements (HIPAA, GDPR, PCI DSS, SOX, etc.) Documentation: Enforce continuous tracking of changes and intent Annual audits: Commission 3rd party annual audits to ensure adherence with regulatory and legislative requirements (HIPAA, GDPR, PCI DSS, SOX, etc.) Conclusion and next steps Compliance violations are no laughing matter. They can result in fines, business loss, and even jail time in extreme cases. They can be difficult to avoid unless you take the right steps to avoid them. You have a complex set of rules and regulations to follow as well as numerous procedures, processes, and policies. And if you don’t stay on top of things, you can end up with a compliance violation mess that is difficult to untangle. Fortunately, there are ways to reduce the risk of being blindsided by a compliance violation mess with your organization. Now that you know the risks and what needs to be done, here are six best practices for achieving it. External links: $50 million $56 billion 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

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

AlgoSec application discovery Enhance the discovery of your network applications 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 Cloud Enterprise (Horizon ACE) is the comprehensive cloud network security suite for the modern cloud enterprise. Gain visibility, enforce consistent policies, and automate change management across cloud and on-premises environments. AlgoSec Cloud Enterprise: Transform your cloud network security with AlgoSec Empower your organization to secure application connectivity across multi-cloud environments with the industry's leading platform Schedule a demo Watch a video Watch a video Securing the cloud enterprise:
 Navigating the complexities of cloud network security In today's digital landscape, securing application connectivity is more critical than ever. Organizations face complex challenges in managing security across hybrid environments, leading to potential vulnerabilities and compliance risks. AlgoSec offers a comprehensive solution that provides deep visibility, automates security changes, and ensures continuous compliance. Our platform integrates seamlessly with your existing infrastructure, enabling you to: Streamline Security Policies Reduce manual interventions and accelerate application delivery. Enhance Visibility Gain a unified view of your network's security posture. Ensure Compliance Stay ahead of regulatory requirements with automated compliance checks. The comprehensive cloud network security platform Unifying security across your applications Deep application visibility Compliance management Automate security & compliance Streamlined change management Horizon ACE’s application first approach simplifies cloud network security with: Deep visibility Map and secure your cloud applications. Gain deep visibility into your cloud network and address over 150 cloud-specific risks including vulnerabilities in security groups, cloud firewalls, and container configurations. Consistent enforcement Apply unified security policies across your cloud and on-premises environments, ensuring consistent protection for all your applications. Automated change management Streamline updates and reduce errors with automated workflows for security policy changes and configuration updates. Deep application visibility Horizon ACE is the comprehensive cloud network security platform you need to protect your organization. Unified security policy management Streamlined change management Automate security & compliance Elevate your cloud network security with Horizon ACE Horizon ACE provides a comprehensive suite of capabilities to help you secure your cloud network security, including: Unified security & compliance across hybrid environments Seamlessly extend security policy visibility, compliance and change automation across cloud and on-premises infrastructures. Application 
visibility Automatically discover application dependencies and traffic flows across multi-cloud environments. Compliance management across the hybrid environment Monitor your compliance posture across your entire hybrid environment, ensuring adherence to industry standards and regulations. Unmatched network security posture Over 150+ network security policy risks checks plus customize risks enabling unique segmentation or zero trust policy enforcement. Application context to cloud network risk mapping Map cloud network security risks to applications. By using Horizon ACE, you can significantly improve the network security of your applications and reduce the risk of a data breach. Ready to secure your applications? Trusted by over 2,200 organizations worldwide, including 20 of the Fortune 50, AlgoSec is the preferred choice for enterprises seeking robust network security solutions. How much will Horizon ACE cost and how much will it save your company? Check the Horizon ACE ROI calculator for more information. Take the next step: AlgoSec Cloud Enterprise Cloud connectivity without compromise Learn more 6 best practices to stay secure in the hybrid cloud   Read eBook AlgoSec cloud product demo Watch it now Schedule a demo today and experience the future of network security. Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Continue

Algosec for Azure automates security policy management, enhances visibility, and ensures compliance across your Azure cloud environment. Microsoft Azure & AlgoSec Visibility, Risk Management and Change Automation for Azure Environments AlgoSec manages security policies across cloud, hybrid and on-prem environments, delivering proactive risk and compliance analysis, end-to-end change management and automation – all in the business application context. AlgoSec supports enterprises in their journey to the cloud by automatically mapping existing application connectivity prior to the migration, determining and facilitating required connectivity changes during the move, and ensuring continuous compliance and automated change management in the newly established hybrid cloud environment. AlgoSec completes the picture, providing clear visibility and effective management of Microsoft Azure’s native security constructs – Network Security Groups (NSGs) and Azure Firewalls – as well as 3rd party virtual firewalls deployed in the Azure cloud. AlgoSec for Microsoft Azure firewall is available now. Sign up here Automated Security Policy Management for Azure Network Security Groups With AlgoSec, you gain visibility into your entire Azure cloud estate, including network topology and connectivity, the effective security enforcement by Azure Network Security Groups, and aggregated risk and compliance analysis across Azure and 3rd party security devices. AlgoSec also provides an end-to-end change management and automation solution, covering security policies in the cloud, as well as on-premises SDN and traditional networks. Central Management for Azure Firewall Azure Firewall is a new managed, cloud-based network security service that protects your Azure Virtual Network resources. With AlgoSec, you can manage multiple instances of the Azure Firewall using a shared policy model, to facilitate and automate security policy management in multi-region cloud environments. In addition, the AlgoSec solution provides end-to-end visibility and management capabilities across the Azure Firewalls, Azure NSGs and 3rd party firewalls, in the cloud and on-prem. Key benefits Unified security Unified security policy management across cloud, SDN and on-premise networks Cloud visibility Visibility into the Azure cloud network, topology and connectivity Securing cloud estate Securing your cloud estate from misconfigurations with risk alerts as well as overall risk visibility Automation Automated Azure NSG and 3rd party firewall changes, eliminating misconfigurations and rework Proactive assessment Proactive assessment the impact of network changes to ensure continuous compliance Simplified and automate Simplified and automate internal and regulatory audits, and reduce time and costs by as much as 80% Cloud and Hybrid Environments Download infographic Schedule time with one of our experts

Update : Next two parts of the analysis are available here and here . As earlier reported by FireEye, the actors behind a global... Cloud Security Sunburst Backdoor: A Deeper Look Into The SolarWinds’ Supply Chain Malware 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/15/20 Published Update : Next two parts of the analysis are available here and here . As earlier reported by FireEye, the actors behind a global intrusion campaign have managed to trojanise SolarWinds Orion business software updates in order to distribute malware. The original FireEye write-up already provides a detailed description of this malware. Nevertheless, as the malicious update SolarWinds-Core-v2019.4.5220-Hotfix5.msp was still available for download for hours since the FireEye’s post, it makes sense to have another look into the details of its operation. The purpose of this write-up is to provide new information, not covered in the original write-up. Any overlaps with the original description provided by FireEye are not intentional. For start, the malicious component SolarWinds.Orion.Core.BusinessLayer.dll inside the MSP package is a non-obfuscated .NET assembly. It can easily be reconstructed with a .NET disassembler, such as ILSpy , and then fully reproduced in C# code, using Microsoft Visual Studio. Once reproduced, it can be debugged to better understand how it works. In a nutshell, the malicious DLL is a backdoor. It is loaded into the address space of the legitimate SolarWinds Orion process SolarWinds.BusinessLayerHost.exe or SolarWinds.BusinessLayerHostx64.exe . The critical strings inside the backdoor’s class SolarWinds.Orion.Core.BusinessLayer.OrionImprovementBusinessLayer are encoded with the DeflateStream Class of the .NET’s System.IO.Compression library, coupled with the standard base64 encoder. Initialisation Once loaded, the malware checks if its assembly file was created earlier than 12, 13, or 14 days ago. The exact number of hours it checks is a random number from 288 to 336. Next, it reads the application settings value ReportWatcherRetry . This value keeps the reporting status, and may be set to one of the states: New (4) Truncate (3) Append (5) When the malware runs the first time, its reporting status variable ReportWatcherRetry is set to New (4) . The reporting status is an internal state that drives the logic. For example, if the reporting status is set to Truncate , the malware will stop operating by first disabling its networking communications, and then disabling other security tools and antivirus products. In order to stay silent, the malware periodically falls asleep for a random period of time that varies between 30 minutes and 2 hours. At the start, the malware obtains the computer’s domain name . If the domain name is empty, the malware quits. It then generates a 8-byte User ID, which is derived from the system footprint. In particular, it is generated from MD5 hash of a string that consists from the 3 fields: the first or default operational (can transmit data packets) network interface’s physical address computer’s domain name UUID created by Windows during installation (machine’s unique ID) Even though it looks random, the User ID stays permanent as long as networking configuration and the Windows installation stay the same. Domain Generation Algorithm The malware relies on its own CryptoHelper class to generate a domain name. This class is instantiated from the 8-byte User ID and the computer’s domain name, encoded with a substitution table: “rq3gsalt6u1iyfzop572d49bnx8cvmkewhj” . For example, if the original domain name is “ domain “, its encoded form will look like: “ n2huov “. To generate a new domain, the malware first attempts to resolve domain name “ api.solarwinds.com “. If it fails to resolve it, it quits. The first part of the newly generated domain name is a random string, produced from the 8-byte User ID, a random seed value, and encoded with a custom base64 alphabet “ph2eifo3n5utg1j8d94qrvbmk0sal76c” . Because it is generated from a random seed value, the first part of the newly generated domain name is random. For example, it may look like “ fivu4vjamve5vfrt ” or “ k1sdhtslulgqoagy “. To produce the domain name, this string is then appended with the earlier encoded domain name (such as “ n2huov “) and a random string, selected from the following list: .appsync-api.eu-west-1[.]avsvmcloud[.]com .appsync-api.us-west-2[.]avsvmcloud[.]com .appsync-api.us-east-1[.]avsvmcloud[.]com .appsync-api.us-east-2[.]avsvmcloud[.]com For example, the final domain name may look like: fivu4vjamve5vfrtn2huov[.]appsync-api.us-west-2[.]avsvmcloud[.]com or k1sdhtslulgqoagyn2huov[.]appsync-api.us-east-1[.]avsvmcloud[.]com Next, the domain name is resolved to an IP address, or to a list of IP addresses. For example, it may resolve to 20.140.0.1 . The resolved domain name will be returned into IPAddress structure that will contain an AddressFamily field – a special field that specifies the addressing scheme. If the host name returned in the IPAddress structure is different to the queried domain name, the returned host name will be used as a C2 host name for the backdoor. Otherwise, the malware will check if the resolved IP address matches one of the patterns below, in order to return an ‘address family’: IP Address Subnet Mask ‘Address Family’ 10.0.0.0 255.0.0.0 Atm 172.16.0.0 255.240.0.0 Atm 192.168.0.0 255.255.0.0 Atm 224.0.0.0 240.0.0.0 Atm fc00:: fe00:: Atm fec0:: ffc0:: Atm ff00:: ff00:: Atm 41.84.159.0 255.255.255.0 Ipx 74.114.24.0 255.255.248.0 Ipx 154.118.140.0 255.255.255.0 Ipx 217.163.7.0 255.255.255.0 Ipx 20.140.0.0 255.254.0.0 ImpLink 96.31.172.0 255.255.255.0 ImpLink 131.228.12.0 255.255.252.0 ImpLink 144.86.226.0 255.255.255.0 ImpLink 8.18.144.0 255.255.254.0 NetBios 18.130.0.0 255.255.0.0 NetBios 71.152.53.0 255.255.255.0 NetBios 99.79.0.0 255.255.0.0 NetBios 87.238.80.0 255.255.248.0 NetBios 199.201.117.0 255.255.255.0 NetBios 184.72.0.0 255.254.0.0 NetBios For example, if the queried domain resolves to 20.140.0.1 , it will match the entry in the table 20.140.0.0 , for which the returned ‘address family’ will be ImpLink . The returned ‘address family’ invokes an additional logic in the malware. Disabling Security Tools and Antivirus Products If the returned ‘address family’ is ImpLink or Atm , the malware will enumerate all processes and for each process, it will check if its name matches one of the pre-defined hashes. Next, it repeats this processed for services and for the drivers installed in the system. If a process name or a full path of an installed driver matches one of the pre-defined hashes, the malware will disable it. For hashing, the malware relies on Fowler–Noll–Vo algorithm. For example, the core process of Windows Defender is MsMpEng.exe . The hash value of “ MsMpEng ” string is 5183687599225757871 . This value is specifically enlisted the malware’s source under a variable name timeStamps : timeStamps = new ulong[1] { 5183687599225757871uL } The service name of Windows Defender is windefend – the hash of this string ( 917638920165491138 ) is also present in the malware body. As a result, the malicioius DLL will attempt to stop the Windows Defender service. In order to disable various security tools and antivirus products, the malware first grants itself SeRestorePrivilege and SeTakeOwnershipPrivilege privileges, using the native AdjustTokenPrivileges() API. With these privileges enabled, the malware takes ownership of the service registry keys it intends to manipulate. The new owner of the keys is first attempted to be explicitly set to Administrator account. If such account is not present, the malware enumerates all user accounts, looking for a SID that represents the administrator account. The malware uses Windows Management Instrumentation query “ Select * From Win32_UserAccount ” to obtain the list of all users. For each enumerated user, it makes sure the account is local and then, when it obtains its SID, it makes sure the SID begins with S-1-5- and ends with -500 in order to locate the local administrator account. Once such account is found, it is used as a new owner for the registry keys, responsible for manipulation of the services of various security tools and antivirus products. With the new ownership set, the malware then disables these services by setting their Start value to 4 (Disabled): registryKey2.SetValue(“Start”), 4, RegistryValueKind.DWord); HTTP Backdoor If the returned ‘address family’ for the resolved domain name is NetBios , as specified in the lookup table above, the malware will initialise its HttpHelper class, which implements an HTTP backdoor. The backdoor commands are covered in the FireEye write-up, so let’s check only a couple of commands to see what output they produce. One of the backdoor commands is CollectSystemDescription . As its name suggests, it collects system information. By running the code reconstructed from the malware, here is an actual example of the data collected by the backdoor and delivered to the attacker’s C2 with a separate backdoor command UploadSystemDescription : 1. %DOMAIN_NAME% 2. S-1-5-21-298510922-2159258926-905146427 3. DESKTOP-VL39FPO 4. UserName 5. [E] Microsoft Windows NT 6.2.9200.0 6.2.9200.0 64 6. C:\WINDOWS\system32 7. 0 8. %PROXY_SERVER% Description: Killer Wireless-n/a/ac 1535 Wireless Network Adapter #2 MACAddress: 9C:B6:D0:F6:FF:5D DHCPEnabled: True DHCPServer: 192.168.20.1 DNSHostName: DESKTOP-VL39FPO DNSDomainSuffixSearchOrder: Home DNSServerSearchOrder: 8.8.8.8, 192.168.20.1 IPAddress: 192.168.20.30, fe80::8412:d7a8:57b9:5886 IPSubnet: 255.255.255.0, 64 DefaultIPGateway: 192.168.20.1, fe80::1af1:45ff:feec:a8eb NOTE: Field #7 specifies the number of days (0) since the last system reboot. GetProcessByDescription command will build a list of processes running on a system. This command accepts an optional argument, which is one of the custom process properties enlisted here . If the optional argument is not specified, the backdoor builds a process list that looks like: [ 1720] svchost [ 8184] chrome [ 4732] svchost If the optional argument is specified, the backdoor builds a process list that includes the specified process property in addition to parent process ID, username and domain for the process owner. For example, if the optional argument is specified as “ ExecutablePath “, the GetProcessByDescription command may return a list similar to: [ 3656] sihost.exe C:\WINDOWS\system32\sihost.exe 1720 DESKTOP-VL39FPO\UserName [ 3824] svchost.exe C:\WINDOWS\system32\svchost.exe 992 DESKTOP-VL39FPO\UserName [ 9428] chrome.exe C:\Program Files (x86)\Google\Chrome\Application\chrome.exe 4600 DESKTOP-VL39FPO\UserName Other backdoor commands enable deployment of the 2nd stage malware. For example, the WriteFile command will save the file: using (FileStream fileStream = new FileStream(path, FileMode.Append, FileAccess.Write)) { fileStream.Write(array, 0, array.Length); } The downloaded 2nd stage malware can then the executed with RunTask command: using (Process process = new Process()) { process.StartInfo = new ProcessStartInfo(fileName, arguments) { CreateNoWindow = false, UseShellExecute = false }; if (process.Start()) … Alternatively, it can be configured to be executed with the system restart, using registry manipulation commands, such as SetRegistryValue . 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

Introduction Imagine your sensitive business data falling into the wrong hands. A data breach can be devastating, leading to financial... Cloud Security What Is Cloud Encryption? Your Key to Data Security Asher Benbenisty 2 min read Asher Benbenisty 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/16/24 Published Introduction Imagine your sensitive business data falling into the wrong hands. A data breach can be devastating, leading to financial losses, legal headaches, and irreparable damage to your reputation. Cloud encryption is your key to protecting your valuable data and ensuring peace of mind in the cloud. In this article, we'll explore cloud encryption and how AlgoSec can help you implement it effectively. We'll cover the basics of encryption, its benefits, the challenges you might face, and best practices to ensure your data stays safe. What Is Cloud Encryption? Cloud encryption is like creating a secret code for your data. It scrambles your information so that only authorized people with the key can read it. This process ensures that even if someone gains unauthorized access to your data, they won't be able to understand or use it. Cloud encryption is essential for protecting sensitive information like customer data, financial records, and intellectual property. It helps organizations meet compliance requirements, maintain data privacy, and safeguard their reputation. Encryption in Action: Protecting Data at Rest and in Transit Cloud encryption can be used to protect data in two states: Data at Rest: This refers to data that is stored in the cloud, such as in databases or storage buckets. Encryption ensures that even if someone gains access to the storage, they can't read the data without the encryption key. Data in Transit: This refers to data that is moving between locations, such as between your computer and a cloud server. Encryption protects the data while it travels over the internet, preventing eavesdropping and unauthorized access. How does it work? Cloud encryption uses algorithms to transform your data into an unreadable format. Think of it like this: Symmetric encryption: You and the recipient have the same key to lock (encrypt) and unlock (decrypt) the data. It's like using the same key for your front and back door. Asymmetric encryption: There are two keys: a public key to lock the data and a private key to unlock it. It's like having a mailbox with a slot for anyone to drop mail in (public key), but only you have the key to open the mailbox (private key). Why Encrypt Your Cloud Data? Cloud encryption offers a wide range of benefits: Compliance: Avoid costly fines and legal battles by meeting compliance requirements like GDPR, HIPAA, and PCI DSS. Data Protection: Safeguard your sensitive data, whether it's financial transactions, customer information, or intellectual property. Control and Ownership: Maintain control over your data and who can access it. Insider Threat Protection: Reduce the risk of data breaches caused by malicious or negligent employees. Multi-Tenancy Security: Enhance data security and isolation in shared cloud environments. Cloud Encryption Challenges (and How AlgoSec Helps) While cloud encryption is essential, it can be complex to manage. Here are some common challenges: Key Management: Securely managing encryption keys is crucial. Losing or mismanaging keys can lead to data loss. AlgoSec Solution: AlgoSec provides a centralized key management system to simplify and secure your encryption keys. Compliance: Meeting various regional and industry-specific regulations can be challenging. AlgoSec Solution: AlgoSec helps you navigate compliance requirements and implement appropriate encryption controls. Shared Responsibility: Understanding the shared responsibility model and your role in managing encryption can be complex. AlgoSec Solution: AlgoSec provides clear guidance and tools to help you fulfill your security responsibilities. Cloud Encryption Best Practices Encrypt Everything: Encrypt data both at rest and in transit. Choose Strong Algorithms: Use strong encryption algorithms like AES-256. Manage Keys Securely: Use a key management system (KMS) like the one provided by AlgoSec to automate and secure key management. Control Access: Implement strong access controls and identity management systems. Stay Compliant: Adhere to industry standards and regulations. Monitor and Audit: Regularly monitor your encryption implementation and conduct audits to ensure ongoing effectiveness. Conclusion Protecting your data in the cloud is non-negotiable. Cloud encryption is a fundamental security measure that every organization should implement. By understanding the benefits, challenges, and best practices of cloud encryption, you can make informed decisions to safeguard your sensitive information. Ready to protect your cloud data with encryption? AlgoSec helps businesses ensure data confidentiality and drastically lower the risk of cloud security incidents. Dive deeper into cloud security: Read our previous blog posts, Unveiling Cloud's Hidden Risks, A Secure VPC as the Main Pillar of Cloud Security, Azure Best Practices and Kubernetes Security Best Practices to uncover the top challenges and learn how to gain control of your cloud environment. These articles will equip you with the knowledge and tools to strengthen your cloud defenses. Subscribe to our blog to stay informed and join us on the journey to a safer and more resilient cloud future. Have a specific cloud security challenge? Contact us today for a free consultation. Want to learn more about how AlgoSec can help you secure your Kubernetes environment? Request a free demo today! 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

Every business needs to manage risks. If not, they won’t be around for long. The same is true in cloud computing. As more companies move their resources to the cloud, they must ensure efficient risk management to achieve resilience, availability, and integrity. Yes, moving to the cloud offers more advantages than on-premise environments. But, enterprises must remain meticulous because they have too much to lose. For example, they must protect sensitive customer data and business resources... Cloud Security Introduction to Cloud Risk Management for Enterprises 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 11/24/22 Published Every business needs to manage risks. If not, they won’t be around for long. The same is true in cloud computing. As more companies move their resources to the cloud, they must ensure efficient risk management to achieve resilience, availability, and integrity. Yes, moving to the cloud offers more advantages than on-premise environments. But, enterprises must remain meticulous because they have too much to lose. For example, they must protect sensitive customer data and business resources and meet cloud security compliance requirements. The key to these – and more – lies in cloud risk management. That’s why in this guide, we’ll cover everything you need to know about managing enterprise risk in cloud computing, the challenges you should expect, and the best ways to navigate it. If you stick around, we’ll also discuss the skills cloud architects need for risk management. What is Cloud Risk Management and Why is it Important? In cloud computing, risk management refers to the process of identifying, assessing, prioritizing, and mitigating the risks associated with cloud computing environments. It’s a process of being proactive rather than reactive. You want to identify and prevent an unexpected or dangerous event that can damage your systems before it happens. Most people will be familiar with Enterprise Risk Management (ERM). Organizations use ERM to prepare for and minimize risks to their finances, operations, and goals. The same concept applies to cloud computing. Cyber threats have grown so much in recent years that your organization is almost always a target. For example, a recent report revealed 80 percent of organizations experienced a cloud security incident in the past year. While cloud-based information systems have many security advantages, they may still be exposed to threats. Unfortunately, these threats are often catastrophic to your business operations. This is why risk management in cloud environments is critical. Through effective cloud risk management strategies, you can reduce the likelihood or impact of risks arising from cloud services. Types of Risks Managing risks is a shared responsibility between the cloud provider and the customer – you. While the provider ensures secure infrastructure, you need to secure your data and applications within that infrastructure. Some types of risks organizations face in cloud environments are: Data breaches are caused by unauthorized access to sensitive data and information stored in the cloud. Service disruptions caused by redundant servers can affect the availability of services to users. Non-compliance to regulatory requirements like CIS compliance , HIPAA, and GDPR. Insider threats like malicious insiders, cloud misconfigurations, and negligence. External threats like account hijacking and insecure APIs. But risk assessment and management aren’t always straightforward. You will face certain challenges – and we’ll discuss them below: Challenges Facing Enterprise Cloud Risk Management Most organizations often face difficulties when managing cloud or third-party/vendor risks. These risks are particularly associated with the challenges that cloud deployments and usage cause. Understanding the cloud security challenges sheds more light on your organization’s potential risks. The Complexity of Cloud Environments Cloud security is complex, particularly for enterprises. For example, many organisations leverage multi-cloud providers. They may also have hybrid environments by combining on-premise systems and private clouds with multiple public cloud providers. You’ll admit this poses more complexities, especially when managing configurations, security controls, and integrations across different platforms. Unfortunately, this means organizations leveraging the cloud will likely become dependent on cloud services. So, what happens when these services become unavailable? Your organisation may be unable to operate, or your customers can’t access your services. Thus, there’s a need to manage this continuity and lock-in risks. Lack of Visibility and Control Cloud consumers have limited visibility and control. First, moving resources to the public cloud means you’ll lose many controls you had on-premises. Cloud service providers don’t grant access to shared infrastructure. Plus, your traditional monitoring infrastructure may not work in the cloud. So, you can no longer deploy network taps or intrusion prevention systems (IPS) to monitor and filter traffic in real-time. And if you cannot directly access the data packets moving within the cloud or the information contained within them, you lack visibility or control. Lastly, cloud service providers may provide logs of cloud workloads. But this is far from the real deal. Alerts are never really enough. They’re not enough for investigations, identifying the root cause of an issue, and remediating it. Investigating, in this case, requires access to data packets, and cloud providers don’t give you that level of data. Compliance and Regulatory Requirements It can be quite challenging to comply with regulatory requirements. For instance, there are blind spots when traffic moves between public clouds or between public clouds and on-premises infrastructures. You can’t monitor and respond to threats like man-in-the-middle attacks. This means if you don’t always know where your data is, you risk violating compliance regulations. With laws like GDPR, CCPA, and other privacy regulations, managing cloud data security and privacy risks has never been more critical. Understanding Existing Systems and Processes Part of cloud risk management is understanding your existing systems and processes and how they work. Understanding the requirements is essential for any service migration, whether it is to the cloud or not. This must be taken into consideration when evaluating the risk of cloud services. How can you evaluate a cloud service for requirements you don’t know? Evolving Risks Organizations struggle to have efficient cloud risk management during deployment and usage because of evolving risks. Organizations often develop extensive risk assessment questionnaires based on audit checklists, only to discover that the results are virtually impossible to assess. While checklists might be useful in your risk assessment process, you shouldn’t rely on them. Pillars of Effective Cloud Risk Management – Actionable Processes Here’s how efficient risk management in cloud environments looks like: Risk Assessment and Analysis The first stage of every risk management – whether in cloud computing or financial settings – is identifying the potential risks. You want to answer questions like, what types of risks do we face? For example, are they data breaches? Unauthorized access to sensitive data? Or are they service disruptions in the cloud? The next step is analysis. Here, you evaluate the likelihood of the risk happening and the impact it can have on your organization. This lets you prioritize risks and know which ones have the most impact. For instance, what consequences will a data breach have on the confidentiality and integrity of the information stored in the cloud? Security Controls and Safeguards to Mitigate Risks Once risks are identified, it’s time to implement the right risk mitigation strategies and controls. The cloud provider will typically offer security controls you can select or configure. However, you can consider alternative or additional security measures that meet your specific needs. Some security controls and mitigation strategies that you can implement include: Encrypting data at rest and in transit to protect it from unauthorized access. For example, you could encrypt algorithms and implement secure key management practices that protect the information in the cloud while it’s being transmitted. Implementing accessing control and authentication measures like multi-factor authentication (MFA), role-based access control (RBAC), and privileged access management (PAM). These mechanisms ensure that only authorized users can access resources and data stored in the cloud. Network security and segmentation: Measures like firewalls, intrusion detection/intrusion prevention systems (IDS/IPS), and virtual private networks (VPN) will help secure network communications and detect/prevent malicious actors. On the other hand, network segmentation mechanisms help you set strict rules on the services permitted between accessible zones or isolated segments. Regulatory Compliance and Data Governance Due to the frequency and complexity of cyber threats, authorities in various industries are releasing and updating recommendations for cloud computing. These requirements outline best practices that companies must adhere to avoid and respond to cyber-attacks. This makes regulatory compliance an essential part of identifying and mitigating risks. It’s important to first understand the relevant regulations, such as PCI DSS, ISO 27001, GDPR, CCPA, and HIPAA. Then, understand each one’s requirements. For example, what are your obligations for security controls, breach notifications, and data privacy? Part of ensuring regulatory compliance in your cloud risk management effort is assessing the cloud provider’s capabilities. Do they meet the industry compliance requirements? What are their previous security records? Have you assessed their compliance documentation, audit reports, and data protection practices? Lastly, it’s important to implement data governance policies that prescribe how data is stored, handled, classified, accessed, and protected in the cloud. Continuous Monitoring and Threat Intelligence Cloud risks are constantly evolving. This could be due to technological advancements, revised compliance regulations and frameworks, new cyber-treats, insider threats like misconfigurations, and expanding cloud service models like Infrastructure-as-a-Service (IaaS). What does this mean for cloud computing customers like you? There’s an urgent need to conduct regular security monitoring and threat intelligence to address emerging risks proactively. It has to be an ongoing process of performing vulnerability scans of your cloud infrastructure. This includes log management, periodic security assessments, patch management, user activity monitoring, and regular penetration testing exercises. Incident Response and Business Continuity Ultimately, there’s still a chance your organization will face cyber incidents. Part of cloud risk management is implementing cyber incident response plans (CIRP) that help contain threats. Whether these incidents are low-level risks that were not prioritized or high-impact risks you missed, an incident response plan will ensure business continuity. It’s also important to gather evidence through digital forensics and analyze system artifacts after incidents. Backup and Recovery Implementing data backup and disaster recovery into your risk management ensures you minimize the impact of data loss or service disruptions. For example, backing up data and systems regularly is important. Some cloud services may offer redundant storage and versioning features, which can be valuable when your data is corrupted or accidentally deleted. Additionally, it’s necessary to document backup and recovery procedures to ensure consistency and guide architects. Best Practices for Effective Cloud Risk Management Achieving cloud risk management involves combining the risk management processes above, setting internal controls, and corporate governance. Here are some best practices for effective cloud risk management: 1. Careful Selection of Your Cloud Service Provider (CSP) Carefully select a reliable cloud service provider (CSP). You can do this by evaluating factors like contract clarity, ethics, legal liability, viability, security, compliance, availability, and business resilience. Note that it’s important to assess if the CSP relies on other service providers and adjust accordingly. 2. Establishing a Cloud Risk Management Framework Consider implementing cloud risk management frameworks for a structured approach to identifying, assessing, and mitigating risks. Some notable frameworks include: National Institute of Standards and Technology (NIST) Cloud Computing Risk Management Framework (CC RMF) ISO/IEC 27017 Cloud Security Alliance (CSA) Cloud Controls Matrix (CCM) Cloud Audit and Compliance (CAC) Criteria Center for Internet Security (CIS) Controls for Cloud, etc. 3. Collaboration and Communication with Stakeholders You should always inform all stakeholders about potential risks, their impact, and incident response plans. A collaborative effort can improve risk assessment and awareness, help your organization leverage collective expertise, and facilitates effective decision-making against identified risks. 4. Implement Technical Safeguards Deploying technical safeguards like cloud access security broker (CASB) in cloud environments can enhance security and protect against risks. CASB can be implemented in the cloud or on-premise and enforces security policies for users accessing cloud-based resources. 5. Set Controls Based on Risk Treatment After identifying risks and determining your risk appetite, it’s important to implement dedicated measures to mitigate them. Develop robust data classification and lifecycle mechanisms and integrate processes that outline data protection, erasure, and hosting into your service-level agreements (SLA). 6. Employee Training and Awareness Programs What’s cloud risk management without training personnel? At the crux of risk management is identifying potential threats and taking steps to prevent them. Insider threats and the human factor contribute significantly to threats today. So, training employees on what to do to prevent risks during and after incidents can make a difference. 7. Adopt an Optimized Cloud Service Model Choose a cloud service model that suits your business, minimizes risks, and optimizes your cloud investment cost. 8. Continuous Improvement and Adaptation to Emerging Threats As a rule of thumb, you should always look to stay ahead of the curve. Conduct regular security assessments and audits to improve cloud security posture and adapt to emerging threats. Skills Needed for Cloud Architects in Risk Management Implementing effective cloud risk management requires having skilled architects on board. Through their in-depth understanding of cloud platforms, services, and technologies, these professionals can help organizations navigate complex cloud environments and design appropriate risk mitigation strategies. Cloud Security Expertise: This involves an understanding of cloud-specific security challenges and a solid knowledge of the cloud provider’s security capabilities. Risk Assessment and Management Skills: Cloud architects must be proficient in risk assessment processes, methodologies, and frameworks. It is also essential to prioritize risks based on their perceived impact and implement appropriate controls. Compliance and Regulatory Knowledge: Not complying with regulatory requirements may cause similar damage as poor risk management. Due to significant legal fees or fines, cloud architects must understand relevant industry regulations and compliance standards. They must also incorporate these requirements into the company’s risk management strategies. Incident Response and Incident Handling: Risk management aims to reduce the likelihood of incidents or their impact. It doesn’t mean completely eradicating incidents. So, when these incidents eventually happen, you want cloud security architects who can respond adequately and implement best practices in cloud environments. Conclusion The importance of prioritizing risk management in cloud environments cannot be overstated. It allows you to proactively identify risks, assess, prioritize, and mitigate them. This enhances the reliability and resilience of your cloud systems, promotes business continuity, optimizes resource utilization, and helps you manage compliance. Do you want to automate your cloud risk assessment and management? Horizon ACE is the ideal option for identifying risks and achieving security compliance. Request a demo now to see how Horizon ACE’s agentless platform can protect your valuable assets and streamline your multi-cloud environments. 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

Top 5 misconfigurations to avoid for robust security Multi-cloud environments have become the backbone of modern enterprise IT, offering unparalleled flexibility, scalability, and access to a diverse array of innovative services. This distributed architecture empowers organizations to avoid vendor lock-in, optimize costs, and leverage specialized functionalities from different providers. However, this very strength introduces a significant challenge: increased complexity in security... Cloud Security 5 Multi-Cloud Environments Iris Stein 2 min read Iris Stein 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 6/23/25 Published Top 5 misconfigurations to avoid for robust security Multi-cloud environments have become the backbone of modern enterprise IT, offering unparalleled flexibility, scalability, and access to a diverse array of innovative services. This distributed architecture empowers organizations to avoid vendor lock-in, optimize costs, and leverage specialized functionalities from different providers. However, this very strength introduces a significant challenge: increased complexity in security management. The diverse security models, APIs, and configuration nuances of each cloud provider, when combined, create a fertile ground for misconfigurations. A single oversight can cascade into severe security vulnerabilities, lead to compliance violations, and even result in costly downtime and reputational damage. At AlgoSec, we have extensive experience in navigating the intricacies of multi-cloud security. Our observations reveal recurring patterns of misconfigurations that undermine even the most well-intentioned security strategies. To help you fortify your multi-cloud defences, we've compiled the top five multi-cloud misconfigurations that organizations absolutely must avoid. 1. Over-permissive policies: The gateway to unauthorized access One of the most pervasive and dangerous misconfigurations is the granting of overly broad or permissive access policies. In the rush to deploy applications or enable collaboration, it's common for organizations to assign excessive permissions to users, services, or applications. This "everyone can do everything" approach creates a vast attack surface, making it alarmingly easy for unauthorized individuals or compromised credentials to gain access to sensitive resources across your various cloud environments. The principle of least privilege (PoLP) is paramount here. Every user, application, and service should only be granted the minimum necessary permissions to perform its intended function. This includes granular control over network access, data manipulation, and resource management. Regularly review and audit your Identity and Access Management (IAM) policies across all your cloud providers. Tools that offer centralized visibility into entitlements and highlight deviations can be invaluable in identifying and rectifying these critical vulnerabilities before they are exploited. 2. Inadequate network segmentation: Lateral movement made easy In a multi-cloud environment, a flat network architecture is an open invitation for attackers. Without proper network segmentation, a breach in one part of your cloud infrastructure can easily lead to lateral movement across your entire environment. Mixing production, development, and sensitive data workloads within the same network segment significantly increases the risk of an attacker pivoting from a less secure development environment to a critical production database. Effective network segmentation involves logically isolating different environments, applications, and data sets. This can be achieved through Virtual Private Clouds (VPCs), subnets, security groups, network access control lists (NACLs), and micro-segmentation techniques. The goal is to create granular perimeters around critical assets, limiting the blast radius of any potential breach. By restricting traffic flows between different segments and enforcing strict ingress and egress rules, you can significantly hinder an attacker's ability to move freely within your cloud estate. 3. Unsecured storage buckets: A goldmine for data breaches Cloud storage services, such as Amazon S3, Azure Blob Storage, and Google Cloud Storage, offer incredible scalability and accessibility. However, their misconfiguration remains a leading cause of data breaches. Publicly accessible storage buckets, often configured inadvertently, expose vast amounts of sensitive data to the internet. This includes customer information, proprietary code, intellectual property, and even internal credentials. It is imperative to always double-check and regularly audit the access controls and encryption settings of all your storage buckets across every cloud provider. Implement strong bucket policies, restrict public access by default, and enforce encryption at rest and in transit. Consider using multifactor authentication for access to storage, and leverage tools that continuously monitor for publicly exposed buckets and alert you to any misconfigurations. Regular data classification and tagging can also help in identifying and prioritizing the protection of highly sensitive data stored in the cloud. 4. Lack of centralized visibility: Flying blind in a complex landscape Managing security in a multi-cloud environment without a unified, centralized view of your security posture is akin to flying blind. The disparate dashboards, logs, and security tools provided by individual cloud providers make it incredibly challenging to gain a holistic understanding of your security landscape. This fragmented visibility makes it nearly impossible to identify widespread misconfigurations, enforce consistent security policies across different clouds, and respond effectively and swiftly to emerging threats. A centralized security management platform is crucial for multi-cloud environments. Such a platform should provide comprehensive discovery of all your cloud assets, enable continuous risk assessment, and offer unified policy management across your entire multi-cloud estate. This centralized view allows security teams to identify inconsistencies, track changes, and ensure that security policies are applied uniformly, regardless of the underlying cloud provider. Without this overarching perspective, organizations are perpetually playing catch-up, reacting to incidents rather than proactively preventing them. 5. Neglecting Shadow IT: The unseen security gaps Shadow IT refers to unsanctioned cloud deployments, applications, or services that are used within an organization without the knowledge or approval of the IT or security departments. While seemingly innocuous, shadow IT can introduce significant and often unmanaged security gaps. These unauthorized resources often lack proper security configurations, patching, and monitoring, making them easy targets for attackers. To mitigate the risks of shadow IT, organizations need robust discovery mechanisms that can identify all cloud resources, whether sanctioned or not. Once discovered, these resources must be brought under proper security governance, including regular monitoring, configuration management, and adherence to organizational security policies. Implementing cloud access security brokers (CASBs) and network traffic analysis tools can help in identifying and gaining control over shadow IT instances. Educating employees about the risks of unauthorized cloud usage is also a vital step in fostering a more secure multi-cloud environment. Proactive management with AlgoSec Cloud Enterprise Navigating the complex and ever-evolving multi-cloud landscape demands more than just awareness of these pitfalls; it requires deep visibility and proactive management. This is precisely where AlgoSec Cloud Enterprise excels. Our solution provides comprehensive discovery of all your cloud assets across various providers, offering a unified view of your entire multi-cloud estate. It enables continuous risk assessment by identifying misconfigurations, policy violations, and potential vulnerabilities. Furthermore, AlgoSec Cloud Enterprise empowers automated policy enforcement, ensuring consistent security postures and helping you eliminate misconfigurations before they can be exploited. By providing this robust framework for security management, AlgoSec helps organizations maintain a strong and resilient security posture in their multi-cloud journey. Stay secure out there! The multi-cloud journey offers immense opportunities, but only with diligent attention to security and proactive management can you truly unlock its full potential while safeguarding your critical assets. 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

Securely accelerate application delivery by automating application connectivity and security policy across the hybrid network estate Secure application connectivity.
Anywhere. Automatisieren Sie die Security-Richtlinien in Ihrem hybriden Netzwerk, damit Ihre Applikationen stets die erforderliche Konnektivität aufweisen und Sie schnell und sicher agieren können. Schedule a demo Watch a video Schaffen Sie Transparenz Entdecken, identifizieren und erfassen Sie alle Netzwerkverbindungen und Datenströme Ihrer Business-Applikationen und korrelieren Sie diese mit den Security-Richtlinien Policy Management unter Einhaltung von Compliance-Vorgaben Automatically associate the relevant business applications that each firewall rule supports, enabling you to review the firewall rules quickly and easily. Automatisieren Sie Änderungen - Sicher Vermeiden Sie Fehlkonfigurationen, indem Sie Änderungen für die Konnektivität Ihrer Applikationen und deren Security-Richtlinien automatisieren – von der Planung über die Risikoanalyse bis hin zur Implementierung und Validierung Übernehmen Sie die Kontrolle über Ihre Applikationen und Security-Richtlinien Schnelle, sichere Bereitstellung von Applikationen und effiziente Verwaltung von Security-Richtlinien für Public Clouds, Private Clouds, Container und On-Premises-Netzwerke Mehr als 1.800 Unternehmen vertrauen auf AlgoSec – seit dem Jahr 2004 Vereinbaren Sie Ihren persönlichen Demo-Termin Sichere Konnektivität für alle Business-Applikationen AlgoSec führt Ihre IT-Infrastruktur, Ihre Security-Richtlinien und Ihre Applikationen, die die Grundlage für Ihren Geschäftserfolg bilden, zusammen. So können Sie Veränderungen in Ihrem Unternehmen voranbringen und die Bereitstellung von Applikationen beschleunigen Cloud/SDN ITSM Network & Security DevOps / Automation SIEM/SOAR Micro-segmentation Vulnerability scanners Chat solutions Watch the video "Placeholder Text" What they say about us Placeholder Name Send Michael West Reece Secure application connectivity 
across your entire application fabric Heading 5 Send Michael West Reece Secure application connectivity 
across your entire application fabric Heading 5 Read the eBook Migrieren Sie die Konnektivität Ihrer Applikationen in die Cloud Profitieren Sie von Experten-Know-how
Gewinnen Sie neue Einblicke 6 Best Practices für mehr Sicherheit in hybriden Cloud-Umgebungen Nutzen Sie unser eBook Verwalten Sie die Konnektivität Ihres Netzwerks bei Fusionen und Lesen Sie unseren Blog Wirtschaftliche Faktoren für die Auswahl von NSPM-Lösungen Profitieren Sie von unserem Whitepaper Der ultimative Leitfaden für hybrides Netzwerk-Management Nutzen Sie unser eBook Schedule time with one of our experts

In today’s evolving threat landscape, Zero Trust Architecture has emerged as a significant security framework for organizations. One... Zero Trust Zero Trust Design Nitin Rajput 2 min read Nitin Rajput 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 5/18/24 Published In today’s evolving threat landscape, Zero Trust Architecture has emerged as a significant security framework for organizations. One influential model in this space is the Zero Trust Model, attributed to John Kinderbag. Inspired by Kinderbag’s model, we explore how our advanced solution can effectively align with the principles of Zero Trust. Let’s dive into the key points of mapping the Zero Trust Model with AlgoSec’s solution, enabling organizations to strengthen their security posture and embrace the Zero Trust paradigm. My approach of mapping Zero Trust Model with AlgoSec solution is based on John Kinderbag’s Zero Trust model ( details ) which being widely followed, and I hope it will help organizations in building their Zero trust strategy. Firstly, let’s understand what Zero trust is all about in a simple language. Zero Trust is a Cybersecurity approach that articulates that the fundamental problem we have is a broken trust model where the untrusted side of the network is the evil internet, and the trusted side is the stuff we control. Therefore, it is an approach to designing and implementing a security program based on the notion that no user or device or agent should have implicit trust. Instead, anyone or anything, a device or system that seeks access to corporate assets must prove it should be trusted. The primary goal of Zero Trust is to prevent breaches. Prevention is possible. In fact, it’s more cost effective from a business perspective to prevent a breach than it is to attempt to recover from a breach, pay a ransom, and the deal with the costs of downtime or lost customers. As per John Kinderbag, there are Four Zero Trust Design Principles and Five-Step Zero Trust Design Methodology. The Four Zero Trust Design Principles: The first and the most important principle of your Zero Trust strategy is know “What is the Business trying to achieve?”. Second, start with DAAS (Data, Application, Asset and Services) elements and protect surfaces that need protection and design outward from there. Third, determine who needs to have access to a resource in order to get their job done, commonly known as least privilege. Fourth, all the traffic going to and from a protect surface must be inspected and logged for malicious content. Define Business Outcomes Design from the inside out Determine who or what needs access Inspect and log all traffic The Five-Step Zero Trust Design Methodology To make your Zero trust journey achievable, you need a repeatable process to follow. The first step in the Zero trust is to break down your environment into smaller pieces that you need to protect (protect surfaces). The second step for deploying Zero Trust in each protect surfaces is to map the transactions flows so that we can allow only the ports and the address needed and nothing else. Everyone wants to know what products to buy to do Zero trust or to eliminate trust between digital systems, the truth is that you won’t know the answer to that until you’ve gone through the process. Which brings us to the third step in the methodology: architecting the Zero trust environment. Ultimately, we need to instantiate Zero Trust as a Layer 7 policy statement. Use the Kipling Method of Zero Trust policy writing to determine who or what can access your protect surface. The fifth design principle of Zero Trust is to inspect and log all traffic, for monitor and maintain, one needs to take all of the telemetry – whether it’s from a network detection and response tool, or from firewall or server application logs and then learn from them. As you learn over time, you can make security stronger and stronger. Define the protect surface Map the transaction flows Architect a Zero trust environment Create Zero trust policies Monitor and maintain. How AlgoSec aligns with “Map the transaction Flows” the 2nd step of Design Methodology? AlgoSec Auto-Discovery. analyses your traffic flows, turning them into a clear map. AutoDiscovery receives network traffic metadata as NetFlow, SFLOW, or full packets and then digest multiple streams of traffic metadata to let you clearly visualize your transaction flows. Once the transaction flows are discovered and optimized, the system keeps tracking changes in these flows. Once new flows are discovered in the network, the application description is updated with the new flows. Outcome: Clear visualization of transaction flows. Updated application description. Optimized transaction flows. How AlgoSec aligns with “Architect Zero Trust Policies” – the 4th step of Design Methodology? With AlgoSec, you can automate the security policy change process without introducing any element of risk, vulnerability, or compliance violation. AlgoSec allows you to ingest the discovered transaction flows as a Traffic Change request and analyze those traffic changes before they are implemented all the to your Firewalls, Public Cloud and SDN Solutions and validate successful changes as intended, all within your existing IT Service Management (ITSM) solutions. Outcome: Analyzed traffic changes for implementation. Implemented security policy changes without risk, vulnerability, or compliance violations. How Algosec aligns with “Monitor and maintain” – the 5th step of Design Methodology? AlgoSec analyzes security by analyzing firewall policies, firewall rules, firewall traffic logs and firewall change configurations. Detailed analysis of the security logs offers critical network vital intelligence about security breaches and attempted attacks like virus, trojans, and denial of service among others. With AlgoSec traffic flow analysis, you can monitor traffic within a specific firewall rule. You do not need to allow all traffic to traverse in all directions but instead, you can monitor it through the pragmatic behaviors on the network and enable network firewall administrators to recognize which firewall rules they can create and implement to allow only the necessary access. Outcome: Critical network intelligence, identification of security breaches and attempted attacks. Enhanced firewall rule creation and implementation, allowing only necessary access. Schedule a demo Related Articles 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

Streamlining PCI DSS Compliance and Accelerating E-commerce for a Leading Retailer Case Study 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