Database Search Results

While not a delegation in the truest sense, the statute clearly instructs the Secretary on a specific requirement: informing the Chief of Mission. This directive falls under “Specific Authority” because it is a focused instruction about a particular regulatory task related to military operations and foreign relations. The language is mandatory (“may not authorize unless…”).

The statute outlines a requirement for the Secretary to inform the Chief of Mission before authorizing a military operation in the information environment. While 48 CFR Part 7 generally covers acquisition planning, including equipment acquisition, it doesn’t specifically address the notification requirements for military operations in the information environment outlined in 10 U.S. Code § 399. Therefore, the relationship is related in that both involve Department of Defense activities, but the regulation is neither directly mandated nor explicitly authorized by this specific statute.

While broad in scope (dealing with humanitarian and civic assistance), the statute explicitly instructs the agency (Secretary of Defense) to create regulations for a specific regulatory task – the carrying out of humanitarian and civic assistance activities in conjunction with military operations. It also lays out constraints regarding the purpose and nature of these activities, suggesting a narrowing of agency discretion. The authorization is cabined by the requirement that activities must promote the security interests of the US and the host country, and must build readiness skills of the armed forces.

10 U.S. Code § 401(a)(1) explicitly states, “Under regulations prescribed by the Secretary of Defense…”. This language directly mandates the Secretary of Defense to create regulations.

The statute specifically allows the Secretary of Defense to transport humanitarian supplies under certain conditions. It also directs the President to establish procedures for making determinations about the transportation of these supplies. This constitutes specific regulatory tasks and guidance, falling under the “Specific Authority Delegations” category, despite the use of broad terms such as “adequate arrangements,” the action and regulatory task is clear.

The statute authorizes the Secretary of Defense to transport humanitarian relief supplies and tasks the President with establishing procedures for determinations related to this transportation. 48 CFR Part 7 deals with acquisition planning generally. While the statute involves the Department of Defense and the transport of supplies, it does not directly mandate the specific acquisition planning detailed in 48 CFR Part 7. There may be an indirect relationship because acquiring the means to transport these supplies (planes, trucks, etc.) may involve acquisition planning, but the statute doesn’t explicitly require or authorize regulations related to acquisition planning as outlined in 48 CFR Part 7.

10 U.S.C. chapter 4 and chapter 137 provide broad rulemaking authority related to the organization and equipping of the armed forces and general acquisition policies, rather than specifying particular regulatory tasks.

While 10 U.S.C. § 403, before it was repealed, related to international peacekeeping activities, and 48 CFR Part 7 concerns acquisition planning, they are related in that acquisition planning could potentially involve activities related to international peacekeeping. However, the statute does not directly mandate acquisition planning for peacekeeping activities, nor does it explicitly authorize or forbid it. The regulation’s authority cites 10 U.S.C. chapter 4 and 137, which are broader grants of authority regarding the armed forces and acquisition.

While 10 U.S.C. chapter 4 and 10 U.S.C. chapter 137 are cited as authority for the regulation, these are broad areas of law dealing with military functions and acquisitions, rather than specific instructions related to how agencies must plan for acquisitions. They are providing broad rulemaking authority without specific regulatory tasks identified.

The statute authorizes foreign disaster assistance and allows for the provision of supplies and equipment. The regulation concerns acquisition planning, which could be related to acquiring the supplies and equipment needed for disaster assistance, but the statute does not directly mandate or explicitly authorize acquisition planning regulations.

Subsection (b)(1) of the statute explicitly instructs the Secretary of Defense to “establish and submit to the congressional defense committees procedures for complying with the requirements of subsection (a) consistent with the national security of the United States and the protection of operational integrity.” This is a specific regulatory task.

10 U.S. Code § 395 mandates notification procedures for sensitive military cyber operations. 48 CFR Part 7 concerns acquisition planning. While both relate to the Department of Defense, the statute does not directly mandate or explicitly authorize the regulation. The statute pertains to cyber operations, and the regulation pertains to acquisition planning.

The statute explicitly instructs the Secretary of Defense to establish procedures for complying with the notification requirements regarding cyber weapons, a specific regulatory task.

The statute mandates reporting procedures related to cyber weapons, while the regulation concerns general acquisition planning. While both relate to the Department of Defense, they are not directly mandated nor explicitly authorized by each other.

The statute provides explicit instructions regarding the creation of a position (Principal Information Operations Advisor) and very specifically defines the responsibilities assigned to that position. This level of detail and specific task assignment aligns with the definition of Specific Authority Delegations. Furthermore, the statute provides clear directions regarding the development of strategies, posture reviews, and reports, all falling under the realm of specific regulatory tasks.

The statute establishes a Principal Information Operations Advisor and outlines their responsibilities, including policy promulgation and coordination. While 48 CFR Part 7 concerns acquisition planning, which could indirectly relate to information operations if those operations require procurement of resources, the statute does not directly mandate or explicitly authorize this specific regulation. The regulation is a general one for DoD acquisitions, and this statute concerns a specific role within information operations.

10 U.S. Code § 398 specifically instructs the Secretary of Defense to perform particular actions, such as notifying congressional defense committees within 48 hours of any new MISO plan or a change in scope to an existing one, and to submit annual reports. It also includes a prohibition on clandestine operations designed to influence opinions and politics in the United States. These are detailed instructions and prohibitions, constituting a specific delegation of authority, even while using general terms like “appropriate” in relation to “any other elements the Secretary determines appropriate” to report.

10 U.S. Code § 398 relates to military information support operations and mandates reporting requirements to Congress. 48 CFR Part 7 governs acquisition planning. While both concern the Department of Defense, the statute does not directly mandate the regulation, nor is the regulation explicitly authorized by the statute. They are related insofar as both deal with aspects of DoD operations and resource allocation, but are distinct topics.

The statute provides specific instructions to the Secretary of Defense and Secretary of State. It directs them to establish a pilot program, create a list of suitable countries and criteria, establish coordination procedures, maintain performance metrics, and provide notifications to Congress. Although the statute employs terms like “appropriate” and gives discretion to the Secretaries in determining the national security interest and defining criteria, it still falls within the scope of specific authority delegations by clearly instructing the agency on specific regulatory tasks.

10 U.S. Code § 398a authorizes the Secretary of Defense, with the concurrence of the Secretary of State, to conduct a pilot program for sharing cyber capabilities with foreign partners. 48 CFR Part 7 concerns acquisition planning. While 10 U.S.C chapter 4 and 10 U.S.C chapter 137, cited as authority for 48 CFR Part 7, relate to the Department of Defense and acquisitions, neither directly mandates nor explicitly authorizes regulations specifically regarding the sharing of cyber capabilities with foreign partners as laid out in 10 U.S.C. § 398a.

The statute explicitly instructs the Secretary of Defense to designate executive agents, prescribe their roles and responsibilities, develop a biennial integrated plan with specific components (listing ranges, establishing priorities, defining architecture, certifying investments, etc.), and select a standard language for cyber event data. Even though it uses terms like “appropriate” assessments, the legislation identifies specific regulatory tasks and gaps.

The statute authorizes the Secretary of Defense to prescribe the roles, responsibilities, and authorities of the executive agents designated for cyber test and training ranges, including the development of a biennial integrated plan. While the statute mandates the creation of the executive agent roles and a plan, it does not directly mandate specific regulations found within the regulation, though it does authorize them.

The statute explicitly instructs the Secretary of Defense and other officials to establish positions, define their responsibilities (including cyber strategy implementation, budget review, and coordination), and designate personnel with specific qualifications. These are specific regulatory tasks, fitting within the “Specific Authority” delegation.

The statute, 10 U.S. Code § 392a, establishes the position and responsibilities of Principal Cyber Advisors within the Department of Defense. The regulation, 48 CFR Part 7, concerns acquisition planning. While cybersecurity capabilities, policies and programs under the purview of the Principal Cyber Advisors would almost certainly be acquired through the process described in 48 CFR Part 7, the statute doesn’t directly mandate or explicitly authorize the regulation, and the regulation is broader than just cyber acquisitions. There is some necessary connection, but not direct authorization nor mandate.

The statute specifically instructs the Secretary of Defense to establish procedures requiring cleared defense contractors to report network penetrations, outlines the required elements of such reporting, and offers guidance on the dissemination of information. While some discretion is left to the Secretary, the statute is very prescriptive regarding the what and the who, thus fitting the “Specific Authority” category.

10 U.S. Code § 393 explicitly mandates the Secretary of Defense to establish procedures for cleared defense contractors to report network penetrations, which is precisely what 32 CFR Part 236 addresses. The regulation’s authority section also explicitly cites 10 U.S.C. § 393.

The statute clearly instructs the Secretary of Defense to establish specific procedures for a narrowly defined task: reporting network penetrations by cleared defense contractors. The statute outlines the criteria and requirements for these procedures.

10 U.S. Code § 393 directly mandates the Secretary of Defense to establish procedures for cleared defense contractors to report network penetrations.

The statute provides broad authority to the Secretary of Defense to conduct military cyber activities or operations in cyberspace. While the statute does define “clandestine military activity or operation in cyberspace,” it doesn’t instruct the agency on a specific regulatory task or gap; rather, it provides broad rulemaking authority related to the conduct of military cyber activities.

The statute and regulation are related because both concern the Department of Defense. The statute discusses military cyber operations, while the regulation concerns acquisition planning, including equipment acquisition. However, the statute does not directly mandate the regulation, nor is the regulation explicitly authorized by the statute. The regulation is promulgated under separate authorities, namely 40 U.S.C. 121(c); 10 U.S.C. chapter 4 and 10 U.S.C. chapter 137 legacy provisions (see 10 U.S.C. 3016); and 51 U.S.C. 20113.

The authority cited in 48 CFR Part 7 includes broad provisions like “10 U.S.C. chapter 4 and 10 U.S.C. chapter 137 legacy provisions (see 10 U.S.C. 3016)” which generally concern the organization and powers of the Department of Defense, including acquisition authority. These are not specific delegations to regulate particular aspects of acquisition planning related to the reporting requirements of 10 U.S.C. § 386.

The statute mandates a report on security cooperation activities. While acquisition planning (the subject of the regulation) could be related to security cooperation activities insofar as those activities might involve acquiring goods or services, the statute does not mandate acquisition planning regulations, nor does it explicitly authorize regulations specifically on acquisition planning. The connection is indirect.

The statute instructs the agency on a specific regulatory task, which is to establish procedures for cyber incident reporting from operationally critical contractors. While the statute provides some discretion to the Secretary of Defense in designing these procedures, it clearly outlines the requirements that the procedures must include, such as designating contractors, rapid reporting, protection of trade secrets, and dissemination of information.

The statute explicitly mandates the Secretary of Defense to establish procedures for reporting cyber incidents, designating a component to receive these reports, and setting requirements for those procedures. 32 CFR Part 236 directly implements these mandates by establishing the DoD Defense Industrial Base Cybersecurity Activities and outlining the mandatory reporting procedures.

The statute provides specific instructions to the Secretary of Defense regarding the content and scope of the procedures to be established. For example, subsection (c) details “Procedure Requirements,” mandating inclusion of a process for designating and notifying operationally critical contractors, requiring rapid reporting of cyber incidents, specifying the content of those reports, mandating mechanisms for department assistance, and requiring protection of trade secrets. Although open-ended terms such as “reasonable protection” are used, the statute directs the agency on specific regulatory tasks.

The statute, 10 U.S.C. § 391, directly mandates the Secretary of Defense to establish procedures for cyber incident reporting by operationally critical contractors. The statute specifies numerous requirements for these procedures. This creates a direct mandate for regulatory action.

The statute mandates a specific report, detailing the evaluation of military departments’ support for the Cyber Command, based on requirements established by the Commander and validated by the Office of the Secretary of Defense. It also lays out specific elements that must be included in this evaluation. This represents a clear instruction on a specific task, making it a Specific Authority delegation, despite the statute using terms like “adequacy” which falls under the acceptable “open-ended” term.

10 U.S.C. § 391a mandates a report from the Commander of the United States Cyber Command to Congress. 48 CFR Part 7 concerns acquisition planning generally within the federal government. While cyberspace operations could involve acquisitions, there is no direct mandate or explicit authorization linking the reporting requirement in the statute to the acquisition planning regulations. They are related in that they both concern governmental functions and resource allocation, but the relationship is indirect.

The statute provides detailed instructions to the Secretary of Defense, the Under Secretaries, the Vice Chairman of the Joint Chiefs of Staff, and the Director of the National Security Agency, and other specified individuals regarding the establishment, structure, responsibilities, and reporting requirements of the Strategic Cybersecurity Program. It is directing agencies to specific tasks.

10 U.S.C. § 391b deals with strategic cybersecurity programs within the Department of Defense and mandates specific actions, responsibilities, and reporting requirements directly related to cybersecurity. The regulation 48 CFR Part 7 concerns acquisition planning. While cybersecurity programs may involve acquisitions, the regulation isn’t directly mandated by the statute, nor is it explicitly authorized by it; rather it is related, because any procurement would naturally have to follow general acquisition planning guidance.

10 U.S.C §381 specifically instructs the Department of Defense on the regulatory task of providing budget information on security cooperation programs and activities and reporting obligations to Congress. Although “to the extent practicable” provides some leeway, the statute’s language explicitly sets out the required reporting content and frequency. This level of detail aligns with Specific Authority.

10 U.S. Code § 381 mandates the DoD to submit a consolidated budget and semiannual reports to Congress. While 48 CFR Part 7 deals with acquisition planning, and cites 10 U.S.C. chapter 4 and 10 U.S.C. chapter 137 as authority, the statute doesn’t directly mandate or explicitly authorize the regulation. The regulation is related because the reports required under the statute would likely involve information related to acquisition planning, but the connection is indirect.

While 10 U.S.C. § 382 focuses on assigning responsibilities for execution and administration, it does so within the clearly defined area of security cooperation programs. The statute delineates specific regulatory gaps relating to resource allocation, execution of programs involving defense articles/training, and designation of responsibility within defense agencies. Though the statute uses broad terms like “maximum effectiveness, efficiency, and economy”, it does so within a relatively bounded context.

While 10 U.S.C. § 382 outlines responsibilities for security cooperation programs, it doesn’t directly mandate the specific acquisition planning regulations found in 48 CFR Part 7. However, the statute authorizes activities related to the provision of defense articles, military training, and other defense-related services, which would necessitate acquisition planning as detailed in the CFR. The CFR cites 10 U.S.C. chapter 4 and 10 U.S.C. chapter 137 as authorities, linking it to the broader framework within which 10 U.S.C. § 382 exists.

10 U.S.C. § 383 provides a specific regulatory task, requiring the Secretary of Defense to “maintain a program of assessment, monitoring, and evaluation in support of the security cooperation programs and activities of the Department of Defense.” The statute provides detailed requirements for what this program must entail, indicating a specific delegation of authority.

The statute and regulation are related in that both concern the Department of Defense, but the statute addresses security cooperation programs assessment, monitoring, and evaluation while the regulation concerns acquisition planning. The regulation’s authority cites broader statutes related to government contracting and does not specifically mention the assessment, monitoring, and evaluation of programs outlined in 10 U.S.C. § 383. Therefore, it is related but not directly mandated or explicitly authorized.

While the statute broadly mandates the creation of the Department of Defense Security Cooperation Workforce Development Program, it also clearly instructs the agency (Secretary of Defense) on specific regulatory tasks. The statute identifies gaps and then instructs the Secretary of Defense to create regulation to fill the gap. An example is subsection (c)(2) which instructs the Secretary of Defense to write regulation for a management information system for standardization of data collection concerning personnel within the security cooperation workforce. This is beyond general rulemaking authority.

The statute mandates the Secretary of Defense to carry out a program, and subsection (c)(2) and (d)(3), specifically instruct the Secretary to prescribe regulations related to the management information system and standardization of data collection concerning personnel within the security cooperation workforce. However, the statute does not prescribe the specific content of the regulations, but rather authorizes the Secretary to create them to achieve the broader goals of the statute.

The statute specifically instructs the Secretary of Defense on a regulatory task””supporting other agencies for foreign assistance programs””and outlines the conditions, limitations, and notification requirements for doing so. While the authority is broad in the sense of which programs can be supported, it’s specific in how the support is to be administered, including the “notice and wait” provision which mandates a detailed notification process to Congress.

10 U.S.C. § 385(a) authorizes the Secretary of Defense to support other departments and agencies for specific purposes, but it does not mandate that they do so. The statute uses the word “authorized,” indicating permissive, not mandatory, action.