AUTONOMY INSIDE THE BOUNDARY
Sensitive applications may sit behind a boundary that cannot connect to a cloud assessment service. Ares Edge is the on-premises deployment option for bringing supported adversarial validation into that environment.
Operators access Ares through the enclave’s network. In the disconnected configuration, the platform, model serving, and required backing services operate locally rather than depending on an internet-hosted model endpoint.
ILLUSTRATIVE ARCHITECTURE
This conceptual diagram shows a disconnected configuration, not a fixed installation topology. The platform and model may use one supported machine or separate local resources.
CUSTOMER-CONTROLLED LOCAL BOUNDARY
OPERATORS
Access the platform through the enclave’s own network.
ARES EDGE + LOCAL AI
Run the platform, local model endpoint, and required runtime services.
AUTHORIZED TARGETS
Reach supported applications and APIs through local routing and agents where needed.
Findings and evidence are handled locally in this planned configuration. Report exports, integrations, and networking choices determine any transfers beyond the boundary.
APPROVED TRANSFER → LOCAL VERIFICATION → OPERATOR-APPLIED RELEASE
Signed release bundles and offline entitlement material enter through your organization’s approved process. Disconnected operation does not require sending assessment prompts to a cloud model.
CONNECTIVITY OPTIONS
Select the operating model around your boundary and validate the required workflows against the delivered release.
Configuration
How it operates
What to plan
Connected Edge
Uses infrastructure you operate with approved outbound paths to configured connected services.
Model endpoint choice, release and entitlement channels, integrations, and permitted egress.
Disconnected Edge
Runs with a local model and required local runtime services, without an internet connection.
Prerequisites, signed bundles, local trust information, offline entitlement, and controlled transfer.
Intermittently connected
Plans for disconnected operation during periods without external access.
Maintain local model and service availability. Prepare the offline lifecycle rather than assuming connectivity.
PLATFORM VERSUS NETWORK REACH
An agent relays supported assessment traffic to an existing Ares deployment and needs connectivity to it. Edge places the deployment itself inside your perimeter.
Option
Where the platform runs
How it reaches private targets
Ares SaaS
Assail-hosted infrastructure.
A campaign agent connects outbound to the hosted deployment where needed.
Ares BYOC
Your supported cloud environment.
Network placement and agents provide the authorized reach.
Ares Edge
Your on-premises infrastructure.
Local network access and appropriately placed agents reach authorized segments.
In a disconnected enclave, an agent can connect to the local Edge installation where the topology requires it. An agent outside the enclave is not a substitute for the local platform and model.
ENVIRONMENTS WITH DEFINED BOUNDARIES
Deployment location does not broaden protocol support, establish compliance, or make every operational target appropriate for testing.
CARDHOLDER DATA ENVIRONMENTS
Place supported application and API assessments inside the managed boundary. Align access, evidence handling, and exports with your requirements. Deployment alone does not establish PCI DSS compliance.
INDUSTRIAL & SCADA ENVIRONMENTS
Assess supported web consoles, application APIs, and related interfaces from an approved segment. Coordinate scope, techniques, and operating conditions with process owners.
SECURE ENTERPRISE ENCLAVES
Bring assessment capabilities to private application networks, isolated development environments, and research facilities that cannot depend on an external platform.
Application and API testing is distinct from native testing of PLCs, fieldbuses, or proprietary operational protocols. Establish specific protocol coverage separately and use a representative test environment where appropriate.
OFFLINE RELEASE LIFECYCLE
Offline deployment includes installation, model delivery, verification, updates, and entitlement renewal.
Stage
Operator action
01 / Receive
Obtain the architecture-matched signed bundle and required model material.
02 / Transfer
Bring approved material into the environment through the organization’s controlled process.
03 / Verify
Verify release material against the configured trust anchor and integrity checks.
04 / Apply
Approve and perform installation or update locally under change control.
05 / Renew
Deliver signed offline entitlement material through the approved renewal process.
Prepare required packages or an approved local package source before installation. An unprepared machine may otherwise attempt external prerequisite downloads.
HARDWARE AND WORKLOAD
Release artifacts support architecture-specific x86_64 and ARM64 paths. Compatibility still depends on the complete hardware, operating environment, serving stack, and selected release.
Planning area
Confirm before deployment
Architecture and software
Match the bundle to the supported machine and operating environment. Prepare prerequisites.
Local inference
Provide appropriate GPU capacity and the supported model-serving configuration.
Memory and storage
Account for platform services, model resources, assessment workload, and update space.
Topology and concurrency
Choose one supported machine or separate platform and model resources. Size for intended parallel work.
Required capabilities
Confirm the included assessment lanes and any local alternatives for external-provider dependencies.
Confirm the offered Edge release, supported hardware, and required application workflows with Assail before deployment. Do not assume every SaaS integration or assessment lane works unchanged offline.
DEPLOYMENT PLAN
Keep network placement, target authorization, access, evidence handling, and operations in the same deployment plan.
Step
What to establish
01 / Define the boundary
Identify the enclave, applications, permitted paths, and connectivity constraints.
02 / Select the architecture
Size local platform and model resources, required services, and operator access.
03 / Prepare
Obtain the matching signed release and trust information. Prepare hardware, software, networking, and transfer procedures.
04 / Install and validate
Verify the release, confirm local inference, and validate an authorized assessment through its findings and report.
05 / Operate
Manage local access, backups, recovery, updates, report transfer, and entitlement renewal.
External identity providers, cloud device services, source providers, email delivery, and issue trackers may require connectivity or a supported local alternative. Confirm the workflows your installation needs.
FREQUENTLY ASKED QUESTIONS
Local operation depends on the selected release and the complete environment, not the deployment label alone.
TALK TO ASSAIL
Tell us where Ares needs to run, what it needs to assess, and whether the environment can connect. We will help you define the deployment.
Your environment. Your objectives. A mission built around both.
