A. Technical FAQ

What code can I analyze with Set in Stone?

Why shouldn’t I just use standard vulnerability tools, such as Static analysis tool?

How do you keep vulnerabilities up to date?

What about false positives?

Do you support advanced techniques like fuzzing or formal verification?

How are the security reports structured?

Are there any rules to follow before analyzing a codebase?

Payment & Subscription — How does it work?

Do you still have questions?

B. Documentation

Understanding Your Security Scan Results

Understanding Your Security Report

Managing Your Account & Reports

Set In Stone API Documentation

Set In Stone Analysis Rules