Skip to content

Commit dec5738

Browse files
committed
Linting
Signed-off-by: Andrés Vega <av@messier42.com>
1 parent 443d5c0 commit dec5738

File tree

3 files changed

+5
-7
lines changed

3 files changed

+5
-7
lines changed

README.md

+2-5
Original file line numberDiff line numberDiff line change
@@ -129,7 +129,6 @@ seen [here](governance/related-groups/README.md)
129129
| Marina Moore | Independent | October, 2023 - October, 2025 | @mnm678 |
130130
| Eddie Knight | Sonatype | May, 2024 - May, 2026 | @eddie-knight |
131131

132-
133132
### Tech Leads
134133

135134
| Name | Organization | Handle |
@@ -141,7 +140,6 @@ seen [here](governance/related-groups/README.md)
141140
| Michael Lieberman | Kusari | @mlieberman85 |
142141
| John Kjell | TestifySec | @jkjell |
143142

144-
145143
### Security TAG Chair Emeriti
146144

147145
| Name | Organization | Term | Handle |
@@ -154,11 +152,10 @@ seen [here](governance/related-groups/README.md)
154152
| Aradhana Chetal | TIAA | June, 2021 - September, 2023 | @achetal01 |
155153
| Andrew Martin | ControlPlane | March, 2022 - March, 2024 | @sublimino|
156154

157-
158155
### Working groups
159156

160-
The TAG's working groups focus on specific areas and organize most community activities, including weekly meetings.
161-
These groups facilitate discussions, engagement, and publications with key stakeholders, operating differently based on their needs.
157+
The TAG's working groups focus on specific areas and organize most community activities, including weekly meetings.
158+
These groups facilitate discussions, engagement, and publications with key stakeholders, operating differently based on their needs.
162159
Each group, led by a responsible leader, reaches consensus on issues and manages logistics. All materials, such as reports, white papers, documents, and reference architectures, are in the repository's /community directory.
163160

164161
| Project | Leads |

community/compliance/README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
Compliance Working Group
1+
# Compliance Working Group
22

33
Cloud Native systems shift technical and human workflows. The community has researched cloud native security, tackling software vulnerabilities, risk management, dependencies, GitOps, supply chain provenance, malicious attacks, threat models, and security assessments. Organizations must comply with privacy and data protection laws, ensuring compute and data integrity. These concerns require both technical configurations and complex human orchestration, especially for audits needing reviewable artifacts.
44

community/controls/README.md

+2-1
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,8 @@
22

33
## Overview
44

5-
The controls catalog ensures the usability of CNCF deliverables by GRC professionals and Auditors of Cloud Native systems. The primary goal is to support quickly identifying the controls status of cloud-native environments, and methods to share the output of those assessments in machine readable formats (OSCAL, JSON, etc.). These outputs should also map to existing frameworks and regulations (CSA, NIST, FedRAMP, SOX, GDPR, etc.), and provide guidance to properly validate and verify administrative and technical controls.
5+
The controls catalog ensures the usability of CNCF deliverables by GRC professionals and Auditors of Cloud Native systems. The primary goal is to support quickly identifying the controls status of cloud-native environments, and methods to share the output of those assessments in machine readable formats (OSCAL, JSON, etc.).
6+
These outputs should also map to existing frameworks and regulations (CSA, NIST, FedRAMP, SOX, GDPR, etc.), and provide guidance to properly validate and verify administrative and technical controls.
67

78
## Impact
89

0 commit comments

Comments
 (0)