The consequences of a government system being offline can be detrimental to national security. Chaos engineering employs specific practices and tools to create a shift in mindset and pushes everyone to design the system with failures in mind.
Chaos engineering assumes and introduces failure, rather than minimalizing and reacting to it. This shift in philosophy can create two important effects. First, code developers and their leadership become more comfortable responding to unanticipated system problems, since chaos engineering practices force them to deal with the unpredictable and undesired. Second, the infrastructure becomes more resilient and fault tolerant by becoming more modular and debuggable. This paper explores the benefits and risks to applying chaos engineering in the government.