CWE_Industry_Question_and_Response_2017.pdf

PDF 272 KB Posted

Attached to
Modeling and Simulation Contract (MASC) Small Business Setaside
Solicitation number
HQ0147-16-R-0022
Issued by

About this file

CWE Industry Question and Response 2017

View the file

Other files

File Type Posted
CLM_PR_CR_2_PEELS.pdf PDF
Vol_9_OPTISIG_Acceptance_Test_Report_900RPT2256__RevC.pdf PDF
Environment_Test_Harness_Requirements_20150731_final.pdf PDF
KIDD_User_manual.pdf PDF
Truth-Requirements-Document--2015.12.31--1200_3.7.2.2_Environment_States.pdf PDF
MS_T2D_SRD_Version_4.2_Aug2015.pdf PDF
CTM_3rd-Party_Software_List_rev3_04aug17.pdf PDF
MDA_Directive_8315.03_Modeling_and_Simulation_Program_Dec2015.pdf PDF
Truth-Requirements-Document--2015.12.31--1200_3.7.2.4_Lethality.pdf PDF
Vol_4_Thermophysical_Properties_Handbook_900MAN2251_RevB.pdf PDF
DODI_8500.01_Cybersecurity_2014.pdf PDF
DODM_5000.04-M-1_Cost_and_Software_Data_Reporting_CSDR_Manual_Nov2011.pdf PDF
MS_SRD_PAA_Phase_3_D4_Ground_Test_Venue_Oct2014.pdf PDF
Information_Exchange_Requirements_for_GTISS_(Draft)_Jan2017.pdf PDF
Vol_1_OSC_BASIC_Option_Reference_Manual_900MAN2248_RevC.pdf PDF
MDA_Directive_8315.01_MS_VVA_w_CH1_Apr2011.pdf PDF
CLM_PR_CR_2_PEGEM.pdf PDF
Truth-Requirements-Document--2015.12.31--1200_3.7.2.1_Signatures.pdf PDF
MITRE_Common_Weakness_Enumeration_v2.10.pdf PDF
MITRE_Corp_2011_CWE_SANs_Top_25_Most_Dangerous_Software_Errors_v1.0.3.pdf PDF
Vol_7_OPTISIG_User_Manual_and_ICD_900MAN2254_RevC.pdf PDF
Vol_2_OSC_Example_Cases_900MAN2249_RevA.pdf PDF
Vol_5_BALIS3_Users'_Manual_900MAN2252_RevB.pdf PDF
PEELS_Executive_Summary.pdf PDF
OSC_OPTISIG_Seminar_2016.pdf PDF
OWASP_Top_10_2013.pdf PDF
MS_Intended_Uses_Description_Document_20_Apr_2015_DE_Signed.pdf PDF
NIST_SP_800-53_Rev4_Security_and_Privacy_Controls_for_Federal_Information_Systems_and_Organizations.pdf PDF
PEGEM_Users_Manual.pdf PDF
DRAFT_List_of_Artifacts_to_be_transferred_to_MASC-T.pdf PDF
CTM_Capabilities_Summary.pdf PDF
PEGEM_Executive_Summary.pdf PDF
DODI_8530.01_Cybersecurity_Activities_to_Support_DoD_Network_Operations.pdf PDF
CTM-Definitions-List_-_All_Categories--2013.07.16.pdf PDF
CTM_Visual_Charts__2013.03.18.pdf PDF
Vol_8_OPTISIG_Algorithm_Notes_900RPT2255_RevA.pdf PDF
Truth-Requirements-Document--2015.12.31--1200_3.7.2.3_Environment_Effects.pdf PDF
CTM-Taxonomy--2013.06.19.pdf PDF
KIDD_Executive_Summary.pdf PDF
Vol_6_DIPREF_Theory_Manual_900MAN2253_RevA.pdf PDF
IMAP_v15.3_Vol_I_2015-12-15_Signed.pdf PDF
Historical_Hours_Worked_For_OSC_OPTISIG_and_Truth_Interaction.pdf PDF
NIST_SP_800-37_Rev_1_Applying_RMF_to_Federal_Information_Systems.pdf PDF
DODI_8510.01_Risk_Management_Framework_for_DoD_Informatin_Technology_CH1.pdf PDF
DODI_5000.02_Operation_of_the_Defense_Acquisition_System_CH2.pdf PDF
MASC-T_Historical_Information.pdf PDF
IMTP_v18.1_Smart_Book_20170324_Revision_-_Final_1.pdf PDF
Vol_3_OSC_Acceptance_Test_Report_900RPT2250_RevA.pdf PDF
Truth_Model_List.pdf PDF
CLM_PR_CR_2_KIDD.pdf PDF
Show 40 more

Latest 50 of 56 listed here. See the rest on GovTribe.

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Can government please provide a list of the anticipated “CWE (Common Weakness Enumeration), CVE (Common Vulnerabilities & Exposures), OWASP (Open Web Application Security Project) provided by the Government” to assess the potential cost impacts associated with migrating to complete compliance to CWE, CVE, and OWASP?

1. Yes, we have added some documentation to the bidder’s library specifically the Common Weakness Enumeration (CWE) Version 2.10 dated 19 Jan 2017 developed by the MITRE Corporation in support of the US Department of Homeland Security.

Additionally, the link to the Common Weakness Enumeration website is:

https://cwe.mitre.org/data/ This website contains the CWE/SANS Institute Top 25 for 2011, OWASP Top Ten for 2013 and also specific secure coding standards for specific software to include Java and C++. Both of these items have also been added to the bidder’s library for reference.

2. Common Vulnerabilities and Exposures (CVE®) is a dictionary of common names (i.e., CVE Identifiers) for publicly known cybersecurity vulnerabilities. CVE's common identifiers make it easier to share data across separate network security databases and tools, and provide a baseline for evaluating the coverage of an organization’s security tools. If a report from one of your security tools incorporates CVE Identifiers, you may then quickly and accurately access fix information in one or more separate CVE-compatible databases to remediate the problem.

CVE was launched in 1999 when most information security tools used their own databases with their own names for security vulnerabilities. At that time there was no significant variation among products and no easy way to determine when the different databases were referring to the same problem. The consequences were potential gaps in security coverage and no effective interoperability among the disparate databases and tools. In addition, each tool vendor used different metrics to state the number of vulnerabilities or exposures they detected, which meant there was no standardized basis for evaluation among the tools. CVE’s common, standardized identifiers provided the solution to these problems. CVE is now the industry standard for vulnerability and exposure names.

To have access to the dictionary for Common Vulnerabilities & Exposures (CVE) you can go to the website: https://cve.mitre.org/ https://cwe.mitre.org/data/ https://cve.mitre.org/

File details come from the government source that posted it. Updated .