all tags
Mackenzie Jackson, GitGuardian: “code security needs to be a layered approach”

Mackenzie Jackson, GitGuardian: “code security needs to be a layered approach”

Security should be something that companies implement into the software development lifecycle as early as possible. It should be a consideration at every step of development, from design and through to deployment and every incremental change made thereafter.

Documentation as a Killer Feature

Documentation as a Killer Feature

Julia recently joined GitGuardian to improve the product experience for Enterprise users. She explained to us how documentation could be an essential asset to achieve that objective and what drove her to become a Guardian in the first place.

GitGuardian is now SOC 2 Type I compliant

GitGuardian is now SOC 2 Type I compliant

Developed by the American Institute of CPAs (AICPA), SOC 2 defines criteria for managing customer data based on five “trust service principles”—security, availability, processing integrity, confidentiality, and privacy.

Data Breach: a 5 Steps Response Plan

Data Breach: a 5 Steps Response Plan

A data breach is one of the worst scenarios in today’s enterprise security. What’s your plan to remediate this kind of situation, minimize the impact, and ensure business continuity? Although there is no such thing as a one-size-fits-all tactic, the following steps are crucial to a positive outcome.

Start your journey to secrets-free source code

And keep your secrets out of sight

arrow-down