// GLOSSARY

PoC (Safe Proof of Concept)

A reproducible proof of concept that shows a finding is genuinely exploitable, without destructive side effects, preserving data integrity in production. It is the tangible output of evidence-based validation and the tool that draws the line between 'it can be done' and 'it was done'. A scanner's warning that 'this point may be risky' is a hypothesis; a safe proof of concept turns that hypothesis into a fact shown in the field. But the qualifier 'safe' becomes critical right here and separates the concept from an irresponsible 'exploit show': the aim is not to impress, crash the system or display the force of the attack; the aim is to produce evidence the remediation team can validate in its own environment while not disrupting the service, corrupting data or being irreversible. The side-effect control principle of controlled execution makes this design mandatory. A good proof of concept answers two questions at once: is the vulnerability real, and how is it reproduced; a claim thus becomes an engineering task the product team can act on with confidence.