This page walks through the end-to-end S4E workflow - from onboarding your first asset to continuous, automated security monitoring.

The S4E Workflow

Assets → Verify → Scan → Findings → Actions → Monitor

Stage 1: Add Assets

Everything in S4E starts with assets. Before you can scan anything, you need to tell the platform what you want to protect.

You can add assets in several ways:

• Manual entry - Add individual domains, IPs, or URLs through the web interface.
• Bulk import - Upload a CSV or use the API to import a large asset inventory at once.
• Automated discovery - S4E can discover related assets (subdomains, linked applications) through crawling and DNS enumeration once you provide a root domain.

When adding assets, you can assign tags (e.g., production, staging, payment-system) and criticality levels to help prioritize findings later.

Asset Service Tracking

If advanced security is enabled, S4E discovers open services and ports on your assets and automatically tracks and monitors them. When a new service or port is detected, S4E automatically triggers a scan for that service. This means you do not need to manually initiate scans every time your infrastructure changes - the platform keeps up with your attack surface in real time.

Stage 2: Verify Ownership

Before any scan can run against an asset, S4E requires ownership verification. This ensures that you are authorized to test the target and prevents unauthorized scanning of third-party infrastructure.

Verification methods include:

• DNS TXT record - Add a specific TXT record to your domain's DNS configuration.
• HTML meta tag - Place a meta tag in the root page of your web application.
• File upload - Host a verification file at a specific path on your web server.

Verification is a one-time step per asset. Once verified, the asset remains verified unless ownership is explicitly revoked.

Stage 3: Run Scans & Crawler

With verified assets in place, you can begin scanning. S4E provides multiple scanning modes:

On-Demand Scans

Trigger a scan immediately from the web interface or API. Select the scan type (or multiple types), choose the target assets, and start the scan. Results begin appearing as the scan progresses.

Scheduled Scans

Set up recurring scans to run automatically at defined intervals - daily, weekly, or on a custom cron schedule. Scheduled scans ensure continuous coverage without manual intervention.

Crawler

You can also start the Crawler on any verified asset. The crawler navigates through your web application like a real user, discovering pages, endpoints, hidden paths, API routes, and dynamically generated content. Crawler results are automatically fed into the scanning pipeline, expanding the scope of your security assessments without manual configuration.

Enrichment

After scans and crawling complete, S4E enriches the collected data with additional context - technology stack detection, known CVE mappings, geolocation, WHOIS data, certificate details, and third-party threat intelligence feeds. This turns raw scan output into actionable, context-rich findings.

AI-Created Scans

Describe what you want to test in plain English, and the AI generates and executes the scan code for you. No coding required.

Stage 4: Review Findings

Once scans complete, findings appear on the Scan Reports page. Open it from Analyze > Scans in the left sidebar. Each finding represents a specific security issue discovered on a specific asset.

The Scan Reports page provides:

• Filtering and search - Search findings or filter them by asset, severity, status, tags, scan tool, CVE ID, or date.
• Detailed view - Open any finding to see the scan output, solution advice, and status history.
• Severity - Each finding has a severity from Informational to Critical. Sort the list by severity to see the most serious issues first.
• Status management - Change the status of one finding or many at once, for example to Fixed, False Positive, or Accepted Risk.
• Trend tracking - The Overview tab shows active and resolved issues and a weekly trend of open and closed findings.

See Scan Reports and Finding Status for details.

Stage 5: Take Actions

Actions are prebuilt tasks that S4E runs for you, for example tagging assets or sending finding reports by email.

Choose from the Library

Open Automate > Library in the left sidebar to browse prebuilt actions. Each action shows its purpose and expected output. Assign the ones that fit your environment.

When Actions Run

Each action runs automatically in one of two ways:

• Scheduled - The action runs at a time interval that you set in days.
• Post-Scan - The action runs after the scans that you select.

Manage your assigned actions in Automate > My List. From there you can activate, disable, or update an action, or run it manually with Test Run. Every run is logged with its start time, finish time, status, and output.

Set Up Integrations

Admins can connect S4E with other tools from Integrations in the profile menu:

• Alert - SMS, Discord, Slack
• DNS Integration - DigitalOcean, Cloudflare
• Threat Intelligence - Brandefense, IntelX.io, ProudSec

Email alerts are set in User Settings > Alerts & Mails.

See What Is an Action and Integrations for details.

Stage 6: Monitor Continuously

S4E is designed for continuous operation, not one-time assessments. Once your workflow is established, the platform runs autonomously:

• Scheduled scans run on their defined cadence, continuously checking for new vulnerabilities and verifying that resolved issues stay fixed.
• Asset service tracking detects new services and ports and triggers scans automatically.
• Automated actions respond to new findings without manual intervention.
• Dashboards and KPIs track your security posture over time, showing trends in finding counts, remediation velocity, and overall security score.
• Reports can be generated on demand or scheduled for automatic delivery to stakeholders.
• Alerts notify your team when significant events occur - new critical findings, scan failures, or security score changes.

What's Next

• S4E Cloud - Getting Started - Set up your account and run your first scan.
• S4E On-Prem - Deployment - Install S4E in your own infrastructure.
• Core Concepts - Review detailed definitions of assets, scans, findings, and other platform objects.
• API Reference - Integrate S4E into your existing toolchain programmatically.