Skip to content
This repository was archived by the owner on Jun 23, 2026. It is now read-only.

Commit c0bfcdd

Browse files
chore(security): daily update 2026-06-23
1 parent ae6063b commit c0bfcdd

5 files changed

Lines changed: 29404 additions & 389 deletions

File tree

tracks/security/data/normalized.json

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,30 @@
11
[
2+
{
3+
"id": "72e19c51abe59df1",
4+
"track": "security",
5+
"source": "rss:aws-security-blog",
6+
"source_kind": "rss",
7+
"url": "https://aws.amazon.com/blogs/security/prevent-data-exfiltration-aws-egress-controls-for-cloud-workloads/",
8+
"title": "Prevent data exfiltration: AWS egress controls for cloud workloads",
9+
"summary": "When securing an Amazon Web Services (AWS) environment, teams naturally prioritize inbound controls, firewalls, WAFs, and access policies, because that’s where the most visible threats originate. Outbound traffic, on the other hand, tends to get less attention. It’s often left open by default to avoid breaking application dependencies and because the risk feels less immediate. […]",
10+
"published_at": "2026-06-22T15:53:05+00:00",
11+
"fetched_at": "2026-06-23T09:31:01.092243+00:00",
12+
"tags": [
13+
"Advanced (300)",
14+
"Amazon GuardDuty",
15+
"Amazon Route 53",
16+
"AWS Network Firewall",
17+
"AWS Security Hub",
18+
"Best Practices",
19+
"Security, Identity, & Compliance",
20+
"Technical How-to",
21+
"Resolver DNS Firewall",
22+
"Security Blog"
23+
],
24+
"severity": null,
25+
"score": 0.0,
26+
"score_breakdown": {}
27+
},
228
{
329
"id": "f6b44a85a3a61242",
430
"track": "security",
Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
[]

0 commit comments

Comments
 (0)