segudev

17 ms·

1.
Avoiding Secrets Leaks: Practical Tips for SecOps Practitioners(blog.gitguardian.com)
2 points by segudev 3y ago|0 comments
2.
by segudev 3y ago
If the numbers look suspicious to you, I would suggest you check what is found more specifically about your company/organization. GitGuardian can provide an automatic audit of your company-specific leaks we found on GitHub. Just ask:
3.
Show HN: We've built SaaS-Sentinel, the Downdetector for supply chain breaches(blog.gitguardian.com)
7 points by segudev 3y ago|0 comments
4.
Show HN: Honeytoken – give attackers a taste of their own medicine(gitguardian.com)
3 points by segudev 3y ago|0 comments
5.
GitHub Exposed a Private SSH Key: What You Need to Know(blog.gitguardian.com)
4 points by segudev 4y ago|1 comments
6.
10M Secrets Discovered in GitHub in 2023, Exposed by 1.35M Authors (1 in 10)(gitguardian.com)
4 points by segudev 4y ago|0 comments
7.
Top Practices for Secure Software Development(blog.gitguardian.com)
1 points by segudev 4y ago|1 comments
8.
Code Confessions: Share Your Hardcoded Secret Horror Stories(shittysecrets.dev)
1 points by segudev 4y ago|0 comments
9.
by segudev 4y ago
I'm afraid I have to disagree. There are so many different needs it is impossible to discredit them so simply. I recommend that readers take inspiration from this model of maturity to see more clearly: https://www.gitguardi
10.
Secrets Horror Stories(shittysecrets.dev)
1 points by segudev 4y ago|0 comments
11.
Secrets Management Maturity Model(gitguardian.com)
2 points by segudev 4y ago|0 comments
12.
SOPS: A Comprehensive Guide(blog.gitguardian.com)
2 points by segudev 4y ago|0 comments
13.
10 Rules for Better Cloud Security(blog.gitguardian.com)
1 points by segudev 4y ago|0 comments
14.
by segudev 4y ago
Unfortunately, it's not as simple as that. Lots of secrets are "generic" (think of a DB user/password combination), meaning that you need to take into account the surrounding source code context to be able to determine i
15.
by segudev 4y ago
Indeed, last year we detected on average 84 AWS IAM creds for every 10k commits pushed to GitHub https://res.cloudinary.com/da8kiytlc/image/upload/v164614852...
16.
Lavarand(en.wikipedia.org)
1 points by segudev 4y ago|0 comments
17.
DMCA Takedown Notices on GitHub (2015-2022)(blog.gitguardian.com)
2 points by segudev 4y ago|0 comments
18.
GitHub Actions Security cheat sheet(blog.gitguardian.com)
1 points by segudev 4y ago|0 comments
19.
Security Comics(securityzines.com)
153 points by segudev 4y ago|19 comments
20.
GitHub Action Tutorial: Hardening Containers with Seccomp Filters(blog.gitguardian.com)
3 points by segudev 5y ago|0 comments
21.
Kubernetes Hardening Tutorial(blog.gitguardian.com)
2 points by segudev 5y ago|0 comments
22.
Data Breach: A 5 Steps Response Plan(blog.gitguardian.com)
2 points by segudev 5y ago|0 comments
23.
Kubernetes Network Hardening Tutorial(blog.gitguardian.com)
2 points by segudev 5y ago|0 comments
24.
Doggerland(en.wikipedia.org)
3 points by segudev 5y ago|0 comments
25.
Tip about Git Configs(blog.gitguardian.com)
1 points by segudev 5y ago|0 comments