Security Databases Ecosystem - Revision history

Cskallak: Cskallak moved page Enumeration Database Ecosystem to Security Databases Ecosystem

2020-01-16T17:40:41Z

Cskallak moved page Enumeration Database Ecosystem to Security Databases Ecosystem

← Older revision	Revision as of 17:40, 16 January 2020
(No difference)

Cskallak at 17:40, 16 January 2020

2020-01-16T17:40:21Z

← Older revision		Revision as of 17:40, 16 January 2020
Line 45:		Line 45:
	* CWE: https://cwe.mitre.org/index.html		* CWE: https://cwe.mitre.org/index.html
	* CAPEC: https://capec.mitre.org/index.html		* CAPEC: https://capec.mitre.org/index.html
			* [[File:Common Vulnerabilities and Exposures (CVE).pdf]]

	[[Category:Basic]]		[[Category:Basic]]

Cskallak at 17:34, 16 January 2020

2020-01-16T17:34:22Z

← Older revision		Revision as of 17:34, 16 January 2020
Line 7:		Line 7:
	Security databases categorize information of vulnerabilities, weaknesses or other cybersecurity related Topics. Every company had their own vulnerability database before MITRE started to build an interconnected database and only a portion of the organizations shared their information. MITRE developed in January 1999 a standardized enumeration system for vulnerabilities. The documentation of the enumeration system was written down in the paper “Towards a Common Enumeration of Vulnerabilities”. This enumeration system is seen known and used by many organizations today and set the foundation for various databases with other use cases.		Security databases categorize information of vulnerabilities, weaknesses or other cybersecurity related Topics. Every company had their own vulnerability database before MITRE started to build an interconnected database and only a portion of the organizations shared their information. MITRE developed in January 1999 a standardized enumeration system for vulnerabilities. The documentation of the enumeration system was written down in the paper “Towards a Common Enumeration of Vulnerabilities”. This enumeration system is seen known and used by many organizations today and set the foundation for various databases with other use cases.

	[[File:~~Example~~.jpg]]		[[File:Ecosystem.jpg\|200px\|thumb\|right\|Enumeration database ecosystem]]

	== Common Vulnerabilities and Exposures (CVE)==		== Common Vulnerabilities and Exposures (CVE)==

Cskallak at 17:31, 16 January 2020

2020-01-16T17:31:01Z

← Older revision		Revision as of 17:31, 16 January 2020
Line 1:		Line 1:
	== Summary ==		== Summary ==

	~~Description what this~~ documentation ~~is about~~		This documentation gives an introduction into the enumeration database ecosystem.

	== ~~Inrtoduction~~ ==		== Introduction ==

	Security databases categorize information of vulnerabilities, weaknesses or other cybersecurity related Topics. Every company had their own vulnerability database before MITRE started to build an interconnected database and only a portion of the organizations shared their information. MITRE developed in January 1999 a standardized enumeration system for vulnerabilities. The documentation of the enumeration system was written down in the paper “Towards a Common Enumeration of Vulnerabilities”. This enumeration system is seen known and used by many organizations today and set the foundation for various databases with other use cases.		Security databases categorize information of vulnerabilities, weaknesses or other cybersecurity related Topics. Every company had their own vulnerability database before MITRE started to build an interconnected database and only a portion of the organizations shared their information. MITRE developed in January 1999 a standardized enumeration system for vulnerabilities. The documentation of the enumeration system was written down in the paper “Towards a Common Enumeration of Vulnerabilities”. This enumeration system is seen known and used by many organizations today and set the foundation for various databases with other use cases.

			[[File:Example.jpg]]

	== Common Vulnerabilities and Exposures (CVE)==		== Common Vulnerabilities and Exposures (CVE)==
Line 20:		Line 22:
	CVE−YYYY −NNNN		CVE−YYYY −NNNN

	The CVE ID is a unique ~~identiﬁer~~ of the CVE. The YYYY part ~~deﬁnes~~ the year the CVE was assigned by a CVA or was published. The NNNN portion is a unique ~~identiﬁer~~ that gets set back to zero if the YYYY part gets incremented. The restriction of the NNNN portion to 4 digits was removed in 2014 to an unlimited number of digits.		The CVE ID is a unique identifier of the CVE. The YYYY part defines the year the CVE was assigned by a CVA or was published. The NNNN portion is a unique identifier that gets set back to zero if the YYYY part gets incremented. The restriction of the NNNN portion to 4 digits was removed in 2014 to an unlimited number of digits.


Line 32:		Line 34:


	== Common Attack Pattern Enumeration and ~~Classiﬁcation~~(CAPEC) ==		== Common Attack Pattern Enumeration and Classification (CAPEC) ==

	The Common Attack Pattern Enumeration and ~~Classiﬁcation~~ (CAPEC) is a database specialized on common attack patterns. CAPEC was released by MITRE in 2007 and gets hosted by the organization until today. The purpose of CAPEC is to understand how hackers exploit weaknesses in software. The ~~beneﬁts~~ of CAPEC are cybersecurity training and attacking tools for penetration testing.		The Common Attack Pattern Enumeration and Classification (CAPEC) is a database specialized on common attack patterns. CAPEC was released by MITRE in 2007 and gets hosted by the organization until today. The purpose of CAPEC is to understand how hackers exploit weaknesses in software. The benefits of CAPEC are cybersecurity training and attacking tools for penetration testing.

	== References ==		== References ==

	* https://~~wikipedia~~.org		* CVE: https://cve.mitre.org/index.html
	* https://~~google~~.~~com~~		* NVD: https://nvd.nist.gov/
			* CVSSv3.1: https://www.first.org/cvss/v3.1/specification-document
			* CWE: https://cwe.mitre.org/index.html
			* CAPEC: https://capec.mitre.org/index.html

	[[Category:Basic]]		[[Category:Basic]]

Cskallak at 17:24, 16 January 2020

2020-01-16T17:24:29Z

← Older revision		Revision as of 17:24, 16 January 2020
Line 16:		Line 16:
	* and References to Papers and other sources which address the vulnerability		* and References to Papers and other sources which address the vulnerability

	The CVE ID		=== The CVE ID ===

	CVE−YYYY −NNNN		CVE−YYYY −NNNN

Cskallak at 17:23, 16 January 2020

2020-01-16T17:23:33Z

← Older revision		Revision as of 17:23, 16 January 2020
Line 40:		Line 40:
	* https://wikipedia.org		* https://wikipedia.org
	* https://google.com		* https://google.com
	[[Category:~~Basics~~]]

			[[Category:Basic]]

Cskallak: Created page with "== Summary == Description what this documentation is about == Inrtoduction == Security databases categorize information of vulnerabilities, weaknesses or other cybersecuri..."

2020-01-16T17:21:37Z

Created page with "== Summary == Description what this documentation is about == Inrtoduction == Security databases categorize information of vulnerabilities, weaknesses or other cybersecuri..."

New page

== Summary ==

Description what this documentation is about

== Inrtoduction ==

Security databases categorize information of vulnerabilities, weaknesses or other cybersecurity related Topics. Every company had their own vulnerability database before MITRE started to build an interconnected database and only a portion of the organizations shared their information. MITRE developed in January 1999 a standardized enumeration system for vulnerabilities. The documentation of the enumeration system was written down in the paper “Towards a Common Enumeration of Vulnerabilities”. This enumeration system is seen known and used by many organizations today and set the foundation for various databases with other use cases.

== Common Vulnerabilities and Exposures (CVE)==

The Common Vulnerabilities and Exposures was published in September 1999 by MITRE. The initial list had 321 CVE entries. Today There are over 100.000 entries accessible for everyone. The CVE database was constructed to operate as trusted third party. Companies and individuals can send CVE entry requests which get checked by the CVE Numbering Authority. The CVE entry request than gets published on the CVE database. The CVE Entries are accessible for everyone.

A CVE entry consists out of:
* a CVE ID
* the Description
* and References to Papers and other sources which address the vulnerability

The CVE ID

CVE−YYYY −NNNN

The CVE ID is a unique identiﬁer of the CVE. The YYYY part deﬁnes the year the CVE was assigned by a CVA or was published. The NNNN portion is a unique identiﬁer that gets set back to zero if the YYYY part gets incremented. The restriction of the NNNN portion to 4 digits was removed in 2014 to an unlimited number of digits.

== The U.S. National Vulnerability Database (NVD) ==

The U.S. National Vulnerability Database (NVD) is also a Vulnerability Database launched by the National Institute of Standards and Technology (NIST) in 2000. The NVD is synchronized with the CVE Database which means that CVE entries get uploaded to the NVD as soon as they get published. The Team of the NVD add enhanced information to the entries such as the affected configurations and a severity score. The severity score is calculated threw the Common Vulnerability Scoring System (CVSS).

== Common Weakness Enumeration (CWE) ==

Common Weakness Enumeration (CWE) is also hosted by MITRE since 2008 and holds a list of common weaknesses. The difference between weaknesses and vulnerabilities is that weaknesses cause vulnerabilities. Du to the fact that weaknesses are hardware and software independent there are less of them and they are easy to categorize. The CWE ID is only four digits long and doesn’t have a year portion but they reference to parent or child weaknesses because they are organized in a tree like structure.

== Common Attack Pattern Enumeration and Classiﬁcation(CAPEC) ==

The Common Attack Pattern Enumeration and Classiﬁcation (CAPEC) is a database specialized on common attack patterns. CAPEC was released by MITRE in 2007 and gets hosted by the organization until today. The purpose of CAPEC is to understand how hackers exploit weaknesses in software. The beneﬁts of CAPEC are cybersecurity training and attacking tools for penetration testing.

== References ==

* https://wikipedia.org
* https://google.com
[[Category:Basics]]