Search results

So we’ve made it to the last part of our blog series on PCI 3.0 Requirement 1. The first two posts covered Requirement 1.1... Auditing and Compliance Avoid the Traps: What You Need to Know About PCI Requirement 1 (Part 3) Matthew Pascucci 2 min read Matthew Pascucci Short bio about author here Lorem ipsum dolor sit amet consectetur. Vitae donec tincidunt elementum quam laoreet duis sit enim. Duis mattis velit sit leo diam. Tags Share this article 9/9/14 Published So we’ve made it to the last part of our blog series on PCI 3.0 Requirement 1. The first two posts covered Requirement 1.1 (appropriate firewall and router configurations) and 1.2 (restrict connections between untrusted networks and any system components in the cardholder data environment) and in this final post we’ll discuss key requirements of Requirements 1.3 -1.5 and I’ll again give you my insight to help you understand the implications of these requirements and how to comply with them. Implement a DMZ to limit inbound traffic to only system components that provide authorized publicly accessible services, protocols, and ports (1.3.1.): The DMZ is used to publish services such as HTTP and HTTPS to the internet and allow external entities to access these services. But the key point here is that you don’t need to open every port on the DMZ. This requirement verifies that a company has a DMZ implemented and that inbound activity is limited to only the required protocols and ports. Limit inbound Internet traffic to IP addresses within the DMZ (1.3.2): This is a similar requirement to 1.3.1, however instead of looking for protocols, the requirement focuses on the IPs that the protocol is able to access. In this case, just because you might need HTTP open to a web server, doesn’t mean that all systems should have external port 80 open to inbound traffic. Do not allow any direct connections inbound or outbound for traffic between the Internet and the cardholder data environment (1.3.3): This requirement verifies that there isn’t unfiltered access, either going into the CDE or leaving it, which means that all traffic that traverses this network must pass through a firewall. All unwanted traffic should be blocked and all allowed traffic should be permitted based on an explicit source/destination/protocol. There should never be a time that someone can enter or leave the CDE without first being inspected by a firewall of some type. Implement anti-spoofing measures to detect and block forged source IP addresses from entering the network (1.3.4): In an attempt to bypass your firewall, cyber attackers will try and spoof packets using the internal IP range of your network to make it look like the request originated internally. Enabling the IP spoofing feature on your firewall will help prevent these types of attacks. Do not allow unauthorized outbound traffic from the cardholder data environment to the Internet (1.3.5): Similar to 1.3.3, this requirement assumes that you don’t have direct outbound access to the internet without a firewall. However in the event that a system has filtered egress access to the internet the QSA will want to understand why this access is needed, and whether there are controls in place to ensure that sensitive data cannot be transmitted outbound. Implement stateful inspection, also known as dynamic packet filtering (1.3.6): If you’re running a modern firewall this feature is most likely already configured by default. With stateful inspection, the firewall maintains a state table which includes all the connections that traverse the firewall, and it knows if there’s a valid response from the current connection. It is used to stop attackers from trying to trick a firewall into initiating a request that didn’t previously exist. Place system components that store cardholder data (such as a database) in an internal network zone, segregated from the DMZ and other untrusted networks (1.3.7): Attackers are looking for your card holder database. Therefore, it shouldn’t be stored within the DMZ. The DMZ should be considered an untrusted network and segregated from the rest of the network. By having the database on the internal network provides another layer of protection against unwanted access. [Also see my suggestions for designing and securing you DMZ in my previous blog series: The Ideal Network Security Perimeter Design: Examining the DMZ Do not disclose private IP addresses and routing information to unauthorized parties (1.3.8): There should be methods in place to prevent your internal IP address scheme from being leaked outside your company. Attackers are looking for any information on how to breach your network, and giving them your internal address scheme is just one less thing they need to learn. You can stop this by using NAT, proxy servers, etc. to limit what can be seen from the outside. Install personal firewall software on any mobile and/or employee-owned devices that connect to the Internet when outside the network (for example, laptops used by employees), and which are also used to access the network (1.4): Mobile devices, such as laptops, that can connect to both the internal network and externally, should have a personal firewall configured with rules that prevent malicious software or attackers from communicating with the device. These firewalls need to be configured so that their rulebase can never be stopped or changed by anyone other than an administrator. Ensure that security policies and operational procedures for managing firewalls are documented, in use, and known to all affected parties (1.5): There needs to be a unified policy regarding firewall maintenance including how maintenance procedures are performed, who has access to the firewall and when maintenance is scheduled. Well, that’s it! Hopefully, my posts have given you a better insight into what is actually required in Requirement 1 and what you need to do to comply with it. 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

Ensure your network security is up to par with a comprehensive firewall audit checklist. Review and optimize security policy rules to prevent vulnerabilities. Firewall audit checklist for security policy rules review ---- ------- Schedule a Demo Select a size ----- Get the latest insights from the experts Choose a better way to manage your network

Webinars Firewall Rule Recertification - An Application-Centric Approach As part of your organization’s security policy management best practices, firewall rules must be reviewed and recertified regularly to ensure security, compliance and optimal firewall performance. Firewall rules which are out of date, unused or unnecessary should be removed, as firewall bloat creates gaps in your security posture, causes compliance violations, and impacts firewall performance. Manual firewall rule recertification, however, is an error-prone and time-consuming process. Please join our webinar by Asher Benbenisty, AlgoSec’s Director of Product Marketing, who will introduce an application-centric approach to firewall recertification, bringing a new, efficient, effective and automated method of recertifying firewall rules. The webinar will: Why it is important to regularly review and recertify your firewall rules The application-centric approach to firewall rule recertification How to automatically manage the rule-recertification process Want to find out more about the importance of ruleset hygiene? Watch this webinar today! Asher Benbenisty Director of product marketing Relevant resources Tips for Firewall Rule Recertification Watch Video Firewall Rule Recertification Read Document 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

Understand the Federal Information Security Management Act (FISMA). Learn key requirements, best practices, and how to achieve and maintain FISMA compliance. FISMA compliance defined: Requirements & best practices ---- ------- Schedule a Demo Select a size ----- 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 continuous compliance Solution overview See how this customer improved compliance readiness and risk management with AlgoSec Case study Choose a better way to manage your network

Multiple AWS accounts: Security best practices E-BOOK 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

Explore Algosec's customer success stories to see how organizations worldwide improve security, compliance, and efficiency with our solutions. TECHCOMBANK SAVES TIME AND RESOURCES WITH SIMPLIFIED FIREWALL POLICY MANAGEMENT Organization Techcombank Industry Financial Services Headquarters Hanoi, Vietnam Download case study Share Customer
success stories "AlgoSec enables us to identify ways to consolidate and optimize rules and perform deep risk analysis and automate workflows in ways that other products cannot match" Background Techcombank is one of the largest joint stock commercial banks in Vietnam. With more than 300 branches and 7,000 staff, Techcombank provides deposit products, loans, leasing, cash management and other services to more than 3.3 million individual customers and 45,000 corporate clients. Challenge Tens of firewall devices and hundreds of routers and switches protect the financial data of Techcombank’s customers, as well as the operations of hundreds of branches throughout Vietnam. As a bank, all security policies and firewall configurations must comply with PCI-DSS and ISO27001 standards. Ensuring compliance, however, created ongoing headaches for the IT security team. “With equipment from many different vendors, even simple policy audits were challenging tasks,” says Mr. Van Anh Tuan, CSO of Techcombank. “As a result of the diversity of products and lack of visibility, it was difficult for us to monitor changes to rule configurations in real time in order to maintain internal security compliance as well as PCI compliance.” “Cleaning up and fine tuning firewall policies was a particularly complex process, which made it difficult to respond quickly to the changing needs of our business applications,” adds Mr. Tuan. “We wanted a way to optimize and consolidate rules across all of our firewalls, regardless of manufacturer, and completely automate the end-to-end workflow for firewall rule change management.” In addition, Techcombank sought a solution that would simplify the process of conducting risk analysis, evaluating PCI compliance and identifying the necessary steps for remediation. Solution Following an in-depth competitive evaluation, Techcombank selected AlgoSec’s Security Management solution. “AlgoSec met many of our key requirements, better than its competitors in our evaluation,” Mr. Tuan notes. Techcombank particularly liked AlgoSec’s superior security policy analysis and ability to make actionable recommendations with a high level of accuracy. “AlgoSec will enable us to identify ways to consolidate and optimize rules, perform deep risk analysis, automate workflows and ensure compliance in ways that other products cannot match,” says Mr. Tuan. Techcombank’s IT team wants to be able to quickly identify security policy risks and see what specific steps they need to take for remediation. The bank uses AlgoSec to identify overly permissive firewall rules based on actual use as well as duplicate, unused and expired rules and objects. This information gives Techcombank the data they need to close off potential access points and help prevent attacks. AlgoSec also provides clear, detailed recommendations on how to best reorder rules for optimal firewall performance. In addition, AlgoSec validates firewall policy and rules against regulations such as PCI, as well as industry best practices and customized corporate policies to uncover and prioritize risks and track trends over time. For Mr. Tuan, one of the most valuable benefits of AlgoSec is the increased visibility into security policies across the full range of devices. “Now we can easily monitor our firewall operations and quickly detect any mistakes or non-compliant changes made. These operations used to be invisible to me.” Mr. Tuan comments. The AlgoSec deployment process went very smoothly for Techcombank. “Our team received training from AlgoSec and their partners here in Vietnam and we were fully utilizing the product almost immediately. Post-implementation support has addressed every issue quickly and enabled us to take advantage of all aspects of the product in order to optimize our firewall rules and improve our security posture even faster than we anticipated,” Mr. Tuan adds. Since implementation, AlgoSec has enabled Techcombank’s IT team to “greatly reduce our time and resources when complying with internal policies and PCI standards, and when monitoring changes in rules,” says Mr. Tuan. “We are very happy with the improved security and visibility provided by AlgoSec and will continue to use and exploit more AlgoSec features and add licenses,” he concluded. Schedule time with one of our experts

The aim of this post is to provide a very high-level illustration of the DNS Tunneling method used in the SolarWinds supply chain attack.... Cloud Security DNS Tunneling In The SolarWinds Supply Chain Attack 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/23/20 Published The aim of this post is to provide a very high-level illustration of the DNS Tunneling method used in the SolarWinds supply chain attack . An Attacker compromises SolarWinds company and trojanizes a DLL that belongs to its software. Some of the customers receive the malicious DLL as an update for the SolarWinds Orion software. “Corporation XYZ” receives the malicious and digitally signed DLL via update. SolarWinds Orion software loads the malicious DLL as a plugin. Once activated, the DLL reads a local domain name “local.corp-xyz.com” (a fictious name). The malware encrypts the local domain name and adds it to a long domain name. The long domain name is queried with a DNS server (can be tapped by a passive DNS sensor). The recursive DNS server is not authorized to resolve avsvmcloud[.]com, so it forwards the request. An attacker-controlled authoritative DNS server resolves the request with a wildcard A record. The Attacker checks the victim’s name, then adds a CNAME record for the victim’s domain name. The new CNAME record resolves the long domain name into an IP of an HTTP-based C2 server. The malicious DLL downloads and executes the 2nd stage malware (TearDrop, Cobalt Strike Beacon). A Threat Researcher accesses the passive DNS (pDNS) records. One of the long domain names from the pDNS records is decrypted back into “local.corp-xyz.com”. The Researcher deducts that the decrypted local domain name belongs to “Corporation XYZ”. 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

Hybrid cloud computing enables organizations to deploy sensitive workloads on-premise or in a private cloud, while hosting less... DevSecOps Why organizations need to embrace new thinking in how they tackle hybrid cloud security challenges 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 10/9/22 Published Hybrid cloud computing enables organizations to deploy sensitive workloads on-premise or in a private cloud, while hosting less business-critical resources on public clouds. But despite its many benefits, the hybrid environment also creates security concerns. AlgoSec’s co-founder and CTO, Prof. Avishai Wool shares his expert insights on these concerns and offers best practices to boost hybrid cloud security. Hybrid cloud computing combines on-premises infrastructure, private cloud services, and one or more public clouds. Going hybrid provides businesses with enhanced flexibility, agility, cost savings, and scalability to innovate, grow, and gain a competitive advantage. So, how can you simplify and strengthen security operations in the hybrid cloud? It all starts with visibility – you still can’t protect what you can’t see To protect their entire hybrid infrastructure, applications, workloads, and data, security teams need to know what these assets are and where they reside. They also need to see the entire hybrid estate and not just the individual elements. However, complete visibility is a serious hybrid cloud security challenge. Hybrid environments are highly complex, which can create security blind spots, which then prevent teams from identifying, evaluating, and most importantly, mitigating risk. Another hybrid cloud security concern is that you cannot implement a fragmented security approach to control the entire network. With thousands of integrated and inter-dependent resources and data flowing between them, vulnerabilities crop up, increasing the risk of cyberattacks or breaches. For complete hybrid cloud security, you need a holistic approach that can help you control the entire network. Is DevSecOps the panacea? Not quite In many organizations, DevSecOps teams manage cloud security because they have visibility into what’s happening inside the cloud. However, in the hybrid cloud, many applications have servers or clients existing outside the cloud, which DevSecOps may not have visibility into. Also, the protection of data flowing into and out of the cloud is not always under their remit. To make up for these gaps, other teams are required to manage security operations and minimize hybrid cloud risks. These additional processes and team members must be coordinated to ensure continuous security across the entire hybrid network environment. But this is easier said than done. Using IaC to balance automation with oversight is key, but here’s why you shouldn’t solely rely on it Infrastructure as code (IaC) will help you automatically deploy security controls in the hybrid cloud to prevent misconfiguration errors, non-compliance, and violations while in the production stage and pre application testing. With IaC-based security, you can define security best practices in template files, which will minimize risks and enhance your security posture. But there’s an inherent risk in putting all your eggs in the automation and IaC basket. Due to the fact that all the controls are on the operational side, it can create serious hybrid cloud security issues. And without human attention and action, vulnerabilities may remain unaddressed and open the door to cyberattacks. Since security professionals who are not on the operational side must oversee the cloud environment, it could easily open the door to miscommunication and human errors – a very costly proposition for organizations. For this very reason, you should also implement a process to regularly deploy automatic updates without requiring time-consuming approvals that slow down workflows and weaken security. Strive for 95% automated changes and only involve a person for the remaining 5% that requires human input. Hybrid cloud security best practices – start early, start strong When migrating from on-prem to the cloud, you can choose a greenfield migration or a lift-and-shift migration. Greenfield means rolling out a brand-new application. In this case, ensure that security considerations are “baked in” from the beginning and across all processes. This “shift left” approach helps build an environment that’s secure from the get-go. This ensures that all team members adhere to a unified set of security policy rules to minimize vulnerabilities and reduce security risks within the hybrid cloud environment. If you lift-and-shift on-prem applications to the cloud, note any security assumptions made when they were designed. This is important because they were not built for the cloud and may incorporate protocols that increase security risks. Next, implement appropriate measures during migration planning. For example, implement an Application Load Balancer if applications leverage plaintext protocols, and use sidecars to encrypt applications without having to modify the original codebase. You can also leverage hybrid cloud security solutions to detect and mitigate security problems in real-time. Matching your cloud security with application structure is no longer optional Before moving to a hybrid cloud, map the business logic, application structure, and application ownership into the hybrid cloud estate’s networking structure. To simplify this process, here are some tried and proven ways to consider. Break up your environment into a virtual private cloud (VPC) or virtual network. With the VPC, you can monitor connections, screen traffic, create multiple subnets, and also restrict instance access to improve security posture. Use networking constructs to segregate applications into different functional and networking areas in the cloud. This way, you can deploy network controls to segment your cloud estate and ensure that only authorized users can access sensitive data and resources. Tag all resources based on their operating system, business unit, and geographical area. Tags with descriptive metadata can help to identify resources. They also establish ownership and accountability, provide visibility into cloud consumption, and help with the deployment of security policies. Conclusion In today’s fast-paced business environment, hybrid cloud computing can benefit your organization in many ways. But to capture these benefits, you should make an effort to boost hybrid cloud security. Incorporate the best practices discussed here to improve security and take full advantage of your hybrid environment. To learn more about hybrid cloud security, listen to our Lessons in Cybersecurity podcast episode or head to our hybrid cloud resource hub here . 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

Explore Algosec's customer success stories to see how organizations worldwide improve security, compliance, and efficiency with our solutions. BM&FBOVESPA Invests In Security Policy Management To Improve Operational Efficiencies Organization BM&FBOVESPA Industry Financial Services Headquarters Sao Paulo, Brazil Download case study Share Customer
success stories "AlgoSec helps us maintain a problem-free environment. And because of operational efficiencies, the product paid for itself within the first year. With AlgoSec, we can do more with less" Leading Latin American Stock Exchange Maintains a Secure, Compliant Trading Environment AlgoSec Business Impact • Recouped investment in AlgoSec within the first year• Reduce rule review project from 1 month to 1 day• Helps maintain a secure, compliant environment• Frees up staff to focus on other crucial security tasks Background Headquartered in Sao Paulo, Brazil, BM&FBOVESPA is the largest stock exchange in Latin America. BM&FBOVESPA has a diversified and integrated trading model offering a complete custody system. Trading takes place in an exclusively electronic environment. The Exchange enables customers to trade equities, to hedge and to execute arbitrage, investment diversification, allocation and the leveraging of positions. Challenge To keep its systems and transactions secure, BM&FBOVESPA utilizes firewalls from several vendors. In total these firewalls have about 40,000 firewall rules, with another 5,000 added annually. Even with two full-time employeesfocused on maintaining firewall rules, the steady addition of rules and objects created clutter and consumed the firewall appliances’ CPU and memory. Therefore, BM&FBOVESPA realized that an automated solution for firewall policy management was the natural next step in the maturity of its information security processes. “Manually managing our firewall policies was difficultand time consuming. We needed a solution that supported a variety of different firewall vendors and could integrate and manage all policies in an automated manner,” said Wellington Vita, Information Security Manager of BM&FBOVESPA. Solution Following a recommendation from Compugraf, one of BM&FBOVESPA’s key security partners, Vita and his team evaluated AlgoSec’s Security Management solution. The proof of concept clearly showed the value of the solution and the ease and speed with which it could be deployed. The ability to integrate and manage devices from multiple vendors and provide visibility across the entire network was also important in BM&FBOVESPA’s decision to select AlgoSec. Results BM&FBOVESPA uses AlgoSec on a daily basis to manage its firewall policies. “AlgoSec is a great product which helps us maintain the core of our environment -the firewall policy. With AlgoSec we can easily identify unused rules and objects, as well as rules that were not compliant with our information security policy.” noted Vita. “While using AlgoSec, we also discovered a new benefit. AlgoSec enables our information security architects to understand how information flows between firewalls, which helps them significantly with their information security projects.” The gains in efficiency and productivity have dramatically reduced the time consumed by firewall policy management. “Because of operational efficiencies AlgoSec paid for itself in the first year,” said Vita. In addition to cutting the time needed to perform ongoing policy management, the solution enabled BM&FBOVESPA to meet deadlines that would previously have been unachievable. “A month ago, we had to review our incoming internet access rules in two days — and did. Without AlgoSec, it would have taken us at least a month to accomplish this task,” added Vita.“AlgoSec helps us maintain a problem-free environment. And we have been able to move members of our team who previously handled these maintenance jobs onto other tasks, so we can do more with less. I recommend AlgoSec to other companies — it will help them improve their firewall policy management processes,” concluded Vita. Schedule time with one of our experts

The Digital Operational Resilience Act (DORA) is set to transform how financial institutions across the European Union manage and... Network Security Navigating DORA: How to ensure your network security and compliance strategy is resilient Joseph Hallman 2 min read Joseph Hallman 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/19/24 Published The Digital Operational Resilience Act (DORA) is set to transform how financial institutions across the European Union manage and mitigate ICT (Information and Communications Technology) risks. With the official compliance deadline in January 2025, organizations are under pressure to ensure their systems can withstand and recover from disruptions—an urgent priority in an increasingly digitized financial ecosystem. DORA introduces strict requirements for ICT risk management, incident reporting, and third-party oversight, aiming to bolster the operational resilience of financial firms. But what are the key deadlines and penalties, and how can organizations ensure they stay compliant? Key Timelines and Penalties Under DORA Compliance deadline: January 2025 – Financial firms and third-party ICT providers must have operational resilience frameworks in place by this deadline. Regular testing requirements – Companies will need to conduct resilience testing regularly, with critical institutions potentially facing enhanced testing requirements. Penalties for non-compliance – Fines for failing to comply with DORA’s mandates can be substantial. Non-compliance could lead to penalties of up to 2% of annual turnover, and repeated breaches could result in even higher sanctions or operational restrictions. Additionally, firms face reputational risks if they fail to meet incident reporting and recovery expectations. Long term effect- DORA increases senior management's responsibility for ICT risk oversight, driving stronger internal controls and accountability. Executives may face liability for failing to manage risks, reinforcing the focus on compliance and governance. These regulations create a dynamic challenge, as organizations not only need to meet the initial requirements by 2025, but also adapt to the changes as the standards continue to evolve over time. Firewall rule recertification The Digital Operational Resilience Act (DORA) emphasizes the need for financial institutions in the EU to ensure operational resilience in the face of technological risks. While DORA does not explicitly mandate firewall rule recertification , several of its broader requirements apply to the management and oversight of firewall rules and the overall security infrastructure, which would include periodic firewall rule recertification as part of maintaining a robust security posture. A few of the key areas relevant to firewall rules and the necessity for frequent recertification are highlighted below. ICT Risk Management Framework- Article 6 requires financial institutions to implement a comprehensive ICT (Information and Communication Technology) risk management framework. This includes identifying, managing, and regularly testing security policies, which would encompass firewall rules as they are a critical part of network security. Regular rule recertification helps to ensure that firewall configurations are up-to-date and aligned with security policies. Detection Solutions- Article 10 mandates that financial entities must implement effective detection solutions to identify anomalies, incidents, and cyberattacks. These solutions are required to have multiple layers of control, including defined alert thresholds that trigger incident response processes. Regular testing of these detection mechanisms is also essential to ensure their effectiveness, underscoring the need for ongoing evaluations of firewall configurations and rules ICT Business Continuity Policy- Article 11 emphasizes the importance of establishing a comprehensive ICT business continuity policy. This policy should include strategic approaches to risk management, particularly focusing on the security of ICT third-party providers. The requirement for regular testing of ICT business continuity plans, as stipulated in Article 11(6), indirectly highlights the need for frequent recertification of firewall rules. Organizations must document and test their plans at least once a year, ensuring that security measures, including firewalls, are up-to-date and effective against current threats. Backup, Restoration, and Recovery- Article 12 outlines the procedures for backup, restoration, and recovery, necessitating that these processes are tested periodically. Entities must ensure that their backup and recovery systems are segregated and effective, further supporting the requirement for regular recertification of security measures like firewalls to protect backup systems against cyber threats. Crisis Communication Plans- Article 14 details the obligations regarding communication during incidents, emphasizing that organizations must have plans in place to manage and communicate risks related to the security of their networks. This includes ensuring that firewall configurations are current and aligned with incident response protocols, necessitating regular reviews and recertifications to adapt to new threats and changes in the operational environment. In summary, firewall rule recertification supports the broader DORA requirements for maintaining ICT security, managing risks, and ensuring network resilience through regular oversight and updates of critical security configurations. How AlgoSec helps meet regulatory requirements AlgoSec provides the tools, intelligence, and automation necessary to help organizations comply with DORA and other regulatory requirements while streamlining ongoing risk management and security operations. Here’s how: 1. Comprehensive network visibility AlgoSec offers full visibility into your network, including detailed insights into the application connectivity that each firewall rule supports. This application-centric approach allows you to easily identify security gaps or vulnerabilities that could lead to non-compliance. With AlgoSec, you can maintain continuous alignment with regulatory requirements like DORA by ensuring every firewall rule is tied to an active, relevant application. This helps ensure compliance with DORA's ICT risk management framework, including continuous identification and management of security policies (Article 6). Benefit : With this deep visibility, you remain audit-ready with minimal effort, eliminating manual tracking of firewall rules and reducing the risk of errors. 2. Automated risk and compliance reports AlgoSec automates compliance checks across multiple regulations, continuously analyzing your security policies for misconfigurations or risks that may violate regulatory requirements. This includes automated recertification of firewall rules, ensuring your organization stays compliant with frameworks like DORA's ICT Risk Management (Article 6). Benefit : AlgoSec saves your team significant time and reduces the likelihood of costly mistakes, while automatically generating audit-ready reports that simplify your compliance efforts. 3. Incident reporting and response DORA mandates rapid detection, reporting, and recovery during incidents. AlgoSec’s intelligent platform enhances incident detection and response by automatically identifying firewall rules that may be outdated or insecure and aligning security policies with incident response protocols. This helps ensure compliance with DORA's Detection Solutions (Article 10) and Crisis Communication Plans (Article 14). Benefit : By accelerating response times and ensuring up-to-date firewall configurations, AlgoSec helps you meet reporting deadlines and mitigate breaches before they escalate. 4. Firewall policy management AlgoSec simplifies firewall management by taking an application-centric approach to recertifying firewall rules. Instead of manually reviewing outdated rules, AlgoSec ties each firewall rule to the specific application it serves, allowing for quick identification of redundant or risky rules. This ensures compliance with DORA’s requirement for regular rule recertification in both ICT risk management and continuity planning (Articles 6 and 11). Benefit : Continuous optimization of security policies ensures that only necessary and secure rules are in place, reducing network risk and maintaining compliance. 5. Managing third-party risk DORA emphasizes the need to oversee third-party ICT providers as part of a broader risk management framework. AlgoSec integrates seamlessly with other security tools, providing unified visibility into third-party risks across your hybrid environment. With its automated recertification processes, AlgoSec ensures that security policies governing third-party access are regularly reviewed and aligned with business needs. Benefit : This proactive management of third-party risks helps prevent potential breaches and ensures compliance with DORA’s ICT Business Continuity requirements (Article 11). 6. Backup, Restoration, and Recovery AlgoSec helps secure backup and recovery systems by recertifying firewall rules that protect critical assets and applications. DORA’s Backup, Restoration, and Recovery (Article 12) requirements emphasize that security controls must be periodically tested. AlgoSec automates these tests, ensuring your firewall rules support secure, segregated backup systems. Benefit : Automated recertification prevents outdated or insecure rules from jeopardizing your backup processes, ensuring you meet regulatory demands. Stay ahead of compliance with AlgoSec Meeting evolving regulations like DORA requires more than a one-time adjustment—it demands a dynamic, proactive approach to security and compliance. AlgoSec’s application-centric platform is designed to evolve with your business, continuously aligning firewall rules with active applications and automating the process of policy recertification and compliance reporting. By automating key processes such as risk assessments, firewall rule management, and policy recertification, AlgoSec ensures that your organization is always prepared for audits. Continuous monitoring and real-time alerts keep your security posture compliant with DORA and other regulations, while automated reports simplify audit preparation—minimizing the time spent on compliance and reducing human error. With AlgoSec, businesses not only meet compliance regulations but also enhance operational efficiency, improve security, and maintain alignment with global standards. As DORA and other regulatory frameworks evolve, AlgoSec helps you ensure that compliance is an integral, seamless part of your operations. Read our latest whitepaper and watch a short video to learn more about our application-centric approach to firewall rule recertification 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

Explore Algosec's customer success stories to see how organizations worldwide improve security, compliance, and efficiency with our solutions. VERIZON HELPS CLIENTS IMPROVE SECURITY AND BUSINESS AGILITY USING ALGOSEC Organization Verizon Industry Telecom Headquarters NJ, USA Download case study Share Customer
success stories "I selected AlgoSec’s Security Management Solution because the reporting is very trustworthy, it helps reduce the operational workload for network security administrators, and ultimately it improves performance and security." AlgoSec Business Impact Reduce the workload for the operations team and improve efficiency Provide comprehensive trustworthy reporting on change management Improve overall network performance and security Background Verizon is one of the world’s largest global communications companies and an international technology innovator. Verizon provides products and services related to networks, cloud, machine to machine and mobile technologies; data, hosting and storage; and managed security, as well as other wired and wireless offerings to business and government clients around the world. The company’s Global IP Network connects people and businesses in 2,700 cities and 150 countries. Challenge Verizon’s professional services consultants find that their clients too often focus on compliance to the detriment of security and operational issues. “From an auditing perspective, if the firewall is up and running some clients think they are more or less okay,” says Stefano Ciminelli, EMEA Practice Manager, Business Resiliency & Optimization at Verizon Business. Ciminelli warns that clients also need to be certain that “the firewall policies do not contain mistakes—those that could bring down their business. It’s not just a problem of protecting the IT systems, it’s really a matter of protecting the business,” he notes. Firewall management can also create tension between the network security group and business managers. “You always have the network security people focused on IT and the business people who like to focus on change management. Often these two groups don’t really communicate or understand each other easily,” Ciminelli adds.Moreover, many companies have several people devoted to managing firewalls and “firefighting,” “because they simply do not have the right tools,” says Ciminelli. Solution Ciminelli and his team at Verizon wanted to provide their clients with a way to address IT and security issues and, at the same time, automate change management workflows in order to support business continuity.“You want to be operationally efficient; you want to be secure; and especially, you want to help your business do their business. But, when it comes to network firewall management and analysis, you actually have few tools available that help you meet all those goals,” says Ciminelli. From the security manager’s perspective, AlgoSec’s Security Management Solution was the top choice. “The reporting is very trustworthy, it helps reduce the operational workload for network security administrators, and ultimately it improves performance and security,” Ciminelli states. “You can find a lot of vendors for security products in the market. But I don’t want to just sell products. I am entrusted to recommend quality services, so I rely on an extremely trustworthy partner like AlgoSec.” Results Ciminelli reports that when his customers invest in AlgoSec, “they are very happy because they can proactively manage their firewalls.” More importantly, though, “they are not forced to change a rule, close their eyes, cross their fingers and hope that everything is going to be okay.” Customers can trust AlgoSec’s reports to show how a rule change will affect access and their overall security before a change is made, and that there will be no surprises after the fact. The ability to share information between IT and business managers has also provided some unexpected benefits for Ciminelli. “When it comes to asking for additional budget, for instance, IT can now prove value and that makes life easier for everybody,” he notes. Customer service ranks high in Ciminelli’s priorities—and AlgoSec consistently delivers. “Whenever I have a problem I always get very efficient and proactive technical support from the AlgoSec team. This is one of the primary reasons I continue to advise my customers to purchase AlgoSec,” he says. Ciminelli urges his clients and other companies to think broadly about the real purpose of firewall policy management. “What you want is not just a well configured firewall, you want good long-term security management.” The goal is to have a firewall that provides excellent protection as the company grows, needs change, and applications are deployed, changed or decommissioned. Ciminelli’s final recommendation? “Using AlgoSec products and relying on good professional services to help you, that is really the smart choice.” Schedule time with one of our experts

The business case for AlgoSec Cloud Enterprise (Horizon ACE) 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