Search results

IT Central Station and CSO PeerPaper Report Download PDF Schedule time with one of our experts 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. Leading payment solutions company credits AlgoSec for increasing security and compliance Organization Payment Solutions Industry Financial Services Headquarters Download case study Share Customer
success stories "Leading fintech company rapidly improves security and compliance with AlgoSec jumpstart program" Background The company is one of the largest payment solutions providers, with offices processing more than 28 billion transactions worldwide. The company services 800,000 merchant outlets that generate $120 billion in processing volume. Its businesses include credit card processing, merchant acquisition and issuance of bank credit cards. The company grew to its enormous size through innovation and acquisition. It has introduced modern technology into the payments industry and has acquired many innovative companies over the last three decades. Challenges Today, the company operates 10 data centers with varying security architectures and firewall equipment from different vendors. The security staff is currently in the process of a cross-company firewall consolidation that will take several years to complete. The company is automating its change management of firewall rules to cut down on the time and effort spent on researching and implementing rules to keep up with its fast growth. It deploys rule changes during tight, scheduled “push windows” and conducts compliance reviews twice per year. The firewall change process is highly complex with many steps: Request Design Peer Review Management Approval Implementation Validation Success for the security team is all about time. They seek to automate the process by reducing time spent on: Research and writing rules Peer reviews Staging Security peering after staging Firewall push window requirements Quarterly firewall ruleset reviews as part of compliance objectives Solution The security team acquired AlgoSec Firewall Analyzer (AFA) and deployed it at two of its data centers in Arizona and Colorado. In both locations, the company is in the process of firewall migration to consolidate on one vendor. However, they need to add firewall clusters one at a time after each migration instead of all at once. The company took advantage of AlgoSec’s Jumpstart Program that delivers the benefits of AlgoSec Firewall Analyzer in conjunction with other AlgoSec solutions quickly. With Jumpstart, the company is quickly able to: Automate the discovery and mapping of enterprise applications Automate the change management processes Adopt the new processes across the company Realize rapid ROI The company’s lead security infrastructure consultant proclaimed, “AlgoSec customized their Jumpstart Program just for us. Their people are engaged, personable, skilled and highly efficient. They became part of our team dedicated to our success.” In addition to getting Firewall Analyzer up and running quickly and delivering its benefits, the Jumpstart team’s AFA deployment immediately identified network security gaps and helped the company close them, making them more secure and compliant. Results AlgoSec Firewall Analyzer is achieving all the goals of the security team. Time for policy writing reduced from 90 hours to 15 hours – 83% less Cut the total process time by half, enabling the security team to keep up with the barrage of change requests. Reduced the admin overhead from 30 to 4 – 87% less “Automation is definitely the way to go,” declared their security consultant. “We can now stay on top of the process even while we migrate our firewalls. We are looking for more from AlgoSec.” The company is now in the process of implementing AlgoSec FireFlow (AFF) to enhance the existing change management system with intelligent network and security automation. AlgoSec FireFlow enforces compliance and automatically documents the entire change-management lifecycle. Some of the features include: Processing of firewall changes with zero-touch automation Elimination of mistakes and rework, and improvement of accountability for change requests Proactive assessment of the impact of network changes to ensure security and continuous compliance Automation of the rule–recertification processes Schedule time with one of our experts

Making Risk Management Easier: How One Bank Got Smarter About Security Case Study Download PDF Schedule time with one of our experts 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

Last week our CTO, Professor Avishai Wool, presented a technical webinar on the do’s and don’ts for managing external connectivity to and... Auditing and Compliance 4 tips to manage your external network connections Joanne Godfrey 2 min read Joanne Godfrey 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/10/15 Published Last week our CTO, Professor Avishai Wool, presented a technical webinar on the do’s and don’ts for managing external connectivity to and from your network . We kicked off our webinar by polling the audience (186 people) on how many external permanent connections into their enterprise network they have. 40% have less than 50 external connections 31% have 50-250 external connections 24% have more than 250 external connections 5% wish they knew how many external connections they have! Clearly this is a very relevant issue for many enterprises, and one which can have a profound effect on security. The webinar covered a wide range of best practices for managing the external connectivity lifecycle and I highly recommend that you view the full presentation. But in the meantime, here are a few key issues that you should be mindful of when considering how to manage external connectivity to and from your network: Network Segmentation While there has to be an element of trust when you let an external partner into your network, you must do all you can to protect your organization from attacks through these connections. These include placing your servers in a demilitarized zone (DMZ), segregating them by firewalls, restricting traffic in both directions from the DMZ as well as using additional controls such as web application firewalls, data leak prevention and intrusion detection. Regulatory Compliance Bear in mind that if the data being accessed over the external connection is regulated, both your systems and the related peer’s systems are now subject t. So if the network connection touches credit card data, both sides of the connection are in scope, and outsourcing the processing and management of regulated data to a partner does not let you off the hook. Maintenance Sometimes you will have to make changes to your external connections, either due to planned maintenance work by your IT team or the peer’s team, or as a result of unplanned outages. Dealing with changes that affect external connections is more complicated than internal maintenance, as it will probably require coordinating with people outside your organisation and tweaking existing workflows, while adhering to any contractual or SLA obligations. As part of this process, remember that you’ll need to ensure that your information systems allow your IT teams to recognize external connections and provide access to the relevant technical information in the contract, while supporting the amended workflows. Contracts In most cases there is a contract that governs all aspects of the external connection – including technical and business issues. The technical points will include issues such as IP addresses and ports, technical contact points, SLAs, testing procedures and the physical location of servers. It’s important, therefore, that this contract is adhered to whenever dealing with technical issues related to external connections. These are just a few tips and issues to be aware of. To watch the webinar from Professor Wool in full, check out the recording here . Schedule a demo Related Articles Navigating Compliance in the Cloud AlgoSec Cloud Mar 19, 2023 · 2 min read 5 Multi-Cloud Environments Cloud Security Mar 19, 2023 · 2 min read Convergence didn’t fail, compliance did. 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

Containers aren’t VMs. They’re a great lightweight deployment solution, but they’re only as secure as you make them. You need to keep... Cloud Security Best Practices for Docker Containers’ Security 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 7/27/20 Published Containers aren’t VMs. They’re a great lightweight deployment solution, but they’re only as secure as you make them. You need to keep them in processes with limited capabilities, granting them only what they need. A process that has unlimited power, or one that can escalate its way there, can do unlimited damage if it’s compromised. Sound security practices will reduce the consequences of security incidents. Don’t grant absolute power It may seem too obvious to say, but never run a container as root. If your application must have quasi-root privileges, you can place the account within a user namespace , making it the root for the container but not the host machine. Also, don’t use the –privileged flag unless there’s a compelling reason. It’s one thing if the container does direct I/O on an embedded system, but normal application software should never need it. Containers should run under an owner that has access to its own resources but not to other accounts. If a third-party image requires the –privileged flag without an obvious reason, there’s a good chance it’s badly designed if not malicious. Avoid running a Docker socket in a container. It gives the process access to the Docker daemon, which is a useful but dangerous power. It includes the ability to control other containers, images, and volumes. If this kind of capability is necessary, it’s better to go through a proper API. Grant privileges as needed Applying the principle of least privilege minimizes container risks. A good approach is to drop all capabilities using –cap-drop=all and then enabling the ones that are needed with –cap-add . Each capability expands the attack surface between the container and its environment. Many workloads don’t need any added capabilities at all. The no-new-privileges flag under security-opt is another way to protect against privilege escalation. Dropping all capabilities does the same thing, so you don’t need both. Limiting the system resources which a container guards not only against runaway processes but against container-based DoS attacks. Beware of dubious images When possible, use official Docker images. They’re well documented and tested for security issues, and images are available for many common situations. Be wary of backdoored images . Someone put 17 malicious container images on Docker Hub, and they were downloaded over 5 million times before being removed. Some of them engaged in cryptomining on their hosts, wasting many processor cycles while generating $90,000 in Monero for the images’ creator. Other images may leak confidential data to an outside server. Many containerized environments are undoubtedly still running them. You should treat Docker images with the same caution you’d treat code libraries, CMS plugins, and other supporting software, Use only code that comes from a trustworthy source and is delivered through a reputable channel. Other considerations It should go without saying, but you need to rebuild your images regularly. The libraries and dependencies that they use get security patches from time to time, and you need to make sure your containers have them applied. On Linux, you can gain additional protection from security profiles such as secomp and AppArmor . These modules, used with the security-opt settings, let you set policies that will be automatically enforced. Container security presents its distinctive challenges. Experience with traditional application security helps in many ways, but Docker requires an additional set of practices. Still, the basics apply as much as ever. Start with trusted code. Don’t give it the power to do more than it needs to do. Use the available OS and Docker features for enhancing security. Monitor your systems for anomalous behavior. If you take all these steps, you’ll ward off the large majority of threats to your Docker environment. Schedule a demo Related Articles Navigating Compliance in the Cloud AlgoSec Cloud Mar 19, 2023 · 2 min read 5 Multi-Cloud Environments Cloud Security Mar 19, 2023 · 2 min read Convergence didn’t fail, compliance did. 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. Bt Streamlines Firewall Change Control And Proves Compliance Across Its Global Networks Organization BT Industry Telecom Headquarters London, UK Download case study Share Customer
success stories "AlgoSec now does the heavy lifting for us. It allows the engineers to focus more on providing greater levels of security than on process and change, so we’re able to provide a much more secure infrastructure for BT" Background A leading world-wide provider of communications services and solutions, BT serves customers in more than 170 countries. Its principal activities include the provision of networked IT services globally; local, national and international telecommunications services for use at home, at work and on the move; broadband, TV and internet products and services; and converged fixed/mobile products and services. Challenge BT’s internal network is a complex, highly segmented environment that has evolved over the last two decades throughout its worldwide locations. BT’s infrastructure relies on a large number of third-party domains and business-to-business connections with over 1,000 policy enforcement points, some of which date back a number of years.“The challenge facing BT is around the size of the estate, the complexity and our ability to demonstrate at audit that the rules within the policy are still appropriate, still valid, and still authorized,” says Phil Packman, General Manager of Security Gateway Operations for BT. “Equally, we’re challenged to ensure that rules don’t make it into the rulebase unless they’re approved and authorized.” BT therefore realized that it needed automation and reporting to better control its massive rulebase, and provide an approved audit trail to both auditors and internal stakeholders. Solution BT set about to solve its security challenges by creating a set of criteria for evaluating off-the-shelf, automated security solutions. “The criteria were based on ‘total costof ownership,’ our roadmap, and probably most importantly, the willingness of the partner to work with us,” says Packman. AlgoSec uniquely met BT’s requirements.Another feature BT liked was AlgoSec’s ability to prove that policies are implemented as approved. According to Packman, this was a capability “which we’d not seen in other products, and which we couldn’t achieve with our in-house tools.”AlgoSec’s commitment to customer success and its money-back guarantee were also deciding factors in BT’s selection process. Results Immediately after deployment, AlgoSec enabled BT to reduce error rates, make improvements to their rulebase implementation process and ultimately give BT better control over its network security. Packman explains: “Most notably, we were able to track down rogue connectivity, or connectivity that we didn’t understand properly. It gave us an almost immediate view of certain high-risk situations.”In addition, by using AlgoSec’s compliance reports, Packman’s engineering team were able to instantly demonstrate that no rules could be added to the firewall policy without proper approval — saving countless hours.Simplifying the audit preparation process led to a surprise benefit for BT’s Security Gateway Operations Team, which performs rule implementation and authorization: “AlgoSec has allowed us to change the skills profile of the team because the tool does the heavy lifting for us. Now our engineers can focus more on providing greater levels of security than on process and change, so we’re able to provide a much more secure infrastructure for BT.”Packman also endorses AlgoSec’s customer service, stating that the relationship has been a very positive one. “This has really helped put our minds at rest. We believe we’ve done the right thing in terms of deploying AlgoSec.”Using AlgoSec continues to enable BT to manage the complexity of its network with confidence, as it pursues growing and competitive global markets for its IT, computing, and communications services. Packman summarizes: “We have met every objective we hoped to achieve with AlgoSec.” Schedule time with one of our experts

Checklist for implementing security as code Download PDF Schedule time with one of our experts 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

Fortifying cloud security and HIPAA compliance for a global health services company Case Study Download PDF Schedule time with one of our experts 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

Modernize your network with Cisco Nexus and ACI solutions for enhanced performance, scalability, and security in your data center and cloud environments. Modernize your network with Cisco Nexus & ACI ---- ------- Schedule a Demo Select a size ----- Get the latest insights from the experts Choose a better way to manage your network

Partner solution brief Manage secure application connectivity within ServiceNow Download PDF Schedule time with one of our experts 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