Not found in the indexed publications — check the official source.
The passages provided contain references to MIL-HDBK-61 (a configuration management handbook) and excerpts from its appendices and related documents, but they do not address a specific question about MIL-HDBK-61. Your question states only "MIL-HDBK-61" without identifying what you need to know about it. Please rephrase your question to ask about a specific topic, requirement, procedure, or application related to this handbook.
Unofficial — answered from indexed publication text, which may be incomplete or out of date. Your MAJCOM/unit supplement may be stricter. Verify the official PDF before acting or writing a finding.
DODI 5000.87 DAFI 63-150 (effective/current as of 2023-10-13)Federated Assurance Center portal [https://jfac.navy.mil]. (b) (Added)(DAF) Software security testing should be conducted in a development and test environment (see Military Handbook 61 Revision B (MIL-HDBK 61 Rev B, Department of Defense Handbook: Configuration Management Guidance) with SECTION 3: PROCEDURES 23DoDI5000.87_DAFI63-150 11 AUGUST 2021 vulnerabilities mitigated following AFI 17-101, Risk Management Framework (RMF) for Air Force Information Technology (IT) Systems, before a system is made operational. (T-1) Consider including security technical implementation guide (STIG) usage and vendor hardening guidance when using memorandum of agreements or service level agreements following DoDI 4000-19, Support Agreements, as implemented in Air Force Policy Directive (AFPD) 25-2, Support
No supplement passage retrieved — check the supplement chain on the pub page before citing.
No federal/DoD passage retrieved.