Green-Software-Foundation / Green-Software-Foundation/writers

[Article] The Software Needed to Make Cybersecurity Green & Resilient

Open
#67 2 comments 0 reactions 0 assignees View on GitHub
articles blocked
Dominant language
No language data
Stars
2
Forks
1
PR merge metrics
No merged PRs in 30d

Description

## Article Details
_Please enter the details here_

**Proposer**: Namrata Narayan | Communications Lead at GSF | @NAMRATA-WOKE )
**Abstract**: Does going green mean losing resilience? Cybersecurity is a critical issue in today's digital world and a top priority for every CTO. This article brings together two topics and priorities rarely discussed in the same breath and considers the different tools and practices that can help reduce the carbon footprint of cybersecurity solutions while ensuring their resilience.
**Why**: This is an opportunity for GSF to address a priority area for CTOs at every organization undergoing a digital transformation -- especially valuable for companies in tech and finance. Can help demystify green software as it relates to critical concerns they're facing and help change culture.
**Audience**: CTOs/ Chief of Cyber Security / Global Heads of Sustainable Technology
**Timeline**: June or September

## Important Information
_To be filled out later_

**Author**: (Who is assigned to write this article)
**Other contributors**: (Experts, Reviewers)
**Article Link**: (Link to the doc, must be in our official GSF drive)
**Graphics Link**: (Link to the design assets for this article, must be in our official GSF drive)
**Published Link**: (The link the article was published to for memory)

## Checklist
- [ ] Idea discussed and selected for writing. _After checking this box, set Status to "Todo" under "Articles" project_
- [ ] Author identified. _After checking this box Assign issue to the Author_
- [ ] Google doc link created in GSF drive.
- [ ] In progress. _After checking this box, set Status to "In Progress" under "Articles" project_
- [ ] Draft created. _After checking this box, set Status to "In Review" under "Articles" project. Assign issue to Reviewer/Author during the back-and-forth_
- [ ] Draft reviewed. _After checking this box, set Status to "In Publishing" under "Articles" project. Assign issue to Graphic Designer and add "Graphic Design" to issue's Projects_
- [ ] Graphics created. _After checking this box, assign to TBC for approval._
- [ ] Approved. _After checking this box, assign to TBC for publishing._
- [ ] Published. After checking this box, set Status to "Ready" under "Articles" project. Assign to Marketing and add "D: Marketing" to issue's Projects
- [ ] Shared on socials
- [ ] Shared on newsletter. After checking this box, set Status to "Done" under "Articles" project and close issue.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the Article Details section and the abstract to define the article's scope, audience, and timeline. The issue names no code files or tests; use the checklist to track author assignment, drafting, review, graphics, publication, and sharing. Done means the article is published and the final checklist items are complete.

Written by the indexing model from the issue text.

Assessment

Domain
content
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.