DDS to transfer counter-drone capabilities to Air Force

The Defense Digital Service (DDS) is planning to transfer its technologies to sense and detect small unmanned aerial systems (sUAS) to the Air Force Research Lab at the end of the month, FedScoop has learned.

AFRL’s NINJA  counter-sUAS program will absorb DDS’s drone-sensing capabilities, including its high-fidelity long-range sensor and user interface for integrating sensors, by Sept. 30, a DDS spokesperson told this publication.

The transition comes after the two organizations signed a memorandum of understanding in April to collaborate on counter-sUAS work.

DDS was developed as a testbed for innovative technologies at the Department of Defense. New systems are tested there before being transferred to a more permanent home — as will happen in this case with AFRL. DDS hopes that moving its counter-sUAS sensor capabilities to the Air Force will allow the program to “thrive and evolve” with continued development, procurement strategy and temporary sustainment of the products until a program of record is identified, according to the spokesperson.

“One of DDS’s superpowers is the ability to rapidly build, buy and deploy the best in technology that can be scaled to meet the needs of the DOD and the broader defense community,” said Katie Olson, acting director of DDS, in a statement. “Since adding CUAS as a portfolio in early 2020, our technical experts have been able to rapidly test and deliver best-in-class capabilities that support the warfighter’s need for real-time detection and tracking of CUAS threats for mitigation. Transitioning these capabilities to AFRL enables their evolution and growth and allows them to continue to support and modernize the DOD defensive posture.”

During the early days of the pandemic, DDS was noted for using its sUAS detection capabilities in helping secure the Navy’s COVID-19 floating hospitals off the coasts of New York and Los Angeles.

DDS, led by its Rogue Squadron team, will continue to work in the counter-sUAS space with a focus on rapid response while maintaining the partnership with AFRL for any sensing and detection needs.

The Air Force’s NINJA program — short for Negation of Improvised Non-State Joint Aerial system — is “a fielded, affordable, and software-adaptable system capable of taking control of or disabling” inexpensive, commercially available drones. The Air Force is looking to move NINJA into a program of record in the near future.

Air Force Research Lab earlier this year issued a request for proposals for a $490 million contract looking for businesses that can help prototype counter-sUAS technology.

Industry groups press DOD for more information on CMMC

A collection of government contractor trade groups say the lack of information about the new Cybersecurity Maturity Model Certification from the Department of Defense could soon have serious financial implications for the companies they represent.

In a letter sent Wednesday to Deputy Secretary of Defense Kathleen Hicks, three industry groups asked for more communication with industry and support for small business trying to comply with the new cyber regime, among other recommendations. The missive was sent jointly by the National Defense Industry Association, the Professional Services Council and Information Technology Industry Council.

The organizations warn that without action from the department, the cost of doing business with the DOD will increase and ultimately hurt the government’s ability to make purchases as companies are forced out of the market and the costs carried to the government increase.

“Currently, our collective members are facing critical decision points that will impact their budgets, strategic planning, and resource allocation without the benefit of knowing the status of DoD cybersecurity policy implementation,” the groups wrote in the letter. “Further, the continued proliferation of federal cybersecurity requirements at the agency level compounds this uncertainty as it remains unclear how DoD requirements will align with those required by other federal agencies.”

CMMC is DOD’s attempt to increase the cybersecurity of its industrial base. The program hinges on a verification model in which contractors must meet one of five tiers of cybersecurity controls, determined by the sensitivity of information they handle. By fiscal 2026, the department plans to require any contractor to have paid for an assessment of their network that would verify its compliance.

The potential costs of preparing for and getting an assessment could be high, especially for small business with tight margins. Some have estimated it could cost more than $100,000, but many business leaders remain uncertain due to a lack of communication from the department and other groups implementing the program.

Many of the complaints raised in the letter have been aired before, including in congressional testimony. But now companies are facing the dilemma of planning their futures against a regulation many still have questions about. There is also particular concern with an ongoing review of the program that was supposed to be concluded by, but DOD has yet to release any of its findings.

“The lack of clarity during the review process has increased uncertainty throughout the DIB and among commercial vendors seeking to provide covered commercial items,” the letter states.

The letter also brought up a foundational issue to CMMC, defining what exact constitutes controlled unclassified information (CUI). Policy on CUI is set by the National Archives and Records Administration, but the industry groups are asking DOD to be more specific about what information constitutes CUI and what protections need to be taken.

“[T]he Department must still provide detailed guidance regarding the type of information to be protected and should continue to collaborate with contractors and subcontractors that generate DoD CUI,” the letter states.

The groups made six suggestions to DOD:

  • Regularly engage with industry
  • Standardize and improve the marking practices for DoD CUI requiring protection
  • Harmonize CMMC and related contractual clauses with existing and future cybersecurity directives
  • Clarify Inter-Governmental Authorities for Implementing CMMC and Related Cybersecurity Requirements
  • Provide additional implementation guidance and support for small businesses
  • Evaluate and clarify remaining policy and process questions around the implementation of [Defense Federal Acquisition Regulation]

Microsoft combines federal team with Azure cloud unit

Microsoft is set to combine its U.S. federal arm with its Azure cloud team and create a new subsidiary as part of a reorganization of the technology giant’s U.S. public sector operation.

In an email to staff Wednesday, Judson Althoff, executive vice president and chief commercial officer, announced the plans, citing the company’s experience with the Pentagon’s Join Enterprise Defense Infrastructure (JEDI) and other contracts and the need to bring its engineering and business teams together to better serve the federal market.

“Through our direct experience with JEDI and other similar initiatives, we know that working with the U.S. federal government requires the ability to deliver highly customized solutions. Our experience has also taught us the tremendous value of bringing our engineering team and our U.S. federal business unit closer together,” Althoff said in the internal memo, obtained by FedScoop.

Althoff wrote that the company will move its federal team into its engineering organization and “effective October 1, the U.S. Federal team will begin operating as its own subsidiary.”

Microsoft Federal provides cloud solutions to departments and agencies across the federal government, as well as Congress and the federal courts. It has worked with military and intelligence organizations to provide cloud solutions, including the DOD365 platform used by the Department of Defense.

Azure is overseen by Executive Vice President Jason Zander, who first joined the company as a software engineer and has been with Microsoft for nearly 30 years. Azure is the technology company’s flagship cloud product and is part of its cloud and AI division, which focuses on providing infrastructure-as-a-service and software-as-a-service tools for clients.

Earlier this year Microsoft launched Azure Government Top Secret, which is accredited to meet intelligence community security directives and includes air-gapped regions for use with classified workloads.

Azure was first launched by Microsoft in January 2010, as the technology company raced to take advantage of growing interest in internet-based software and services. At the time, it also sought to catch up with competitors Amazon and Google, who had previously begun offering cloud-based storage solutions.

“These changes ensure our ability to deliver the latest technology innovations tailored to the U.S. federal government’s specific needs,” Althoff added in his note to staff. “To that end, I encourage you to consider the new subsidiary like any other. In instances where customers transcend traditional commercial and federal boundaries, we should work together across teams and subsidiaries in their interest.”

Microsoft has a long track record working with government agencies, and for nearly two years was embroiled in a legal dispute with Amazon over the JEDI cloud contract.

Earlier this year, Microsoft filed a complaint with the Government Accountability Office over a billion-dollar cloud procurement involving the National Security Agency awarded to Amazon. It is understood that the GAO will decide the outcome of the bid protest by Oct. 29.

DOD elevates CTO and launches new innovation steering group

The Department of Defense is trying to shift the focus of its chief technology officer more towards innovation and also to elevate the role, the deputy secretary of defense said Wednesday.

Incumbent CTO, Heidi Shyu, now leads a new Innovation Steering Group that will focus on improving the innovation ecosystem within the DOD. The group is the first of its kind and will feed into the Deputy’s Management Action Group (DMAG), a powerful committee comprised of military service chiefs and department secretaries.

“We are moving out quickly to try and modernize our concepts, our culture and capabilities,” Deputy Secretary of Defense Kathleen Hicks said Wednesday during a conference hosted by Defense News.

The steering group is already working on a new deputy secretary-led initiative called the Rapid Defense Experimentation Reserve (RDER). The initiative provides funds for services to experiment on tech that advances joint concepts, like Joint All Domain Command and Control (JADC2), the DOD’s new strategy to connect weapons and sensor in battle.

Processing requests for RDER funding will be one of many initiatives the new group will work on, Hicks said.

“There really has not been a focused [research, development, technology and engineering] group across the department at that level,” She said.

The CTO is gaining new status within the department as it disassembles the chief management officer position, a role eliminated by Congress in early 2021. The CMO had a mandate to increase the efficiency the DOD’s business operations, but a DOD advisory board saw it as redundant it self. Many of the CMO’s responsibilities will be devolved to other senior leaders like the CIO and chief data officer.

IRS commissioner warns lawmakers about IT spending shortfall

The Internal Revenue Service was forced to make up a $600 million IT funding shortfall for the 2021 fiscal year by tapping its enforcement budget and user fees, the agency’s leader has warned.

In a note to lawmakers late last month, Charles Rettig said the agency had recorded a significant rise in demand for its digital services during the COVID-19 pandemic and highlighted an urgent gap in funding for technology modernization.

“IRS’s technology needs are severely underfunded, a problem that has worsened over time as the demand for IT services grew and funding did not keep pace,” the IRS Commissioner wrote in the letter. “Each year, the IRS must take extraordinary measures to fund IT.”

During the 2021 fiscal year, the agency was forced to fund about $2 billion of the required $2.6 billion for IT systems from appropriations, according to the commissioner’s missive. Of the remaining $600 million shortfall, about $200 million came from enforcement, and about $400 million from user fees.

IRS’s systems came under particular strain at the height of the COVID-19 pandemic because of the demand for services delivering relief to citizens in addition to carrying out its responsibilities of tax administration.

The IRS is also contending with new statutory requirements that mandate IT investment in specific areas, as well as an increased threat to digital infrastructure from cyberattacks.

Rettig’s letter was sent in response to questions submitted by three Democratic senators in early August intended to identify further action needed from Congress to help IRS enforce the tax code.

Other conclusions from the commissioner’s letter include the finding that multi-year, consistent funding is necessary to help restore customer service and the demand for increased funding to help IRS mitigate the threat of cyberattacks.

Army’s 18th Airborne Corps hires former Exxon executive as CTO

The Army’s elite 18th Airborne Corps hired its own chief technology officer, a key part of its push to modernize the service’s operations.

Jared Summers was hired through a “highly qualified expert” contract, which allows outside experts to quickly be brought into government. Summers previously worked as the CTO and chief digital officer for Exxon Mobil and before that in a variety of roles in the Pentagon and across the military.

Based out of Fort Bragg, N.C., the 18th Airborne Corps is known as the U.S.’s “contingency forces,” ready to deploy anywhere in the world within 18 hours’ notice.

Summers appears to be the only corps-level CTO in the Army.

“It’s a great honor to serve in America’s Contingency Corps where I hope to advance the Corps’ technological and innovative efforts across all units and echelons,” Summers told FedScoop in a statement.

Summers joins the 18th Airborne Corps as it works to be the first “AI-ready” corps through its modernization project dubbed Project Ridgway. Hiring a CTO was one of the project’s key lines of effort. Other initiatives include sending soldiers to data boot camps and launching its own “Shark Tank”-style pitch events for soldier-made apps called Dragon’s Layer.

“Hiring Jared Summers, a corporate leader in data, analytics, and technology, as the XVIII Airborne Corps Chief Technology Officer is a significant step toward the development of a data-centric corps,” said Col. Joe Buccino, the corps’ spokesman. “Bringing a civilian executive with such significant industry experience into a corps leadership position demonstrates our commitment to building a culture of innovation across all units.”

The job description, reviewed by FedScoop, lists cloud adoption as one of the primary major duties.

“The [CTO] uses their expertise to champion the use of modern technology development and agile methodology while drawing heavily upon best practices from the technology industry
such as open source and cloud capability and capacity,” according to the description.

Other areas include talent management, collaboration with experts and stakeholders, and identifying emerging technologies for enterprise use.

IBM asks for more time to respond to whistleblower’s false audit complaint involving IRS

IBM requested more time to respond to a former senior sales representative’s False Claims Act (FCA) complaint concerning a $265 million software license agreement with the IRS in D.C. District Court.

According to court documents, the company’s attorneys wanted their deadline extended to Sept. 30, as they’re still determining the manner and content of their response to whistleblower Paul Cimino’s allegation that IBM used a false audit to secure an agreement extension.

D.C. District Court previously dismissed Cimino’s case in September 2019, but he successfully appealed in the Circuit Court and had it remanded July 6. The Circuit Court initially gave IBM’s attorneys until Sept. 1 to respond to Cimino’s complaint, but this is the first they’re having to address the particulars. Their motion for the deadline extension was unopposed by Cimino’s counsel.

Cimino filed his original complaint in June 2013 but amended it in July 2018, after the government declined to intervene. The FCA allows whistleblowers to prosecute fraud on the government’s behalf in return for 10% to 30% of the money recouped, and IBM could owe up to $10,000 and treble damages if found to have committed fraud.

The IRS paid between $23 million and $30 million annually for IBM software from 2007 to 2012. But when it became clear the agency would only seek an agreement extension for the products it was using, the company conducted an audit looking to charge compliance penalties for overuse, according to Cimino.

When Deloitte’s audit only found $500,000 in penalties, IBM included software licenses on discontinued servers as being in constant use to raise the number to $292 million, according to Cimino.

The IRS initially rejected IBM’s findings but ultimately caved to a $91 million figure and the company’s offer to waive the penalties in return for an agreement renewal, according to court documents.

While the investigation into Cimino’s complaint was ongoing in 2015, the agency even extended the license another six months for $16 million. Part of the reason the District Court initially dismissed Cimino’s case was the implausibility the IRS “sat idly by” and continued paying for the software amid a fraud investigation.

“[T]he IRS may have felt obligated to pay until it received a legal determination that it was relieved of the agreement’s terms,” wrote Circuit Court Judge Neomi Rao, in reversing the dismissal.

IBM did not respond to a request for comment.

Imposter email attacks: Overcoming ‘needle-in-a-haystack’ threats

Rob Holmes is vice president of products at Proofpoint. He has over 15 years’ experience in brand and fraud protection, and currently drives strategy for email fraud defense.

Email-based attacks represent a serious needle-in-a-haystack threat for organizations. To paint a picture of how serious, consider that in a typical seven-day period in mid-February 2021, Proofpoint found that 98% of 3,000 monitored organizations received a threat from a supplier domain.

Rob Holmes

Rob Holmes, Vice President, Products, Proofpoint

Imposter email threats and business email compromise (BEC) — where cyber criminals pose as someone the recipient should trust — can increasingly evade traditional security solutions that look for malicious content or behavior because those emails don’t use malicious attachments or URLs. Instead, they use social engineering to trick individuals into transferring money or sharing valuable access information unwittingly with hackers.

The scope of these attacks, however, represents a growing risk for government organizations. While imposter emails and BEC used to primarily hijack the identities of executives and organizations’ leaders, threat actors are shifting their focus to a more potentially lucrative opportunity — impersonating or compromising an organization’s suppliers.

Within most organizations there are only a relative handful of senior executives who have significant budgetary discretion, but a federal government agency may have thousands of suppliers to which significant payments are already being made. The size and nature of the supply chain attack surface therefore make it the perfect vehicle for email fraud: by hijacking any one of those suppliers’ trusted identities, a threat actor may be able to socially engineer someone in an accounts payable team to update the supplier’s banking details and redirect payments. 

To launch an imposter email or BEC attack, threat actors employ a range of tactics, the most valuable of which is a compromised account at a supplier. Not only does the compromise afford the threat actor unrestricted access to conduct research and construct an appropriate lure or insert themselves opportunistically into email conversations, but also any emails sent from that compromised account will pass all forms of email authentication. 

However, to maintain persistence and avoid detection, threat actors will often then redirect the conversation to a lookalike email account that they own and control. That may be at a lookalike domain or webmail account they had previously registered. Furthermore, most suppliers’ domains are still vulnerable to spoofing, which enables threat actors to abuse the trust and reputation of a supplier to deliver a highly credible lure.

Combatting these tactics requires a different cybersecurity approach that dynamically analyzes the attributes of an email as it arrives and detects anomalies that point to an imposter.

Establishing a multi-layered security defense

Establishing trust in identity is crucial to detecting cyberthreats, which is why the recent White House Executive Order on zero trust explicitly requires that all agencies deploy multi-factor authentication within the year. 

But to effectively combat email-based attacks, like imposter emails, agencies need to establish a multi-layered defense against infiltration that include requiring stronger identity controls of their suppliers as well.

For example, federal directives already require civilian agencies to configure their domains with domain-based message authentication reporting and conformance (DMARC) records. DMARC can provide a highly effective way to protect organizations against phishing and other fraudulent activity that spoof domains that should otherwise be trusted. 

For email sent to an agency’s supplier, modern DMARC solutions ensure that legitimate email gets properly authenticated and that fraudulent activity, appearing to come from domains under an agency’s control for instance, are blocked before it reaches that supplier. 

Proofpoint’s DMARC solution allows agencies to take this security capability a step further. Once an agency can establish with certainty that it can account for all its legitimate suppliers, the solution allows an agency to establish a policy for incoming emails from these suppliers, blocking any emails that don’t come from an approved IP address or bear the right cryptographic signature. 

In addition to modern MFA and DMARC solutions, agencies also need to rely on intermediaries between users and cloud service providers. Cloud access security brokers (CASB), for instance, identify anomalous behavior on secure cloud applications and intercept fictitious activity.

Tapping into a larger network to improve visibility

According to Proofpoint’s security data, current attack patterns indicate that threat actors are increasingly using a combination of phishing strategies and credential dumps from prior attacks to breach agency networks and their suppliers. If agencies and their suppliers only focus on their own IT environments, they may not see any immediate threats that are growing within their supply chain.

That is why we recommend using an integrated security platform that offers a number of capabilities to combat cyberthreats. 

At Proofpoint, we bring to bear the power of working with a global network of customers, assessing more than 2.2 billion emails per day and more than 35 million cloud accounts to identify and block advanced threats and look for compliance risks. We see how organizations are getting attacked and which countermeasures are proving most effective.

Even if your agency’s security team doesn’t directly identify threats coming from a compromised supplier, with our 8,000 enterprise and federal gateways in place, we can tell our customers if other companies in their federal space have been targeted. 

That gives agencies a better chance to extend the visibility of their cyber risk to get ahead of, or predict, future threats. 

Learn more about how Proofpoint can help protect federal agencies, and their people, against malicious attackers. 

Federal zero-trust strategy needs more deadlines say tech officials

The Office of Management and Budget’s draft federal zero-trust strategy needs more deadlines on required actions to help agencies prioritize them, according to tech officials.

Deadlines give chief information security officers (CISOs) something to point to during discussions with agency leadership over which zero-trust security goals to fund during the budgeting process.

Currently the draft strategy simply requires agencies to complete its identity, device, network, application and data actions by the end of fiscal 2024 — a broad deadline that doesn’t offer guidance on how to prioritize them individually.

“There’s a lot of value in a strategy document, and I’m a big fan,” said Shane Barney, CISO at U.S. Citizenship and Immigration Services, during an AFCEA Bethesda webinar Wednesday. “But there’s also a lot of value in adding teeth.”

Agencies can’t drum up the resources for a zero-trust security architecture overnight, said Sheena Burrell, deputy chief information officer at the National Archives and Records Administration. Planning and alternative funding sources, like the Technology Modernization Fund, are needed.

NARA intends to use TMF funds to build out its zero-trust architecture in accordance with the recent cybersecurity executive order and subsequent OMB guidance.

“My agency is putting in for some of our cybersecurity issues looking at our high-value assets, trying to modernize those systems, as well as looking at our zero-trust architecture and these other key pieces and putting in a request for that Technology Modernization Fund because we didn’t have that money,” Burrell said. “And we didn’t have those resources when [this guidance] came out.”

That the strategy states the goal of a zero-trust model is to place the entire enterprise on the public internet is “revolutionary” and will help agencies design their architectures and define trust, Barney said. And he’s a “big fan” of the requirement that agencies develop a network segmentation plan in consultation with the Cybersecurity and Infrastructure Security Agency to submit to OMB.

Barney would like to see a “no humans in production” requirement — where products are automatically deployed to a production environment without manual intervention — however. USCIS isn’t 100% of the way there yet.

“Humans in production should be a break-glass event; in other words it should be something that’s an emergency,” Barney said. “You moving product into production should be an automated pipeline.”

The strategy should also add an extra layer of security for token-based authentication, so it’s not just multi-factor but multi-tiered. Think adding YubiKey infrastructure — that’s separate from the regular, challenge-handshake authentication protocol — for high-level access accounts.

“Because one of the things you saw with SolarWinds was the ability for threat actors to use or compromise some of our core security in terms of identity,” Barney said.

Barney also took issue with the strategy’s requirement that CISA adapt the Continuous Diagnostics and Mitigation program to avoid the use of privileged software agents wherever possible. The problem there is a number of security tools like Splunk require privileged accounts to run, so the strategy should be clarified to explain what mitigation, monitoring and risk-based scenarios are needed, he said.

Eight bid protests over CIO-SP4 solicitation yet to be resolved

Eight bid protests filed with the Government Accountability Office over the National Institutes of Health’s $50 billion CIO-SP4 healthcare IT contract vehicle have yet to be resolved.

According to sources, the complaints focus largely on a points-based evaluation system used to assess contractors bidding on the contract as part of a mentor-protégé system run by the Small Business Administration (SBA) that may make it hard for some smaller contractors to earn a spot on the vehicle.

A total of 21 protests have so far been filed over CIO-SP4 since a request for proposals was issued in May this year. Of complaints submitted, three have been withdrawn and 10 have been dismissed.

CIO-SP4 is one of the largest technology procurement vehicles to be launched in recent years and has 10 task areas, including IT services, CIO support, cybersecurity, digital government and cloud services, and software development.

Amendments made to the solicitation since May have come under scrutiny because of concerns that changes to the contract’s points-based evaluation system may preclude some smaller companies from using the track record of mentor companies to prove their eligibility for consideration as vendors.

The SBA’s mentor-protégé program is designed to foster small business innovation by allowing larger companies to vouch for emerging businesses as part of a joint venture arrangement.

According to federal government estimates, the contract should be awarded by February 2022. Federal contracting sources queried the timeline and said that such processes typically take as long as one year to complete.

Since the start of the solicitation process in May, the National Institutes of Health Information Technology Acquisition and Assessment Center (NITAAC) has issued 11 amendments to the procurement contract, which sources described as unprecedented.

“I have worked on these types of federal contracts for 15 years, and I have never seen anything like this,” said one source.

Some amendments issued by NITAAC posed a major challenge for contractors by bringing into question the ability of smaller companies bidding on CIO-SP4 to use teaming agreements.

As part of the bid protest process, contractors can take allegations to the GAO, which will assess the merits of their case and issue a binding decision. Bid protests must be resolved within 100 days of being filed.

Earlier in July, the Professional Services Council urged the National Institutes of Health to explain its treatment of tech industry questions about the request for proposals issued for the $50 billion CIO-SP4 contract.

The contract solicitation was launched in May after a year-long draft solicitation process.

The Department of Health and Human Services did not respond to a request for comment.