Explore jobs
Find specific jobs
Explore careers
Explore professions
Best companies
Explore companies
In January 1999, David E. Mann and Steven M. Christey of The MITRE Corporation published “Towards a Common Enumeration of Vulnerabilities” at a workshop at Purdue University.
After the presentation of the whitepaper, the group that would become the CVE Editorial Board was created in May 1999 to pull the initial CVE List together.
The CVE List was officially launched for the public in September 1999.
In September 1999, the first CVE List was made public.
In September 1999, the first CVE List was made public. It also placed a booth at SANS 1999 to help introduce the List and promote its adoption.
Well, here is a link to our first CVE: CVE-1999–0007.
As quickly as December 2000 there were 29 organizations participating with declarations of compatibility for 43 products.
In the summer of 2000, MITRE put out a request for legacy vulnerability information with the intent of adding it to the CVE List.
Members of these organizations also helped form the CVE Editorial Board and later formed the CVE Senior Advisory Council in 2001.
Among other information, the report noted that by May of 2002, the CVE List had 2,032 entries, and CVE/MITRE was receiving 150 to 200 new CVE submissions each month.
Adoption of the CVE List was further boosted when NIST (National Institute of Standard and Technology) released its Special Publication 800-51 in 2002, where it recommended that United States agencies prefer the use of tools that use CVE Identifiers.
In June 2004, the United States Defense Information Systems Agency (DISA) issued a task order for information assurance applications that requires the use of products that use CVE IDs.
How is that possible? Actually, early participants weren’t labeled CNAs until February 1, 2005.
A well-known counterpart to CVE List, the National Vulnerability Database (NVD), was formed in 2005.
By 2018, CVE celebrated the addition of their 100th CVE Numbering Authority and further refined the CNA guidelines and CVE reporting schema.
In 2019, the CVE Board and the CVE Working Groups took on the challenge of updating the CNA Rules.
The phased quarterly transition process began on September 29, 2021 and will last for up to one year.
Rate CVE Group's efforts to communicate its history to employees.
Do you work at CVE Group?
Is CVE Group's vision a big part of strategic planning?
| Company name | Founded date | Revenue | Employee size | Job openings |
|---|---|---|---|---|
| Office Images | 1985 | $38.4M | 24 | 3 |
| Armchem International | 1982 | $10.6M | 10 | - |
| AndrewsPTS Electronics | - | $5.9M | 23 | - |
| PCNA | 2000 | $480.0M | 1,100 | 30 |
| ENSIGN EMBLEM | - | $580,000 | 50 | - |
| MFJ Enterprises | 1972 | $420,000 | 2 | - |
| Elite Lighting | 1998 | $7.0M | 125 | - |
| Halpin's Carpet Inc | 1974 | $7.9M | 35 | - |
Zippia gives an in-depth look into the details of CVE Group, including salaries, political affiliations, employee data, and more, in order to inform job seekers about CVE Group. The employee data is based on information from people who have self-reported their past or current employments at CVE Group. The data on this page is also based on data sources collected from public and open data sources on the Internet and other locations, as well as proprietary data we licensed from other companies. Sources of data may include, but are not limited to, the BLS, company filings, estimates based on those filings, H1B filings, and other public and private datasets. While we have made attempts to ensure that the information displayed are correct, Zippia is not responsible for any errors or omissions or for the results obtained from the use of this information. None of the information on this page has been provided or approved by CVE Group. The data presented on this page does not represent the view of CVE Group and its employees or that of Zippia.
CVE Group may also be known as or be related to CVE Group, CVE Group Inc, CVE Group, Inc., CVE Technology Group, Inc. and Cve Technology Group Inc.