Malicious Hash Blocking
Submit a malicious file's SHA-256 hash to the eScan server and add it to the centralized block list to prevent execution across managed endpoints. Existing entries can also be removed.
Explore APIConnect eScan endpoint protection with your security ecosystem. Use External APIs to automate threat blocking, control website access and deploy outbreak prevention-while forwarding security events to SIEM platforms and cloud-native logging services.
eScan External APIs enable authorized external applications, security teams and automation platforms to submit security actions to the eScan Management Console.
Submit a malicious file's SHA-256 hash to the eScan server and add it to the centralized block list to prevent execution across managed endpoints. Existing entries can also be removed.
Explore APIAdd a website to the eScan database and control whether it is allowed or blocked through policy deployment to endpoints assigned to the relevant policy.
Explore APITrigger outbreak prevention rules for a specified managed endpoint using its client name and IP address. If the endpoint is inactive, deployment is scheduled for when it becomes available.
Explore APIForward eScan EDR/XDR security events in structured formats to SIEM platforms for centralized monitoring, investigation and correlation.
Explore integrationIngest eScan events into cloud logging services alongside cloud audit records, enabling a consolidated view of endpoint and cloud activity.
Explore integrationUse API calls from SOAR playbooks and cloud automation services to coordinate endpoint response actions with wider incident workflows.
Explore integrationConnect your existing security tools to eScan through a controlled, authenticated and intelligent integration workflow.
EDR/XDR or threat intelligence identifies a suspicious file, domain or endpoint.
THREAT IDENTIFICATIONThe integration submits an API request using its administrator-generated token from an approved source IP.
SECURE ACCESSeScan validates the request and performs the requested hash, website or outbreak-prevention action.
API EXECUTIONThe relevant block/allow policy or outbreak-prevention action is applied to applicable managed endpoints.
POLICY ENFORCEMENTThe calling system reads the API result and records the outcome in its incident or automation workflow.
RESULT VALIDATIONAPI actions should be initiated only by trusted automation or administrators. Validate the target, indicator and intended action before allowing an automated playbook to make changes.
The following three API operations are described in the current eScan External APIs reference. Replace the console address and token placeholders with values configured in your environment. Do not publish live tokens or credentials.
For additional API integration capabilities and actions, such as On-Demand Scanning, Network Connectivity Status, and other security management operations, please contact our Technical Support team at support@escanav.com to request the comprehensive API action reference and further assistance.
eScan External APIs use token-based authentication together with trusted source IP validation. Both controls must be configured in the eScan Management Console.
Each API request must include a token generated through the eScan Management Console. The server validates the token before executing the requested operation.
The source IP address making the API call must be added to the Allowed IP list in the management console. Requests from unapproved IP addresses are rejected.
Only the root user is permitted to add trusted IP addresses and generate API tokens through the management console.
Use HTTPS and restrict API access to approved integration hosts.
Store tokens in a secrets vault; never hard-code them in scripts or source repositories.
Do not expose tokens in browser code, URLs copied into tickets, application logs or monitoring dashboards.
Restrict who can trigger block, allow and outbreak-prevention actions.
Validate hash, domain, client name and endpoint IP before submitting requests.
Log the requester, time, target, action and returned result code.
Review trusted IP entries and token validity periodically; revoke and replace credentials when exposure is suspected.
The API documentation defines distinct responses for missing, invalid, expired or unconfigured tokens and for source IP addresses that are not in the Allowed IP list. Integrations should treat these as failed authorization-not as successful security actions.
Note: The published API reference documents token and trusted-IP validation. It does not describe OAuth, JWT, MFA for API calls, request signing or a separate API role model.
In addition to the documented External API actions, the supplied EDR/XDR integration design describes event forwarding to cloud-native logging services and SIEM platforms, with SOAR and cloud automation initiating response actions.
Forward eScan events in structured formats for centralized monitoring, correlation and investigation.
CEF, LEEF 1.0, key-value syslog and ECS-compliant forwarding for Elastic.
UDP 514, TCP or TLS 1.2 over TCP (default port 6514 for TLS).
Place endpoint security events alongside cloud audit and activity records.
SOAR playbooks and cloud orchestration services can coordinate API actions with incident workflows. The supplied integration design identifies Cortex XSOAR, Splunk SOAR, IBM QRadar SOAR, Microsoft Sentinel playbooks, Azure Logic Apps, AWS Lambda, Google Cloud Functions and OCI Functions as examples of integration environments.
Example workflow: A SIEM correlates an eScan detection with other suspicious activity → a SOAR playbook validates the indicator and endpoint → the playbook calls the relevant eScan API → the API result is recorded in the incident for analyst review.
Explore the API reference or speak with eScan about your integration requirements.