Hacker
Aryaveer Singh Rathore
@aryaveer_x1
Security Researcher | Bug Bounty Hunter
Elsewhere
Stack
- Python
Projects
- Top 50
Contextual
Graph HacksOct 2026
In security and compliance audits, auditors rarely ask about today's posture. They ask: "Six months ago, when an exception was approved or an alert was closed, was that decision justified?" That is almost impossible to answer with standard tooling. SIEM logs tell you an event happened, but they don't capture what the environment actually looked like at that exact second. If an IAM role had a path into a customer database, but a security scanner only discovered the connection three days later, traditional systems judge the past using today's knowledge. Analysts get blamed for missing attack paths that were impossible to know when they made the call. Contextual solves this by storing infrastructure topology and security findings in FalkorDB with two separate timestamps on every node and relationship: World Time (valid_from / valid_to): when the infrastructure state actually existed. Knowledge Time (learned_at): when scanners actually recorded it. If an analyst reviewed an alert on January 2 and the scanner only discovered the exposed database connection on January 5, setting World Time to January 2 and Knowledge Time to January 2 reconstructs the exact graph state available for that review. Because the attack path was not yet recorded on January 2, the system returns a DEGRADED verdict. This gives security teams a verifiable record of what was knowable at the moment the decision was made. Contextual is built for security operations engineers, cloud security teams, and compliance leads who need verifiable audit defense rather than guesswork.