Skip to content

Commit 65bb763

Browse files
authored
Merge pull request #1273 from cncf/anvega-streamline-readme
Streamline and update README.md
2 parents ca315fd + c420884 commit 65bb763

File tree

1 file changed

+38
-87
lines changed

1 file changed

+38
-87
lines changed

README.md

+38-87
Original file line numberDiff line numberDiff line change
@@ -2,120 +2,77 @@
22

33
![Cloud Native Security Logo](/design/logo/cloud-native-security-horizontal-darkmodesafe.svg)
44

5-
<!-- markdown-link-check-disable -->
65
## Quick links
76

8-
- [Meeting Information](#meeting-times)
7+
- [Meeting Information](#meeting-information)
98
- [Slack Information](#communications)
10-
- [New Members](#new-members)
119
- [Members](#members)
1210
- [Working Groups](#working-groups)
13-
<!-- markdown-link-check-enable -->
1411

15-
## Objective
12+
## About Us
1613

17-
The CNCF Security Technical Advisory Group facilitates collaboration to discover and produce resources that enable
18-
secure access, policy control, and safety for operators, administrators,
19-
developers, and end-users across the cloud native ecosystem.
14+
The CNCF Security Technical Advisory Group facilitates collaboration to exchange and produce knowledge and resources for building security in the cloud native ecosystem.
2015

21-
## Background
16+
Cloud Native involves building, deploying, and operating modern applications in cloud computing environments, typically using open source. This complex ecosystem presents a technology risk landscape that demands rethinking application and information security through the lens of developer experience.
2217

23-
Cloud Native describes the building, deploying, and operating of modern applications in cloud computing environments, typically using open source. This complex ecosystem composed of different open source projects presents an increasingly complicated technology risk landscape.
24-
While there are several projects in the cloud native ecosystem that address trust, safety, and security in the dynamic interplay between the different layers of infrastructure and application services, the technological shift demands application and information security be rethought through the lens of developer experience as close to applying software engineering to design for security considerations in the effort to safeguard an integrated cloud native ecosystem as a whole.
18+
We aim to significantly reduce the probability and impact of attacks, breaches, and compromises. By empowering developers and operators to understand and manage the security posture of their systems, we strive to fulfill the promise of enhanced productivity and operational efficiency.
2519

26-
## Vision
20+
## Key Focus Areas
2721

28-
We believe in a future where the probability and impact of attacks, breaches, and compromises are significantly reduced. Where the most common risks of today are not just mitigated but made implausible. We believe developers and operators can be empowered to understand better and be reassured by the posture of the systems they build and run through the informed use of cloud technologies with clear
29-
understanding of responsibility and risks and the unlocked ability to validate that their architectural intent meets compliance and regulatory objectives.
30-
31-
<!-- cSpell:ignore sociotechnical -->
32-
There is a growing ecosystem of tools that promises to unlock developer productivity and operational efficiency. We strive to fulfill the human side of the sociotechnical equation to acceleration and attain that promise including:
33-
34-
1. Consumable system security architectures that account for the ever
35-
growing heterogeneity of systems and provides a framework to protect
36-
resources and data while servicing their users.
37-
2. Common lexicon and open source libraries that make it easy for developers
38-
to create and deploy apps that meet system security requirements.
39-
3. Common libraries and protocols that enable people to reason about the
40-
security of the system, such as auditing and explainability features.
22+
- **System Security Architectures**: Frameworks to protect resources and data.
23+
- **Common Lexicon, Templates & Libraries**: Tools for developers to create secure apps.
24+
- **Heuristics and Models**: Approaches for reasoning about system security.
4125

4226
## Publications
4327

44-
TAG Security has published several resources for the community, which can be
45-
found under [publications](publications/README.md).
28+
Below is a list of publications by TAG Security. For a comprehensive collection of our works in various formats, please visit the [publications](publications/README.md) directory.
29+
30+
| Publication | Date |
31+
|-------------|------|
32+
| [Formal Verification for Policy Configurations](https://github.com/cncf/tag-security/blob/main/policy/overview-policy-formal-verification.md) | August, 2019 |
33+
| [Catalog of Supply Chain Compromises](https://github.com/cncf/tag-security/tree/main/supply-chain-security/compromises) | November 2019 - Present |
34+
| [Software Supply Chain Best Practices](https://github.com/cncf/tag-security/raw/main/supply-chain-security/supply-chain-security-paper/CNCF_SSCP_v1.pdf) | May, 2021 |
35+
| [Evaluating your Supply Chain Security](https://github.com/cncf/tag-security/blob/main/supply-chain-security/supply-chain-security-paper/secure-supply-chain-assessment.md) | May, 2021 |
36+
| [Cloud Native Security Lexicon](https://github.com/cncf/tag-security/blob/main/security-lexicon/cloud-native-security-lexicon.md) | August, 2021 |
37+
| [Cloud Native Security Whitepaper](https://www.cncf.io/wp-content/uploads/2022/06/CNCF_cloud-native-security-whitepaper-May2022-v2.pdf) | May, 2022 |
38+
| [Cloud Native Security Controls Catalog](https://github.com/cncf/tag-security/blob/main/cloud-native-controls/phase-one-announcement.md) | May, 2022 |
39+
| [Handling Build-time Dependency Vulnerabilities](https://github.com/cncf/tag-security/blob/main/policy/overview-policy-build-time-dependency-vulns.md) | June, 2022 |
40+
| [Secure Software Factory: A Reference Architecture to Securing the Software Supply Chain](https://github.com/cncf/tag-security/raw/main/supply-chain-security/secure-software-factory/Secure_Software_Factory_Whitepaper.pdf) | May, 2022 |
41+
| [Secure Defaults](https://github.com/cncf/tag-security/blob/main/security-whitepaper/secure-defaults-cloud-native-8.md) | February, 2022 |
42+
| [Open and Secure - A Manual for Practicing Threat Modeling to Assess and Fortify Open Source Security](https://github.com/cncf/tag-security/blob/main/assessments/Open_and_Secure.pdf) | November, 2023 |
4643

4744
## Governance
4845

49-
[Security TAG charter](governance/charter.md) outlines the scope of our group
50-
activities, as part of our [governance process](governance/README.md) which details how we
51-
work.
46+
Refer to the [Security TAG charter](governance/README.md) for our governance process.
5247

5348
## Communications
5449

55-
Anyone is welcome to join our open discussions of Security TAG projects and share news
56-
related to the group's mission and charter. Much of the work of the group
57-
happens outside of Security TAG meetings and we encourage project teams to share
58-
progress updates or post questions in these channels:
59-
60-
Group communication:
50+
Join our open discussions and share news:
6151

6252
- [Email list](https://lists.cncf.io/g/cncf-tag-security)
6353
- [CNCF Slack](https://slack.cncf.io/) #tag-security channel
6454

65-
Leadership:
66-
67-
- To reach the leadership team (chairs & tech leads), email
68-
[cncf-tag-security-leads@lists.cncf.io](mailto:cncf-tag-security-leads@lists.cncf.io)
69-
- To reach the chairs, email [cncf-tag-security-chairs@lists.cncf.io](mailto:cncf-tag-security-chairs@lists.cncf.io)
70-
71-
### Slack governance
72-
73-
Refer to the [slack governance document](slack.md) for details on slack channels
74-
and posting to the channels.
75-
76-
## Meeting times
77-
78-
For our members in North and South America, we host weekly sessions each Wednesday at 10 am (UTC-7). To participate, simply use the following Zoom link: <https://zoom.us/j/99809474566>. The meeting ID is 998 0947 4566.
55+
## Meeting Information
7956

80-
Meanwhile, participants from Europe, the Middle East, and Africa (EMEA) can join bi-weekly meetings on Wednesdays at 1 pm UTC+0, which adjusts to UTC+1 when daylight saving time is in effect. Join us through this Zoom link: <https://zoom.us/j/99917523142>, with the meeting ID: 999 1752 3142.
57+
- **Americas**: Weekly on Wednesdays at 10 am (UTC-7). [Zoom link](https://zoom.us/j/99809474566), Meeting ID: 998 0947 4566.
58+
- **EMEA**: Bi-weekly on Wednesdays at 1 pm UTC+0 (adjusts for daylight saving). [Zoom link](https://zoom.us/j/99917523142), Meeting ID: 999 1752 3142.
8159

82-
To find the corresponding time in your local area, please see your timezone [here](https://time.is/).
60+
Check your local timezone [here](https://time.is/). Meetings are listed on the [CNCF calendar](https://www.cncf.io/calendar/) and the [TAG Security Calendar](https://calendar.google.com/calendar/u/0?cid=MGI4dTVlbDh0YTRzOTN0MmNtNzJ0dXZoaGtAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ).
8361

84-
This dual schedule ensures that no matter where you are, you'll have a place in our conversations.
85-
86-
We invite you to mark your calendars and join the dialogue. For your convenience, all meetings are listed on the main [CNCF calendar](https://www.cncf.io/calendar/) as well as the [TAG Security Calendar](https://calendar.google.com/calendar/u/0?cid=MGI4dTVlbDh0YTRzOTN0MmNtNzJ0dXZoaGtAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ). These calendars are updated regularly to ensure that you stay informed of all upcoming meetings and events.
87-
88-
Got something to bring up or share? Review how to get a topic or presentation added to the Agenda on our [process](governance/process.md#getting-on-the-agenda) page.
62+
To add a topic to the agenda, review our [process](governance/process.md#getting-on-the-agenda).
8963

9064
## Gatherings
9165

92-
Please let us know if you are going and if you are interested in attending (or
93-
helping to organize!) a gathering. Create
94-
a [github issue](https://github.com/cncf/tag-security/issues/new) for an event
95-
and add to list below:
96-
97-
<!-- markdownlint-disable-next-line MD013 -->
9866
- [Cloud Native SecurityCon 24](https://events.linuxfoundation.org/cloudnativesecuritycon-north-america/) June 26-27, 2024 in Seattle, Washington
99-
100-
[Past events](past-events.md)
67+
- [Past events](past-events.md)
10168

10269
## New members
10370

104-
If you are new to the group, we encourage you to check out
105-
our [New Members Page](NEW-MEMBERS.md)
71+
New to the group? Check out our [New Members](NEW-MEMBERS.md) page.
10672

10773
## Related groups
10874

109-
There are several groups that are affiliated to or do work and cover topics
110-
relevant to the work of Security TAG. These can be
111-
seen [here](governance/related-groups/README.md)
112-
113-
## History
114-
115-
- TAG-Security - renamed Security TAG ([TOC Issue 549](https://github.com/cncf/toc/issues/549))
116-
- SAFE WG - renamed to CNCF Security TAG
117-
- [(Proposed) CNCF Policy Working Group](/policy-wg-merging.md) - Merged into
118-
SAFE WG
75+
Explore groups affiliated with or relevant to Security TAG [here](governance/related-groups/README.md)
11976

12077
## Members
12178

@@ -152,15 +109,15 @@ seen [here](governance/related-groups/README.md)
152109
| Aradhana Chetal | TIAA | June, 2021 - September, 2023 | @achetal01 |
153110
| Andrew Martin | ControlPlane | March, 2022 - March, 2024 | @sublimino|
154111

155-
### Working groups
112+
### Working Groups
156113

157114
The TAG's working groups focus on specific areas and organize most community activities, including weekly meetings.
158115
These groups facilitate discussions, engagement, and publications with key stakeholders, operating differently based on their needs.
159116
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.
160117

161118
| Project | Leads |
162119
|---------------------------------|---------------------------------------------|
163-
| [Applied Research](/community/research/README.md) | Andrés Vega |
120+
| [Research](/community/research/README.md) | Andrés Vega |
164121
| [Automated Governance](/community/automated-governance/README.md) | Andrés Vega, Brandt Keller |
165122
| [Catalog of Supply Chain Compromises](/community/catalog/README.md) | Santiago Arias Torres |
166123
| [Compliance](/community/compliance/README.md) | Anca Sailer, Robert Ficcaglia |
@@ -172,15 +129,9 @@ Each group, led by a responsible leader, reaches consensus on issues and manages
172129

173130
### CNCF Security TAG reviews
174131

175-
As part of
176-
the [CNCF project proposal process](https://github.com/cncf/toc/blob/main/process)
177-
projects should create a
132+
For [CNCF project proposal process](https://github.com/cncf/toc/blob/main/process)
133+
create a
178134
new [security review issue](https://github.com/cncf/tag-security/issues/new?assignees=&labels=assessment&template=security-assessment.md&title=%5BAssessment%5D+Project+Name)
179135
with a
180136
[self-assessment](https://github.com/cncf/tag-security/blob/main/assessments/guide/self-assessment.md)
181137
.
182-
183-
### Past events and meetings
184-
185-
For more details on past events and meetings, please see
186-
our [past events page](past-events.md)

0 commit comments

Comments
 (0)