Search results

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

Learn how automation can simplify the process of rule recertification and help determine which rules are still necessary Webinars Play by the rules: Automation for simplified rule recertification As time goes by, once effective firewall rules can become outdated. This results in bloated security policies which can slow down application delivery. Therefore, best practice and compliance requirements calls for rule recertification at least once per year. While rule recertification can be done manually by going through the comments fields of every rule, this is a tedious process which is also subject to the weaknesses of human error. Automation can simplify the process and help determine which rules are still necessary, if done right. Join security experts Asher Benbenisty and Tsippi Dach to learn about: Rule recertification as part of application delivery pipeline The importance of recertifying rules regularly Methods used for rule recertification The business application approach for rule recertification October 27, 2021 Tsippi Dach Director of marketing communications Asher Benbenisty Director of product marketing Relevant resources AlgoSec Horizon AppViz – Rule Recertification Watch Video Changing the rules without risk: mapping firewall rules to business applications 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

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

Learn which cloud security services to consider first, how to prioritize them, and how to govern cloud access, policy changes, and audit evidence Best practices for securing a cloud network ---- ------- Schedule a Demo Select a size ----- Get the latest insights from the experts Choose a better way to manage your network

Safeguarding the network architecture is the need of the hour. According to a study, the average cost of a data breach is at an all-time... Network Security Policy Management Network segmentation vs. VLAN explained 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 8/9/23 Published Safeguarding the network architecture is the need of the hour. According to a study, the average cost of a data breach is at an all-time high of $4.35 million. And this figure will only increase with governments and regulators becoming ever stricter on data breaches. The go-to method IT administrators adopt to safeguard their networks is network segmentation. By segmenting a larger network into smaller chunks, it becomes much more manageable to secure the entire network. But network segmentation is a broad concept and doesn’t refer to a single procedure. In fact, there are several segmentation processes — one of them being VLAN. Instead of simplifying, this adds to the complexity. In this article, we will explain the core difference between network segmentation and VLAN and when you should opt for a particular one over the other. What is network segmentation? Let’s start with the definitions of network segmentation and VLAN. By definition, network segmentation is the practice of compartmentalizing a network according to firewall rules . In other words, it’s about dividing a computer network into subnetworks. The subnetworks, at the IP level, are known as subnets. Each of the subnets then works independently and in isolation. Think of how a nation is split into various states and provinces for better management at the local level. Running an entire nation at the federal level is too much work. In addition to subnetting, there are other segmentation options like firewall segmentation and SDN (Software Defined Network) segmentation. But for this article’s sake, we will focus on subnets since those are the most common. What is VLAN? VLAN or Virtual LAN (Virtual Local Area Network) is also a type of network segmentation approach where the main physical network is divided into multiple smaller virtual networks. The division is done logically or virtually, not requiring buying additional physical resources. The same resource is divided using computer logic. There are several benefits to dividing the parts of the network, either using VLAN segmentation or subnet techniques. Some of them are: Broadcast domain isolation Both subnets and VLAN isolate broadcast domains. This way, broadcasting network traffic is contained in a single segment instead of being exposed to the entire network. This reduces the chance of network congestion during peak hours and unnecessary server overload, thereby maximizing efficiency. Enhanced security The isolation by subnets or VLAN enhances the IT network’s security policies. This is achieved through various factors that are at play. But primarily, the creation of subnetworks makes the flat network more secure. With multiple subnetworks, you can regulate the security parameters. Thus, those subnets containing critical data (like that of healthcare) can have enhanced cybersecurity measures more than others, making them harder to crack. So, from a security perspective, both subnets and VLAN are a must. Better network management With digitization and IT modernization, the IT infrastructure is growing. Concurrently, it’s getting harder to manage them. Microsegmentation is one way of managing the ever-growing infrastructure. By segmenting, you can deploy teams to each segment, thereby strengthening their management and accountability. With the implementation of SDN, you can even configure and automate the management of some of the subnetworks. Flexibility in scalability Many network administrators face network performance and scalability issues expanding resources. The issues are a mix of technical and economical. Network segmentation offers a solution to such issues. By segmenting the entire data center network, you can choose which segments to expand and control the resources granted to each segment. This also makes scalability more economical. While both offer scalability opportunities, VLAN offers superior functionality than subnets. Reduced scope of compliance Compliance is another area that IT execs need to work on. And network segmentation, either via subnets or VLAN, can help in this regard. By having subnets, you don’t have to audit your entire segmented network as required by regulators. Just audit the necessary subnets and submit the reports to the regulators for approval. This takes far less time and costs significantly less than auditing the entire network. Differences between network segmentation and VLAN By definition, network segmentation (subnetting) and VLAN sound pretty similar. After all, there’s a division of the main network into subnetworks or smaller networks. But besides the core similarities mentioned above, there are a few critical differences. Let’s dive into the differences between the two. The primary difference between the two subnets are layer 3 divisions, while VLANs are layer 2 divisions. As you may recall, networks are layer 1 (device), layer 2 (data link), layer 3 (IP, routers), and so on, up to layer 7 (application). TCP/IP is the newer framework with four layers only. So, when you divide a network at a data link, you need to adopt VLAN. With VLAN, several networks exist on the same physical network but may not be connected to the same fiber switch. In subnets, the division occurs at IP level. Thus, the independent subnets are assigned their IP addresses and communicate with others over layer 3. Besides this significant difference, there are other dissimilarities you should know. Here’s a table to help you understand: VLAN Subnet 1 Divides the network within the same physical network using logic. Divides the IP network into multiple IP networks 2 VLANs communicate with other devices within the same LAN The communication between the subnets is carried out over layer 3 3 It is configured at the switch side It is configured at IP level 4 VLAN divisions are software-based terminology since they’re divided logically. Subnets can be both hardware- of software-based 5 VLAN provides better network access and tend to be more stable Subnets offer limited control When to adopt a subnet? There are use cases when subnets are more suited, while there are cases when you’re better off with Virtual LANs. As per the definition, you need to adopt a subnet when dividing different networks at IP level. So, if you want to create multiple IP addresses for each partition, implement subnets. The subnets are essentially networks within a network with their own IP addresses. Thus, they divide the broadcast domain and improve speed and efficiency. Subnets are also the go-to segmentation method when you need to make the sub-networks available over layer 3 to the outside world. With appropriate access control lists, anyone with an internet connection would be able to access the subnets But subnetting is also used to prevent access to a particular subnet. For example, you may want to limit access to the company’s software codebase to anyone outside the development department. So, only network devices with approved IP addresses used by the developer network are approved to access the codebase. But there are two downsides to subnets you should know. The first one is increased time complexity. When dealing with a single network, three steps are in place to reach the Process (Source Host, Destination Network, and Process). In subnets, there’s an additional step involved (Source Host, Destination Network, Subnet, Process). This extra step increases time complexity, requiring more time for data transfer and connectivity. It also affects stability. Subnetting also increases the number of IP addresses required since each subnet requires its own IP address. This can become hard to manage over time. When to adopt VLAN? Virtual LANs are internal networks within the same physical network. They interact with one another, not with other devices on the same network or outside the world. Think of VLAN as a private wireless network at home. Your neighbors don’t have access to it, but everyone in your home has. If that sounds like your desired result, you should adopt VLAN. There are three types of VLANs (basic, extended, and tagged). In basic VLAN, you assign IDs to each switch port or PCI . Once assigned, you can’t change them. Extended VLAN has more functionalities like priority-based routing. Lastly, tagged VLAN enables you to create multiple VLANs with IEEE 802.1Q. The main advantages of different VLANs over subnet are speed and stability. Since endpoints do not have to resolve IP addresses every time, they tend to be faster. But there’s a significant disadvantage to VLANs: It’s easier to breach multiple partitions if there’s a malicious injection. Without proper network security controls, it is easier to exploit vulnerabilities using malware and ransomware , putting your entire network at risk. Having ACLs (access control lists) can help in such situations. Furthermore, there are issues arising out of physical store requirements. Connecting two segments in VLAN requires you to use routers and IoT. Routers are physical devices that take up space. The more segments you create, the more routers you need to use. Over time, management can become an issue. The bottom line Both subnets and VLANs are network segmentation approaches that improve security and workload management. It’s not a given that you can’t have both. Some companies benefit from the implementation of VLAN and subnets simultaneously. But there are specific times when IT service providers prefer one over the other. Consider your requirements to select the approach that’s right for you. 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

Learn hybrid cloud security policy management best practices for governing firewalls, cloud controls, application access, and audit-ready changes Hybrid cloud security policy management: Best practices for enterprise teams ---- ------- Schedule a Demo Select a size ----- Get the latest insights from the experts Choose a better way to manage your network

The new alliance is designed to meet the growing needs of AlgoSec’s partners and customers to maintain their competitiveness by delivering enhanced services AlgoSec Teams with TD SYNNEX to Take Partner and Customer Service to New Heights The new alliance is designed to meet the growing needs of AlgoSec’s partners and customers to maintain their competitiveness by delivering enhanced services October 2, 2022 Speak to one of our experts RIDGEFIELD PARK, N.J., October 3, 2022 – AlgoSec, a global cybersecurity leader in securing application connectivity, has announced its new alliance with TD SYNNEX, a leading global distributor and solutions aggregator for the IT ecosystem. This partnership will enable AlgoSec’s partners to leverage a whole host of customer-centric resources. These include extended partner support and key customer touchpoint services through TD SYNNEX’s expansive distribution channels. AlgoSec partners working through TD SYNNEX Security Solutions will benefit from: Expedited SLAs on all AlgoSec quotes and orders within less than one business day Quarter-end extended hours Access to a dedicated AlgoSec Product Manager from SYNNEX AlgoSec Partners will still have AlgoSec Channel Managers. In addition, AlgoSec customers will enjoy an enhanced service offering, including: Hands-on cybersecurity expertise through TD SYNNEX Cyber Range Dedicated security focused team Pre-sales engineering support Vulnerability assessments, Bill of Materials (BoM), design Proof of Concept (PoC) “We are excited to add AlgoSec to our portfolio of products. Securing applications and managing policy management across hybrid networks is a major challenge for IT teams.” said Scott Young, Sr. Vice President, Strategic Procurement, TD SYNNEX. Jim Fairweather, AlgoSec VP Channels adds “I am fully confident that our partnership with TD SYNNEX will enable our channel partners to accelerate time to market and improve overall support to meet customer demands”. About AlgoSec  AlgoSec, a global cybersecurity leader, empowers organizations to secure application connectivity by automating connectivity flows and security policy, anywhere.  The AlgoSec platform enables the world’s most complex organizations to gain visibility, reduce risk and process changes at zero-touch across the hybrid network.   AlgoSec’s patented application-centric view of the hybrid network enables business owners, application owners, and information security professionals to talk the same language, so organizations can deliver business applications faster while achieving a heightened security posture.  Over 1,800 of the world’s leading organizations trust AlgoSec to help secure their most critical workloads across public cloud, private cloud, containers, and on-premises networks, while taking advantage of almost two decades of leadership in Network Security Policy Management.  See what securely accelerating your digital transformation, move-to-cloud, infrastructure modernization, or micro-segmentation initiatives looks like at www.algosec.com About TD SYNNEX TD SYNNEX (NYSE: SNX) is a leading global distributor and solutions aggregator for the IT ecosystem. We’re an innovative partner helping more than 150,000 customers in 100+ countries to maximize the value of technology investments, demonstrate business outcomes and unlock growth opportunities. Headquartered in Clearwater, Florida, and Fremont, California, TD SYNNEX’ 22,000 co-workers are dedicated to uniting compelling IT products, services and solutions from 1,500+ best-in-class technology vendors. Our edge-to-cloud portfolio is anchored in some of the highest-growth technology segments including cloud, cybersecurity, big data/analytics, IoT, mobility and everything as a service. TD SYNNEX is committed to serving customers and communities, and we believe we can have a positive impact on our people and our planet, intentionally acting as a respected corporate citizen. We aspire to be a diverse and inclusive employer of choice for talent across the IT ecosystem. For more information, visit www.TDSYNNEX.com or follow us on Twitter , LinkedIn , Facebook and Instagram .

Ensure your firewall meets all PCI DSS requirements. Learn essential best practices for configuring and managing your firewall for optimal PCI compliance. Firewall PCI DSS compliance: Requirements & best practices What is a firewall PCI DSS compliance? PCI DSS compliance refers to a set of security measures that apply to businesses handling payment cards, e.g., credit cards, debit cards, and cash cards. The full meaning of the term PCI DSS is Payment Card Industry Data Security Standard. All companies that accept, process, store, or transmit credit card information require PCI Compliance as it ensures data security during and outside financial transactions. PCI DSS compliance is the rules and policies companies processing, storing, or transmitting payment card information must adhere to, helping them build a secure environment for card data. The PCI security standards council (PCI SSC) is the body responsible for managing PCI DSS. PCI SSC was formed in 2006 and has since been providing policies that tackle evolving cyber threats in the payment card industry. A firewall PCI DSS compliance refers to the process of configuring a firewall to monitor and filter incoming and outgoing internet traffic based on PCI DSS policies. Firewalls function based on a set of security rules, enabling them to block bad traffic like viruses and hackers from penetrating your network. Establishing a PCI-compliant firewall gives companies robust payment card information security that meets business needs and effectively protects sensitive data. Schedule a Demo What are the benefits of a PCI-compliant firewall? Hackers see credit cards and other payment card types as money-making opportunities. They tirelessly attack systems and networks to extract cardholders’ personal information and sensitive authentication data, which they can exploit. Examples of cardholder data are: Primary Account Number (PAN) Cardholder name Expiration date Service code Sensitive authentication data include: Full track data (magnetic-stripe data or equivalent on a chip) CAV2/CVC2/CVV2/CID PINs/PIN blocks Becoming PCI-compliant means you have effective security solutions to help defend your network against attacks and protect the financial and personal data of payment cards. A PCI-compliant firewall has been configured following PCI policies to allow specific network traffic and block others from accessing card data. Some benefits of having a PCI-compliant firewall in your organization include: Builds customer trust Any business that stores, processes, accepts, or transmits credit card information must have a reliable cybersecurity solution to gain customers’ trust. Users want reassurance that their data is safely stored and transmitted in your organization’s network, backed by the strictest information security policy. By showing that your business meets international standards for card information security, you can easily build customer trust and increase patronage. Prevents data breaches The primary benefit of PCI DSS compliance is that it eliminates the risks of data breaches. Data breaches can lead to huge financial losses and even damage a company’s reputation. Often, hackers look for easy targets, and one quick way to find them is by checking for companies whose firewall configuration isn’t PCI-compliant. Being PCI-compliant shows any potential attacker that your network security is top-notch, thus discouraging them from taking any further action. It displays that your cardholder data environment is protected by formidable security solutions that meet industry regulations and best practices. Helps you to meet global standards PCI DSS compliance was put together by the PCI Security Standards Council (PCI SSC). The body was formed by Visa, MasterCard, Discover, American Express, and JCB– the top five payment card firms. They designed this payment card information security policy to prevent data breaches and protect network system components, including servers, firewalls, etc. Building a PCI-compliant firewall confirms that your business aligns with the most trusted payment firms and meets global cybersecurity standards for payment cards. Prevents fines and penalties Besides the financial loss that hackers directly cause from data breaches, companies may also suffer heavy fines and penalties. They may be required to foot card replacement bills, audit fees, investigation costs, and even compensate for customers’ losses. Every business that processes, stores, accepts, or transmits payment card data must meet the ideal security standards required to avoid fines and penalties. More importantly, becoming compliant helps you establish a good reputation for your business online and offline. Puts security first A compliant firewall enjoys round-the-clock security as it is fully configured to regulate physical access and network-based attacks. So even if there’s an internal malicious actor, you can still secure your customers and prevent unauthorized access. This attitude of putting security first across your IT infrastructure can save you from losses worth hundreds of thousands of dollars in the long run. Maximum speed functionality Organizations that deploy industry-standard firewall policies can function at maximum speed as they’re assured they have a secure network. Working at full speed enables goods or service providers to generate greater revenue as they can satisfy more customers within a short time. Plus, PCI firewall rules don’t only protect the Cardholder Data Environment against attacks, but they also improve your system’s operational efficiency. As a result, you generate maximum ROI from your investment. Schedule a Demo How does PCI compliance affect my business? As a business handling, storing, processing, or transmitting payment card data, it’s essential to prioritize building trust and a positive reputation. This is because customers prefer to do business with brands they trust to provide top security for their card information. Unarguably, being PCI-compliant is one of the core ways to show customers and partners that your business can be trusted. It makes them understand that your security posture meets international standards and can withstand tough security threats. Also, with your compliance certification, you gain a competitive advantage over many other businesses as statistics show that only about 36% of businesses are PCI-compliant. Being compliant allows you to compete with top brands by displaying the alignment of your card data security with the best industry practices. More interestingly, PCI compliance allows every component of your network environment to function optimally, thus giving an impressive and satisfactory output. Schedule a Demo How should the PCI DSS firewall configuration be? PCI DSS firewall should be configured in line with standard practices to protect Cardholder Data Environments (CDE) effectively. You must first regulate the flow of traffic to gain more control and create an effective risk management strategy that prevents cybercriminals from impacting your network. Organizations with a highly complex CDE may resort to segmentation using multiple firewalls, which involves separating systems for better control. Here’s how the PCI DSS firewall should be configured: Set security : Every switch port should have security settings, especially when following segmentation practices. You must set firewalls at the CDE boundaries and also between untrusted networks and the demilitarized zone (DMZ). The DMZ is a sub-network providing an extra layer of security to your internal private network. Establish rules: Set and regularly update firewall rules so that systems and system ports are only accessed by authorized sources. All wireless networks should have perimeter firewalls installed to prevent access from outside the defined environment. Outdated software programs and default passwords should also be avoided during configuration. Inbound/outbound rules: Determine what traffic should be allowed to enter or exit your network based on business needs. Firewalls should only allow traffic needed in the CDE, while other unnecessary traffic must be blocked. Also, direct traffic from the CDE to the Internet should be blocked to avoid creating a loophole. Use VPNs: remote users accessing the system should do so via virtual private networks (VPNs). Also, their portable devices (laptops, desktops, or smart devices) should have firewalls installed. Add/Close switch ports : You should use switch ports (e.g., Internet, office, CDE) to segment different networks. Also, ensure that end users can’t alter the firewall’s configuration on devices and that their management procedures are well-documented. Schedule a Demo Twelve requirements to become PCI-compliant? Every company that aims to achieve PCI compliance must fulfill the twelve PCI DSS compliance requirements. Doing this ensures that your organization’s network enjoys top-tier security controls against any cybersecurity threat. Below are the PCI DSS requirements. 1. Install a firewall and maintain it The first step toward becoming PCI-compliant is installing and maintaining a firewall. Proper firewall configuration will effectively block all untrusted networks attempting to penetrate your system to steal data. Businesses must configure their firewalls, routers, and other network security devices through industry standard rules to ensure they filter inbound and outbound traffic effectively. Inbound traffic is traffic originating from outside your network and attempting to penetrate it, while outbound traffic comes from within your network and goes out. It’s crucial to have standard inbound and outbound firewall rules to protect the network against malicious incoming traffic, such as malware, denial-of-service (DoS) attacks, etc. With firewalls, routers, and other components properly configured, your first line of defense is optimized for card data protection. 2. Initiate strong password protections Third-party components in your IT infrastructure, such as servers, network devices, point of sale (PoS) systems, applications, access points, etc., must be protected with strong passwords. Avoid using vendor-supplied defaults or generic passwords because they are simple and can be guessed easily. In fact, many of them are published online, hence why changing them to stronger passwords is a requirement. You must also have a list of the devices and software that require a password or any other security feature in your network. Plus, you should document your company’s configuration procedures from the time you obtain the third-party product until it enters your IT network. Doing this helps in vulnerability management so that you will take all required security measures each time you introduce a new component to your IT infrastructure. 3. Protect the data of cardholders The essence of becoming PCI-compliant is to protect cardholder data, and that’s why this third requirement is the most important of all. Companies must know the type of data they want to store, its location, and the retention period. Knowing the type of data you want to store helps in determining the most secure way to protect it. Encryption can protect all data through industry-accepted algorithms, truncation, or tokenization. Typically, two-layer protection is considered the best, such as using both encryption and tokenization. You must conduct regular maintenance and scanning to detect any unencrypted primary account numbers (PAN) and ensure that your PCI DSS encryption key management process is strong. As part of the third requirement, businesses should follow standard security controls when displaying primary account numbers. Ideally, only the first six and last four digits can be displayed. 4. Encrypt data that gets transmitted When data is transmitted across open, public networks like the Internet, WiFi, and Bluetooth, it must be encrypted. Failure to encrypt data puts it at great risk, as cybercriminals can often access such data. However, with proper encryption, you can maintain top security for your data at rest and in transit. Also, you should know the destination and source of card data to avoid sending or receiving data from untrusted networks. 5. Install and maintain anti-virus software Companies must install and maintain anti-virus software to protect against malware that can impact system performance. All systems and devices (e.g., laptops, desktops, mobile devices, workstations, etc.) providing local and remote IT network access should have anti-virus programs installed on them. These devices are commonly affected by malware which disrupts system functionality and allows unauthorized access to your network. Nonetheless, with an active and up-to-date anti-virus or anti-malware program, you can detect known malware, protect your system from malicious actors, and have more access control. 6. Update your systems and software The next layer of requirement is the update and maintenance of systems and applications. You should define and implement a process that identifies security risks from anti-virus programs to firewalls. This process should deploy a reliable third-party source to classify these security risks and send notifications for any newly discovered vulnerabilities in the PCI DSS environment. To ensure effective vulnerability management, you should patch (update) all systems, especially those that store or interact with the cardholder data. Examples of other systems that should be patched regularly include routers, application software, switches, databases, and POS terminals. Timely patching helps you resolve any vulnerabilities or bugs (errors) in your system before bad actors take advantage of them. 7. Restrict access to data Access control is a huge criterion when it comes to achieving PCI compliance. Employees should only have access to the data required to fulfill their roles and meet business needs. In other words, access to card data and systems should strictly be on a need-to-know basis. All staff who do not need cardholder data to execute their roles should be restricted from accessing it to prevent unnecessary exposure of sensitive data. Also, you must have a comprehensive list of all staff who need card data and their roles. Other details to document include: role definition current privilege level expected privilege level data resources required by each user to execute operations on card data. 8. Establish unique IDs for those with access After determining users who need access to cardholder data, you’re required to establish unique IDs for each of them. Some organizations use shared/group passwords for staff, which makes it challenging to track certain activities. Such organizations must switch to having unique IDs for each authorized user to fulfill the eighth requirement for PCI DSS compliance. A two-layer authentication must be implemented for every non-console administrative access (remote access). Establishing a complex and unique ID for each person with access to card data allows you to trace any unusual activity to their respective users. Thus, every user can take responsibility for their actions and be summoned for accountability or even face the necessary disciplinary actions for their security errors. If there’s a security threat, unique IDs enable swift response before serious damage is done. 9. Physical access needs to be limited Physical access to systems with cardholder data must be restricted to prevent data theft, manipulation, or destruction. The systems must be locked in a secure location (in a room, drawer, or cabinet). You should monitor the entry and exit doors of physical locations like data centers using surveillance cameras or electronic access controls. All physical access to systems with cardholder data must be kept in a log and retained for at least 90 days. Companies should allow only authorized visitors in the area and keep a document of their activities. Whenever an employee is switching roles or during resignation, all company-related systems with cardholder data or access to your internal network should be retrieved. Finally, on the restriction of physical access, you must destroy any media or device that’s no longer needed in your system. 10. Establish and maintain access logs One very common non-compliance challenge is the establishment and maintenance of access logs. Organizations must have a proper record-keeping and documentation process for all activities across their network, including data flow and access frequency. The collected information about access logs and other activities should be reviewed daily to detect and address any irregular actions. This requirement mandates that the collected information must meet the standard and be taken in real-time to enhance the audit phase. 11. Scan and perform tests to identify vulnerabilities Hackers understand that every system has a degree of vulnerability, and that’s why they tirelessly try new methods to help them penetrate networks and steal data. However, with frequent vulnerability scans and penetration testing, you can stay on top of cyber threats and keep users’ payment card details safe at all times. Vulnerability scans can help you discover any possible error in software programs and your entire security system. With penetration testing, you can discover your IT infrastructure’s weaknesses using the same tools and techniques as hackers. As a result, you will be able to block any loopholes in your physical and wireless networks before cybercriminals detect them. 12. Document your policies The last requirement for PCI DSS compliance relates to the documentation of information security policies. The policies must be reviewed annually and forwarded to the right persons (such as employees, vendors, etc.) to tackle evolving cyber threats effectively. Some important information to include during documentation includes your inventory of equipment, the process of information flow and storage, software, employees with access to sensitive data, etc. As part of fulfilling the last requirement, you must: Perform a formal risk assessment to determine critical assets, threats, and vulnerabilities. Conduct user awareness training Run employee background checks Perform incident management Schedule a Demo How AlgoSec helps with PCI DSS compliance Achieving PCI DSS compliance is one big step toward success for any business storing, processing, accepting, or transmitting payment card information. The process is often daunting and time-consuming as companies must meet the twelve compliance requirements to get their certification. Firewall configuration alone, which is the first requirement, requires keeping thousands of rules in mind. It’s one of the most challenging requirements on the path to PCI DSS Compliance, especially since the rule bases frequently change. Also, even after receiving compliance certification, businesses must show that their security systems continuously align with the industry’s regulations and standards through consistent auditing. All this work can be quite tedious for companies, making it challenging to achieve or maintain PCI DSS compliance. Now, that’s where AlgoSec comes in. AlgoSec helps you with PCI DSS compliance by preparing your firewalls with the proper configuration that’ll help you be compliant and fulfill the first requirement easily. From installation to maintenance, we’d assist you in setting up a compliant firewall that provides formidable security for the cardholder data environment. At AlgoSec, we understand the PCI DSS firewall requirements to achieve a compliant firewall and have the right tools and solutions to configure your firewall. Furthermore, we’d help you consistently stay compliant by identifying gaps in compliance and enabling you to remediate them. By leveraging our intelligent automation solution, you can avoid costly errors caused by manual work, thus helping you stay compliant and secure when adding, removing, or changing policy rules. We know the challenges most companies face when attaining PCI DSS compliance. That’s why we have created an effective solution that enables flawless data collection and auditing, thus helping you establish and maintain access logs as well as document your policies effortlessly. Lastly, we help your business stay continuously compliant by simplifying firewall audits. This allows you to quickly detect any loopholes and regularly update your firewall rules to avoid violating any policy. Schedule a Demo Select a size What is a firewall PCI DSS compliance? What are the benefits of a PCI-compliant firewall? How does PCI compliance affect my business? How should the PCI DSS firewall configuration be? Twelve requirements to become PCI-compliant? How AlgoSec helps with PCI DSS compliance Get the latest insights from the experts Use these six best practices to simplify compliance and risk mitigation with the AlgoSec platform White paper Learn how AlgoSec can help you pass PCI-DSS Audits and ensure Solution overview See how this customer improved compliance readiness and risk Case study Choose a better way to manage your network

AlgoSec security management solution for Juniper Networks Solution Brief 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 and Cisco Catalyst SD-WAN Solution Brief 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

Tal Dayan, security expert for AlgoSec, discusses the secret to passing audits seamlessly and how to introduce automated compliance... Auditing and Compliance Compliance Made Easy: How to improve your risk posture with automated audits Tal Dayan 2 min read Tal Dayan 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 4/29/21 Published Tal Dayan, security expert for AlgoSec, discusses the secret to passing audits seamlessly and how to introduce automated compliance Compliance standards come in many different shapes and sizes. Some organizations set their own internal policies, while others are subject to regimented global frameworks such as PCI DSS , which protects customers’ card payment details; SOX to safeguard financial information or HIPAA , which protects patients’ healthcare data. Regardless of which industry you operate in, regular auditing is key to ensuring your business retains its risk posture whilst also remaining compliant. The problem is that running manual risk and security audits can be a long, drawn-out, and tedious affair. A 2020 report from Coalfire and Omdia  found that for the majority of organizations, growing compliance obligations are now consuming 40% or more of IT security budgets and threaten to become an unsustainable cost.  The report suggests two reasons for this growing compliance burden.  First, compliance standards are changing from point-in-time reviews to continuous, outcome-based requirements. Second, the ongoing cyber-skills shortage is stretching organizations’ abilities to keep up with compliance requirements. This means businesses tend to leave them until the last moment, leading to a rushed audit that isn’t as thorough as it could be, putting your business at increased risk of a penalty fine or, worse, a data breach that could jeopardize the entire organization. The auditing process itself consists of a set of requirements that must be created for organizations to measure themselves against. Each rule must be manually analyzed and simulated before it can be implemented and used in the real world. As if that wasn’t time-consuming enough, every single edit to a rule must also be logged meticulously. That is why automation plays a key role in the auditing process. By striking the right balance between automated and manual processes, your business can achieve continuous compliance and produce audit reports seamlessly. Here is a six-step strategy that can set your business on the path to sustainable and successful ongoing auditing preservation: Step 1: Gather information This step will be the most arduous but once completed it will become much easier to sustain. This is when you’ll need to gather things like security policies, firewall access logs, documents from previous audits and firewall vendor information – effectively everything you’d normally factor into a manual security audit. Step 2: Define a clear change management process A good change management process is essential to ensure traceability and accountability when it comes to firewall changes. This process should confirm that every change is properly authorized and logged as and when it occurs, providing a picture of historical changes and approvals. Step 3: Audit physical & OS security With the pandemic causing a surge in the number of remote workers and devices used, businesses must take extra care to certify that every endpoint is secured and up-to-date with relevant security patches. Crucially, firewall and management services should also be physically protected, with only designated personnel permitted to access them. Step 4: Clean up & organize rule base As with every process, the tidier it is, the more efficient it is. Document rules and naming conventions should be enforced to ensure the rule base is as organized as possible, with identical rules consolidated to keep things concise. Step 5: Assess & remediate risk Now it’s time to assess each rule and identify those that are particularly risky and prioritize them by severity. Are there any that violate corporate security policies? Do some have “ANY” and a permissive action? Make a list of these rules and analyze them to prepare plans for remediation and compliance. Step 6: Continuity & optimization Now it’s time to simply hone the first five steps and make these processes as regular and streamlined as possible. By following the above steps and building out your own process, you can make day-to-day compliance and auditing much more manageable. Not only will you improve your compliance score, you’ll also be able to maintain a sustainable level of compliance without the usual disruption and hard labor caused by cumbersome and expensive manual processes. To find out more about auditing automation and how you can master compliance, watch my recent webinar and visit our firewall auditing and compliance page. 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 persistence of sophisticated ransomware In 2023, organizations faced a surge in ransomware attacks, prompting a reevaluation of... Network Segmentation Navigating the Cybersecurity Horizon in 2024 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 12/17/23 Published The persistence of sophisticated ransomware In 2023, organizations faced a surge in ransomware attacks, prompting a reevaluation of cybersecurity readiness. The focus on high-value assets and critical infrastructure indicated an escalating threat landscape, demanding stronger preemptive measures. This trend is expected to continue in 2024 as cybercriminals exploit vulnerabilities. Beyond relying on technology alone, organizations must adopt strategies like Zero Trust and Micro-segmentation for comprehensive preparedness, fortifying data security. A resolute and practical response is crucial to safeguard critical assets in the evolving cybersecurity landscape. DevSecOps Integration DevSecOps is set to become a cornerstone in software development, integrating security practices proactively. As Infrastructure as a Service (IaaS) popularity rises, customizing security settings becomes challenging, necessitating a shift from network perimeter reliance. Anticipating an “Always-on Security” approach like Infrastructure as Code (IaC), companies can implement policy-based guardrails in the CI/CD pipeline. If risks violating the guardrails are identified, automation should halt for human review. Cloud-Native Application Protection Platforms (CNAPP): The CNAPP market has advanced from basic Cloud Security Posture Management (CSPM) to include varied vulnerability and malware scans, along with crucial behavioral analytics for cloud assets like containers. However, few vendors emphasize deep analysis of Infrastructure as a Service (IaaS) networking controls in risk and compliance reporting. A more complete CNAPP platform should also provide comprehensive analytics of cloud applications’ connectivity exposure. Application-centric approach to network security will supersede basic NSPM Prepare for the shift from NSPM to an application-centric security approach, driven by advanced technologies, to accelerate in 2024. Organizations, grappling with downsizing and staff shortages, will strategically adopt this holistic approach to improve efficiency in the security operations team. Emphasizing knowledge retention and automated change processes will become crucial to maintain security with agility. AI-based enhancements to security processes Generative AI, as heralded by Chat-GPT and its ilk, has made great strides in 2023, and has demonstrated that the technology has a lot of potential. I think that in 2024 we will see many more use cases in which this potential goes from simply being “cool” to a more mature technology that is brought to market to bring real value to owners of security processes. Any use case that involves analyzing, summarizing, or generalizing text, can potentially benefit from a generative AI assist. The trick will be to do so in ways that save human time, without introducing factual hallucinations. 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