Quantum Systems and product integrity evidence
A containment statement helps establish the scope of an incident. Accepting a product also requires evidence of who can build, approve and distribute the artifact in use.
Lire en portugaisBy Pentesty
The statement and its limits
In its November 12, 2026 statement, Quantum Systems says its internal investigation identified an active cyberattack. The company reported containing the threat in collaboration with authorities and said the investigation continued with internal and external specialists.
The manufacturer also stated that its response and the characteristics of the incident meant its unmanned systems posed no operational risk to users or operators. That is the company’s position. Pentesty has assessed neither its products nor customer environments; the statement does not provide detailed integrity evidence for individual artifacts.
Keep approval connected to the artifact
Prepare a record linking the approved change, the build execution, the resulting artifact and the release decision. Use identifiers the team can check in the systems involved. Where a cryptographic digest is available, record its source and compare the same file at the agreed transitions.
Request separate evidence for authorship, authorization and content. A value copied into a ticket does not explain who could produce or approve that package. Where signing is used, also identify who controls it and which approvals precede it. The Broadcom firmware delivery analysis follows a change through to the equipment; this assessment follows authority over the artifact.
Observe an allowed release and a rejected attempt
Use a harmless package created for the exercise. Run the sequence with the approved identity, then attempt to promote the same package using an account outside the permitted role. Agree the expected outcome, environment and stopping condition beforehand. Distribution must stay within the restricted test destination.
Collect the request, decision, identity, time and observed artifact identifier at each stage. Check whether a missing approval blocks the agreed transition. Preserve the outcome and any observation limits. If records from two tools cannot be connected, assign that gap to an owner before expanding the exercise.
Name the owner of operational acceptance
Security, the product owner and operations should connect the results to the software, configuration and use examined. Define who accepts that combination, which conditions restrict the authorization and which changes require another assessment. The conclusion should identify what was demonstrated and which questions remain open.
Keep the record discoverable after another release or a change of owner. Link to evidence in a restricted repository without copying build secrets or keys. The exercise supports bounded decisions; it neither certifies a product’s security nor replaces the incident investigation.
Frequently asked questions
Did Quantum Systems confirm an attack?
The November 12 statement says the incident was identified in late October and an internal investigation revealed an active attack. The company reported containment and an investigation involving authorities and specialists.
Does containment prove every product’s integrity?
The supplier’s statement needs to be connected to the product and intended use. The assessment checks authorities, approvals and artifacts while documenting what remains unsupported by evidence.
Does testing require a production environment?
The exercise uses an authorized lab, a harmless package and a restricted destination. Participants should agree boundaries and stopping conditions before running the allowed and rejected attempts.
How should a stage with insufficient records be handled?
Document the missing information, the person responsible for obtaining it and the decision that depends on it. Do not fill the gap with an assumption about the investigation’s scope.
Sources and references
Original Pentesty analysis, published November 15, 2026. The proposed scenarios are editorial guidance, with scope and validation to be defined for each environment.