ILLUSTRATIVE ARCHITECTURE
This illustrative disconnected configuration keeps the platform, model inference, and required services within an approved local boundary. Validate the selected release and assessment workflow in your environment.
YOUR ON-PREMISES OR ISOLATED ENVIRONMENT
ARES EDGE PLATFORM
Local application services, configured databases and storage, findings, and assessment evidence.
LOCAL MODEL INFERENCE
Model artifacts and supported serving compute inside the environment, without a remote inference endpoint.
AUTHORIZED TARGETS
Authorized applications and APIs reached over approved local network paths.
Include authentication, time services, storage, reporting dependencies, and any required local integrations in the deployment plan.
CONTROLLED TRANSFER, NOT A LIVE CLOUD DEPENDENCY
Signed release bundles and entitlements enter through your approved transfer process. Your team controls report exports. External integrations need an approved route or a supported local alternative.
CONNECTED OR DISCONNECTED
On-premises placement and disconnected operation are different choices. Define the mode and its dependencies before installation.
Configuration
External connectivity
Release and operating requirements
Connected on premises
Approved connections for the selected entitlement, release, or other configured services.
Keep target access local, review external data flows, and apply releases through your operating process.
Fully disconnected
No internet connection, remote inference endpoint, or live Assail management connection required.
Run required services locally. Transfer signed bundles and entitlements, then verify and apply them inside the enclave.
Disconnected does not mean networkless. Ares Edge still needs approved local reach to the targets in scope. Connected configurations must be reviewed separately for their external dependencies.
HARDWARE & CAPACITY
Architecture support is not a promise that every machine can run the model. Confirm the release, OS, GPU and driver combination, and resource capacity with Assail.
Architecture or resource
What to define
x86 / x86_64
Supported hardware for data centers, security labs, and dedicated on-premises assessment environments.
ARM / aarch64
Supported ARM configurations include NVIDIA GB10-based deployment work with local model serving. Confirm the validated configuration.
Model and platform capacity
Plan GPU capability, model memory, platform services, storage, update space, and intended operation concurrency together.
Confirm the customer release, validated hardware, and required assessment lanes before deployment. Hardware support does not imply identical performance, SaaS feature parity, or government authorization.
SIGNED OFFLINE LIFECYCLE
Offline operation includes installation, model delivery, updates, and entitlement renewal. Prepare complete payloads and prerequisites so the isolated machine does not need external downloads.
01 / TRANSFER
Bring the approved signed bundle and required payloads into the enclave through your controlled transfer process.
02 / VERIFY
Establish the trusted signing anchor. Verify the release signature, integrity, and target architecture before installation.
03 / APPLY
Your operator approves and applies the release locally, then validates the resulting workflow.
Complete active operations before updating and plan recovery procedures. Renew disconnected entitlements through signed local delivery as part of the same change process.
ENVIRONMENTS & OPERATING CONDITIONS
A local installation brings testing closer to sensitive applications. The environment determines the access, evidence handling, and operational coordination the assessment requires.
Environment or control
What to plan
Private data centers
Internal applications and APIs, approved network placement, and the access needed for the workflows in scope.
Cardholder data environments
Segmented application access, authorized assessment scope, and deliberate evidence review or export. Deployment alone does not establish PCI DSS compliance.
Industrial, ICS & SCADA
Supported application and API interfaces, coordinated with process owners. Use a representative test environment where appropriate; native controller and protocol coverage must be established separately.
Government and secure enclaves
Local dependencies, controlled transfers, and mission-specific requirements. Review the appropriate offering and evidence with Assail Federal.
Evidence handling
Operator access, local storage, retention, backups, restore procedures, and any permitted report transfer.
Assessment conditions
Explicit targets, techniques, identities, and operational windows. Local placement is not a guarantee of non-disruptive testing.
FROM DESIGN TO FIRST OPERATION
Confirm the complete assessment path, not only that the interface starts. For disconnected operation, validate with external connectivity unavailable.
Step
Action
01 / Define
Choose connected or disconnected operation. Establish the boundary, authorized targets, and permitted network paths.
02 / Select and prepare
Choose supported x86 or ARM hardware. Prepare compute, prerequisites, signed release material, and local backing services.
03 / Install and validate
Verify and install the release, establish administrator access, and confirm local inference and target connectivity. Validate a disconnected workflow without external connectivity.
04 / Launch and operate
Launch a scoped assessment and review its findings and report. Document access, backups, recovery, updates, and entitlement renewal.
FREQUENTLY ASKED QUESTIONS
A disconnected configuration is a complete local operating workflow. Confirm the release, hardware, and assessment capabilities your installation needs.
TALK TO ASSAIL
Bring autonomous security testing into your infrastructure. Tell us your boundary, connectivity constraints, and assessment needs so we can plan the right Ares Edge configuration.
Your environment. Your objectives. A mission built around both.
