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.

Three principles to ensure a secure remote workforce

In many ways, 2020 served as an unintentional proof of concept for many organizations that workers can be just as productive at home as inside the office, according to a recent Okta report.

As agency leaders begin to look at a more permanent remote or hybrid-work future for some of their employees, they also need to consider both infrastructure and security modernization they will need to support the mission.

Read the full report

“Agencies will need to modernize access…but also security, because attackers never standstill,” says Sean Frazier, federal CSO at Okta in the report.

The report, “The 3 Tenets of Enabling a Remote Government Workforce,” produced by Okta, outlines strategies for agency leaders to consider that will support a more permanent remote workforce built on the principals of zero trust.

As agencies continue down the road to modernizations, says Frazier in the report, they need to change both their infrastructure and their mindset to evolve with changing workforce needs. That includes modernizing the identity stack, focusing on usability and putting security first.

Learn more about how ICAM platforms help agencies stay secure and productive in the age of telework.

This article was produced by FedScoop for, and sponsored by, Okta.

Observability: Modern tools for modern challenges in multi-cloud environments

While federal agencies are making significant headway moving IT workloads to multiple cloud service platforms, they continue to face a variety of challenges in gaining a complete picture of their total operating environment. A new generation of automated solutions — designed to provide end-to-end observability of assets, applications and performance across legacy and cloud systems — make that job easier, says Federal Chief Technology Officer Willie Hicks at Dynatrace. 

Hicks, who led IT operations in the financial sector for nearly two decades before joining Dynatrace, describes in this exclusive FedScoop interview how automated software intelligence platforms — and “deterministic AI” — can give agencies a faster and more powerful way to optimize application performance and security in dynamic IT environments. 

FedScoop: What are you seeing as the key pain points federal IT leaders are wrestling with now to manage operations in today’s increasingly dynamic and distributed IT environments?

Willie Hicks, Federal CTO, Dynatrace

Willie Hicks: Oftentimes, they don’t know what they don’t know. They don’t have visibility or “observability” into their systems. Observability means taking application performance management (APM) to the next level. With traditional APM you gathered metrics, logs, or even some transactional data. Five or six years ago, that manual approach may have been okay because you were often dealing with one runtime, like Java.

In today’s landscape, applications are being built cloud native, taking advantage of microservices, distributed across multiple clouds, often utilizing multiple run times. Instrumenting and collecting data using the old approach is not sustainable for this new environment, and the data fidelity of older APM technologies is not fine enough to adequately monitor and analyze these highly complex systems. Instead, an observability platform can automate the capture of high fidelity data, analyze it, and make sense of systems that are now too complex for a single person or even a team of people to analyze and find root causes when problems occur.  

Many of our government customers have these extremely complex systems — legacy data centers or hybrid environments — where they are crossing multiple clouds, and they start to lose control and visibility into these apps. And that leads to a lack of understanding when there is a problem: Where is the problem originating? What’s the root cause? And how do I quickly resolve it? But these systems must always be on and highly available. Think of the military with critical weapon systems. If these systems aren’t online or performing at full capacity, it could compromise our national security. The same is true for so many other agencies. Observability provides full situational awareness of all of your assets at any given time and an understanding of how they’re performing. And when they’re not, what is the root cause? 

FedScoop: There are a lot of solutions that claim to provide a single-pane-of-glass view of agency networks and applications. What is keeping agencies from adopting these more comprehensive solutions to capture system-wide visibility?

Hicks: Unfortunately, this type of visibility is oftentimes an afterthought. When these systems are designed and built, there’s often a lack of knowledge about platforms like Dynatrace that can provide this type of visibility. A lot of agencies still think in terms of needing to scrub every log to correlate events so they can figure out what’s causing a problem. That’s an antiquated approach. 

What they’re missing is true causal analysis. And to get to that point, you have to have a platform that’s going to be easy to deploy. It has to be automated. And it has to start sending those key telemetry points and do the analysis automatically. 

FedScoop: How mature are the AI and automation capabilities in these types of platforms, and can they really accommodate the mix of legacy and cloud systems agencies have to manage?

Hicks: Everyone’s talking about AI Ops and machine learning. There is a lot of confusion about what AI really can do today and what AI is really good at. Let me be clear. AI is extremely important. In most large organizations in the private sector, but especially in the public sector, you’re looking at these massive systems that have billions of dependencies that could go wrong. You couldn’t analyze all of those without AI.

At Dynatrace, we use more of a deterministic kind of AI model, which is actually quicker in addressing these types of problems. Systems are very dynamic. You have lots of containers spinning up and down. You’re bringing more servers online in the cloud. AI that uses machine learning requires a slower process in order to train their algorithms. It would be tripped up by a lot of dynamic changes in the system. Deterministic AI can handle that type of dynamic environment and give you good answers, even though this system might be shifting and changing under it. 

Another key problem when we start talking about AI and AI Ops…is explain-ability. We have to build into the system the ability to provide an explainable view of what’s happening for the customer and to program owners — that not only tells me what the problem is but shows me why it is the problem. And why you implemented whatever fix you deployed. 

Finally, agencies need to ask are we going to build our own AI monitoring system? Are we going to partner with industry and get something off the shelf? Or work with a contractor to build an AI system to identify problems on our network? Dynatrace partners with agencies to deploy better observability into their most critical systems that have gotten too complex — or in instances where they don’t have visibility out to the edge anymore, like they did when they controlled everything in their data center. Agencies need something that can parse billions of dependencies; something that can scale to handle tens of thousands of devices; something that can easily perform root cause analysis. I see RFPs almost every week from CIOs and agencies that are looking for these types of monitoring systems now. 

FedScoop: What does observability mean in all of this?

Observability extends beyond the analysis of metrics, logs, and traces to also integrate user experience data, as well as data from the latest open source standards (e.g. OpenTelemetry), all in context, at massive scale and with very low overhead.  

It’s important to note that observability is not just a beefed-up term for monitoring. Monitoring is something you do; observability is something you have. Typically, monitoring requires insight into exactly what data to monitor. It’s great for tasks like tracking performance, identifying problems and anomalies, finding the root causes of issues, and gaining insights into physical and cloud environments. If or when something goes wrong, a good monitoring tool alerts you to what is happening based on what you’re monitoring. 

You need monitoring to have observability. Monitoring can view the external, and logging can see the outputs over time. With these combined, observability can be achieved by inferring the internal based on the historical. Think of observability as that insight you need to have on exactly what to monitor. It’s proactive, using logs, AI, and causation to create a holistic system that is visible for everyone. 

FedScoop: What do you say to agencies to give them greater assurance that these automation and intelligent tools can and will perform reliably?

Hicks: Before I joined Dynatrace, I worked for some large banks for about 17 years. And I’ve been in the application performance space for quite some time. I lived through trying to configure systems to generate reports and trying to isolate root cause. Oftentimes, the purpose-built software we bought for monitoring became shelf ware because it was simply too difficult to deploy, too difficult to configure, too difficult to understand. And that was well before AWS, Azure and cloud. The level of complexity has grown an order of magnitude. Now there are systems with hundreds of different physical systems, containers, cloud instances, databases, and back end supporting systems running in the cloud. How do you instrument all that when you don’t even know what’s there?

I guarantee you, if I went to five different people in the organization — a developer, a system admin, a network person, the business owner, the application owner — and said “Show me a simple diagram of the application,” every one of them would give me a different diagram, if they could do it at all. No one knows how the whole system was created. No one knows what is there at any given time. 

You need to have an automated platform to keep track of the true breadth of details, or you will not get complete observability. It has to be intelligent, because there can be millions, if not billions of dependencies, making it virtually impossible to understand manually. So this idea of intelligent, automated observability is a necessity; you really can’t do it any other way.

Learn more about how Dynatrace can help your organization transform faster through advanced observability, automation and intelligence in one platform.

Department of Transportation fills CIO vacancy

The Department of Transportation has hired Cordell Schachter to be CIO.

Schachter joined the department Aug. 30, a DOT official told FedScoop. He replaces Deputy CIO Jack Albright who had been serving in the role in an acting capacity since former CIO Ryan Cote stepped away from the role in January during the transition to the Biden administration.

“As U.S. DOT Chief Information Officer, I look forward to supporting the work of Secretary Pete Buttigieg, Deputy Secretary Polly Trottenberg, and the entire Biden-Harris administration to Build Back Better to provide greater equity when improving the nation’s infrastructure,” Schachter said in a statement to FedScoop.

As the former longtime CTO of the New York City Department of Transportation, Schachter comes to the role with a wealth of experience. In that role, Schachter said he helped lead NYC’s DOT when responding to crises such as restoration after Superstorm Sandy in 2012 and the recent transition to telework during COVID-19.

Prior to his 13-year run with NYC’s DOT, he also worked for NYC’s Department of IT and in a variety of private-sector IT management positions with Avaya, IBM and AT&T. He also spent more than a decade early in his career with the city’s Department of Parks and Recreation.

Schachter is also an adjunct professor in NYU’s Center for Urban Science and Progress and Wagner School of Public Service.