; 129 Stat. 1118). (c) Technologies The technologies described in this subsection are the following: (1) Technology developed and used by Combat Support Agencies of the Department of Defense to discover flaws and weaknesses in software code by inputting immense quantities of pseudo-random data (commonly referred to as fuzz ) to identify inputs that cause the software to fail. (2) Cloud-based software fuzzing-as-a-service to continuously test the security of Department of Defense software repositories at large scale. (3) Formal programming and protocol language for software code development and other methods and tools developed under the High Assurance Cyber Military Systems program of the Defense Advanced Research Projects Agency. (4) The binary analysis and symbolic execution software security tools developed under the Cyber Grand Challenge of the Defense Advanced Research Projects Agency. 1633. Comply to connect and cybersecurity scorecard (a) Limitation After October 1, 2019, no funds may be obligated or expended to prepare the cybersecurity scorecard for the Secretary of Defense unless the Department of Defense is implementing a funded capability to meet the requirements— (1) established by the Chief Information Officer and the Commander of United States Cyber Command pursuant to section 1653 of the National Defense Authorization for Fiscal Year 2017 ( Public Law 114–328 ; 10 U.S.C. 2224 note); and (2) set forth in the Information Security Continuous Monitoring Strategy, the Comply-to-Connect Strategy, the Enterprise Patch Management Service Strategy and Concept of Operations, and the User Activity Monitoring Strategy. (b) Report Not later than January 10, 2019, the Director of Cost Assessment and Program Evaluation shall submit to the congressional defense committees a report comparing the current capabilities of the Department of Defense to— (1) the requirements described in subsection (a)