Over time more and more guidelines have been written.
It now is clear that there is no "naming convention" on the titles of the guidelines:

Make a convention such that:

• The title only states what the guideline is about (avoid having the word "guideline" in the title itself)

Rendering on phone or on "narrow" windows cuts away the menu on the left. And this makes it quite difficult to figure out what page to go next, (until you open the menu on the left side, but I tested it on the phone and it is annoying)

Maybe we should add "Next page" and "Previous page" links at the bottom of each page. Ideally this should be done automatically, but it depends on how much effort this will require

Add a AppSec related security guideline to the docs/resources/guidelines area.

There should be a LICENSE.md file in the repo.

Add more learning material in Learning Material related to appsec

Update Guideline - Logging and Error Handling with more information and guidance

Add some examples of security requirements to Security Requirements.

This would be guidance for modern development-teams on how to create SRs for their solution.

Ex.
Show how to derive security requirements from functional requirements.
Show how to use ASVS to help with defining security requirements.

Expand on Security Tools with more tools related to AppSec and maybe some resources

The link to the Snyk guidelines

Expand Security Testing with information about IAST and RASP

Reading through the FAQ it, among others, has a question about the Kick Off Meeting - which was last year.
Should be updated to ask for SC-related events/meetups.

Consider if there are other questions one could ask and answer too.

Update Guildeline - Api Security with more information and guidance

I enjoyed reading the straight forward guide on how to enable signed commits.

If possible, please add any management system references for why you recommend this on github repositories that already require MFA for pushing commits and authorization on the repository level for writing commits.

I.e. something related to "zero trust" and that we shouldn't even trust our team members from creating forged commits.

Enhance the guideline on secure coding by adding a section about securely processing files.

Addressing this issue requires some internal knowledge, so it's not really a good first issue.

Mention that the Core Group exists (with link to the internal sharepoint), and what are the group's responsibilities

Also fix the https://appsec.equinor.com/security-champion/getting-in-touch/ page, cause it talks about "representative" but what really is meant here is the Core Group

A lot have changed in the past year, and the content of the page is not necessarily up-to-date and coherent. Someone should bother going through all the pages we have here, and if errors or inconsistencies are found, create dedicated issues (or fix them right away)