From 6e47a1717580240a7cfa09fce5704de293e03482 Mon Sep 17 00:00:00 2001 From: Spyros Date: Tue, 2 Jul 2024 21:27:41 +0100 Subject: [PATCH] Update README.md (#520) closes #489 Signed-off-by: Spyros --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 62c00272..f14a07d9 100644 --- a/README.md +++ b/README.md @@ -28,7 +28,7 @@ Independent software security professionals got together to find a solution for The CRE links each section of a standard to a shared topic (a Common Requirement), causing that section to also link with all other resources that map to the same topic. This 1) enables users to find all combined information from relevant sources, 2) it facilitates a shared and better understanding of cyber security, and 3) it allows standard makers to have links that keep working and offer all the information that readers need, so they don’t have to cover it all themselves. The CRE maintains itself: topic links in the standard text are scanned automatically. Furthermore, topics are linked with related other topics, creating a semantic web for security. Example: the session time-out topic will take the user to relevant criteria in several standards, and to testing guides, development tips, more technical detail, threat descriptions, articles etc. From there, the user can navigate to resources about session management in general. -WHEN? + Some of the data has been kindly contributed by the SKF and ASVS projects @@ -117,4 +117,4 @@ Please see [Contributing](CONTRIBUTING.md) for contributing instructions Roadmap --- -For a roadmap of what we would like to be done please see the [issues](https://github.com/OWASP/common-requirement-enumeration/issues). \ No newline at end of file +For a roadmap of what we would like to be done please see the [issues](https://github.com/OWASP/common-requirement-enumeration/issues).