Internal Network Testing (High-Security Mode) in AXQA

High-Security Mode allows you to test systems that are intentionally kept inside private networks — without exposing them to the internet. With Smart Agent, execution is initiated from within your infrastructure, keeping sensitive services protected while maintaining full reporting inside AXQA.

Why this matters

• Prevents exposing internal APIs or services publicly.
• Supports strict corporate or enterprise security policies.
• Enables testing of staging, on-premise, and lab environments safely.
• Reduces attack surface while preserving test visibility.

The core principle

Instead of allowing external systems to connect into your infrastructure, the Smart Agent — running inside your network — initiates the communication.

• No inbound traffic needs to be opened.
• No firewall rules are weakened.
• Execution happens from inside your trusted environment.

How it works

1. The Smart Agent is installed on a machine inside your private network.
2. The Agent securely authenticates with AXQA.
3. Assigned test cases are retrieved by the Agent.
4. Execution runs against internal systems (APIs, devices, services).
5. Structured results are securely returned to AXQA.

What can be tested in High-Security Mode

• Internal APIs not accessible from the public internet.
• Staging environments behind VPN or firewall.
• On-premise infrastructure.
• Hardware devices inside lab networks.
• Systems restricted to specific internal IP ranges.

Security advantages

• No need to deploy temporary public endpoints.
• No reverse tunnels or exposure workarounds required.
• Authentication is handled securely between Agent and platform.
• All execution is traceable and permission-controlled.

Operational benefits

• Run tests in the same environment real users interact with.
• Reduce network variability from external execution.
• Maintain centralized reporting with decentralized execution.

Best practices

• Install the Smart Agent on a controlled machine inside your secure network.
• Limit access to the machine running the Agent.
• Use separate Agents for different environments if needed.
• Regularly monitor execution logs and activity.

Common mistakes

❌ Exposing internal systems just for testing convenience
✔ Use Smart Agent to keep testing internal and secure.

❌ Installing the Agent on an unmanaged or shared machine
✔ Use a controlled and monitored environment.

Related documentation

• Smart Agent Overview
• Why Use Smart Agent?
• Smart Agent Security Model
• Executing Test Cases via Smart Agent