This article explains why SecIntel may fail when integrated through Policy Enforcer (PE). The failure typically occurs due to connectivity issues between Policy Enforcer and ATP, which are required for SecIntel to function properly.

SecIntel fails to operate when configured via Policy Enforcer. Logs may indicate errors related to connectivity or communication between PE and ATP.

Cause

SecIntel relies on a stable connection between Policy Enforcer and ATP. If this connectivity is broken or encounters errors, SecIntel cannot retrieve threat intelligence data, resulting in failure.

If SecIntel is configured to use Policy Enforcer, verify that the connectivity between Policy Enforcer (PE) and ATP is stable and error-free. Any disruption in this communication will result in SecIntel failure.

Action Steps:

• Confirm that PE can successfully connect to ATP.
• Check logs for connectivity errors and resolve any issues before proceeding.
• Validate PE-to-ATP connectivity using diagnostic commands or logs.
• Ensure no errors are reported in the Policy Enforcer dashboard.

If issue persist, please contact JTAC.