Platform

Platform overview How it works Authorization testing Evidence & reports Private scanning Integrations

Solutions

Security agencies Product teams Regulated industries Partner programme

Learn

Blog Knowledge hub Compare

Resources

Pricing Documentation Help centre FAQ Security & data What we haven’t proved

Company

About Contact Careers Sign in to the platform Start a $199 pilot →

Home / Help centre / Security & privacy

Security & privacy

What happens to my source code after a cloud scan?

Quick answer

A cloud scan clones your repository only while it runs. Cyberlop wipes the clone at the end, whether the scan completes, fails or stops on cancel. Nothing carries over to the next scan. Relevant code excerpts go to your chosen AI provider over HTTPS.

The short version

The clone is temporary, and it exists only so the agents can read your code while the scan is running and for no other purpose. Cyberlop copies your repository into an isolated workspace, scans it, then deletes the copy when the scan ends. The next scan starts from a fresh clone, so an old copy never lingers on the platform between runs.

MomentWhat happens to the code
Scan startsCyberlop clones the repository, mounted read-only
Scan runsAgents read it inside an isolated, temporary container
Completed, failed or cancelledCyberlop wipes the clone
Next scanStarts from a new clone, with nothing cached

How it works in Cyberlop

The Security page puts it in one line. Cyberlop clones the repository for the duration of the scan only, and wipes it at a final state. The documentation adds that nothing stays cached across scans. Your repository sits read-only inside its own container while the agents work.

Your Git token plays a small part. Cyberlop hands it to git for each call and never writes it to disk.

One more flow matters. During analysis, relevant code excerpts go over HTTPS to the AI provider your organisation chose, and if that is a concern for your review, read whether your code is sent to an AI provider for the details.

The scan record stays after the clone is gone. Findings keep their file and line, and deleting a scan removes its workspace while the findings of the target stay in place for you to triage later.

What to do next

Need a written answer for a review? Ask through /contact.

Full tutorial

Cyberlop self-hosted scan agents: scan private apps from inside your network

Step-by-step, with annotated screenshots.

Updated · Back to the help centre

Security question we did not answer?

Our team will answer it directly, or walk through it on a call with your security lead.