Repository navigation
Disclose InfraGuard API key fallback in engineering case study - #60
Merged
Merged
Conversation
EdwinJdevops
marked this pull request as ready for review
October 11, 2026 10:10
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Source-backed correction
The InfraGuard Agent main-branch
api/main.pyusesos.getenv("INFRAGUARD_API_KEY", ...)with a publicly known demo key fallback. The existing case study describes API-key authentication without distinguishing this unsafe fallback. This PR clarifies the risk and preserves the distinction between source-code behavior and unverified deployment configuration.Evidence
Scope and checks