The Junos Space Security Director dashboard provides a unified overview of the system and network status retrieved from SRX Series devices ...
You can use the Application Visibility page to view information on bandwidth consumption, session establishment, and the risks associated with your applications ...
Use the Create Firewall Policies page to configure group or device policies that determine all the network resources within your organization and that identify the required security level for those resources ...
Use this page to define how your device handles network traffic and to define policy rules ...
Use the Network Address Translation (NAT) policy page to perform basic NAT configuration ...
Use the Addresses page to create addresses that can be used across all devices managed by Security Director ...
A service in Security Director refers to an application on a device, such as Domain Name Service (DNS) ...
The Junos Space Security Director Logging and Reporting module enables log collection across multiple SRX Series devices and enables log visualization ...
You can only configure the IP address of a Log Collector node with the configuration script. If an IP address is configured manually, then the Log Collector node cannot be added to Security Director.
Verify that the following entry appears in the /etc/hosts file:<IP>LOG-COLLECTOR localhost.localdomain localhost. If you do not see this entry, then re-create the entry and add the node back through the Security Director administration workspace.
There could be a time mismatch between the Log Collector node and the Junos Space server.
The Log Collector and the Junos Space Network Management Platform must be synchronized with the NTP server. Use NTP to synchronize the time between nodes.
The node is added to another Junos Space server or the Junos Space server where it was added is no longer present.
You must delete the existing Log Collector node from Security Director > Administration > Logging Management > Logging Nodes before adding another Log Collector node.
/etc/specialNodeAgent/nodeAdded-<IP>
.System logs are retained until 80% of the disk space is utilized on the Log Collector node. Older logs are deleted to ensure that 20% of the disk space is free to store new logs.
You can use the resizeFS.sh script to increase the disk size.
The system logs that are received might not be structured system logs.
You must ensure that only the structured system logs are sent to Log Collector, so that they are parsed and all the fields are displayed properly.
The application status is shown as Down if the respective service is down. You must restart the service.
To restart each service:
For All-in-One node:
Note Starting in Log Collector version 16.1 onward, the logstash process no longer runs on the Log Receiver node. Instead, the jingest process will run.
For Log Receiver node:
For Log Indexer node:
To load balance log reception:
You can use the diagnostics tool that scans through all of your Log Collector nodes. The tool gathers log files, configuration settings, and other health status information and then bundles all the information in a zip file. You can run this tool and generate the dump file.
To run the diagnostics tool:
You can find the detailed dump file in /opt/system-diagnostics/out/<Date-Time>
syslog-capture.pcap
.
It will take an hour for devices that are configured to send logs to Log Collector to be displayed under Logging Devices.
No, the existing Spotlight Secure license (SPOT-CC) entitles you to use Policy Enforcer. There is no need to re-issue or transfer any licenses. You must, however, make sure you are using a supported version of Security Director. In addition, the SPOT-CC licenses gives you access to Command and Control (C & C) feeds, GeoIP feeds, and custom feeds.
Policy Enforcer supports only the VMware ESXi hypervisor.
Yes. Policy Enforcer itself is installed on a virtual machine and uses RESTful APIs to communicate with both Security Director and Sky ATP.