Know what
you’re sharing.

Connect the application you want tested. Choose who can see the findings and which tools receive them.

Ask a security question

What AISEC uses

Web app & API
Targets in the agreed scope
GitHub
Repositories you connect
Test accounts
Access you provide
See connections

Who can see
the results?

Project data belongs to its workspace. Membership and permissions control access to findings, evidence and settings.

Team access
Review members and their roles.
Connected tools
Choose where Slack alerts and Jira tickets go.
Audit history
Review recorded security changes on supported plans.

What happens
to the data?

AISEC processes target responses, supplied context and findings to perform the assessment. This can include data sent to third-party AI providers.

Read the privacy policy
Stored credentials

Saved integration credentials and webhook secrets use encrypted storage. Use dedicated test accounts and revoke access when it is no longer needed.

Revoking access

Disconnect integrations in AISEC and remove GitHub App access in GitHub. Messages and tickets already delivered remain in their destination.

Retention and deletion

See the privacy policy for retention periods and deletion requests. Contact us before testing if your data handling requirements need a separate agreement.

Testing permission

Only test systems you own or have permission to assess. AISEC checks proof of control before testing a target.

Reports and compliance

Reports provide technical evidence for remediation and audit work. They do not grant certification or guarantee that no vulnerabilities remain.

Have a security requirement?

Tell us what your team needs before connecting sensitive systems.

Contact security Terms of service