Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Add Your Own Custom Secrets Detectors To GitGuardian

Did you know you can add custom detectors to make GitGuardian Secrets Detection even more powerful? GitGuardian already looks for over 390 different types of specific secrets - from Adobe and AWS keys to Zoom and Zendesk Tokens. That's on top of looking for over a dozen generic patterns like Bearer tokens and JSON web tokens. Now, anyone on a Business plan or higher can request to extend GitGuardian's secrets detection engine to support detectors specific to their organization.

Real-time Security Alerts via Microsoft Teams

Prioritizing the security of your Kubernetes environment is of utmost importance. As organizations increasingly rely on containerization for their applications, the need for robust security measures is ever-growing. But security doesn’t work in isolation; it should seamlessly blend into your workflow. This is where the integration of ARMO Platform with collaboration tools like Microsoft Teams becomes invaluable.

DevSecOps101: To Do or Not To Do

DevSecOps, a progression from DevOps, involves embedding security practices throughout the software development process. It emphasizes collaborating, automating, and continuous monitoring to ensure efficient delivery of secure and reliable software. We explore concepts of DevSecOps such as: We review the case of Fannie Mae, who embraced DevSecOps and succeeded in improving collaboration, reduced vulnerabilities, and accelerated software development.

Office Hours: Insights - Focus on Top RIsks

We recently announced Insights, a unique capability providing organizations with code to cloud application intelligence that enables development and security teams to manage their application security posture more effectively by identifying, prioritizing, and fixing those issues posing the greater risk. Watch: What Insights is How to access Insights How to use Insights Watch if you are interested in using Insights, have started, or work as an engineer, developer, or in DevOps.

Software Supply Chain Security: The Basics and Four Critical Best Practices

Modern enterprise software is typically composed of some custom code and an increasing amount of third-party components, both closed and open source. These third-party components themselves very often get some of their functionality from other third-party components. The totality of all of the vendors and repositories from which these components (and their dependencies) come make up a large part of the software supply chain.

Navigating Chaos: JFrog Security Essentials and Advanced Security

We examine fundamental shifts and changes to software development approaches and how we secure developers, the code they write, and the products they build. Learn how your development teams can prioritize critical vulnerable exposure (CVE) remediation, maintain granular, centralized, and complete control of the development process, and maintain a single source of truth from code to device.

How Software Supply Chain Security Regulation Will Develop, and What Will It Look Like?

The escalation of international legislative interest in regulating the software supply chain has led to an increasing likelihood that tools such as software bills of materials (SBOMs) and AppSec solutions will become essential for companies doing business in the public sector or in highly regulated industries. However, the process of building and enforcing effective regulations presents challenges as well.