ON THIS PAGE
About the Organization Page
To access the Organization page, click Administration > Organization.
An organization helps you manage your devices and subscriptions. An administrator, an operator, or a user with read-only access for organizations can create multiple organizations.
With multiple organizations, you can create small manageable groups and control administrative access. For example, you can have different organizations based on location or business units. When an organization is not functional or no longer required, you can delete the organization.
When you delete an organization, its devices, user accounts, reports, and logs are also deleted. This action is permanent and the data cannot be recovered.
Tasks You Can Perform
Field Descriptions
| Field | Description |
|---|---|
|
Details |
|
|
Organization name |
The name of the organization. |
|
Home PoP |
The home region, which is usually the geographical area where your SRX Series Firewalls are located. The home region is also where the Secure Edge and SRX Series Firewall logs are stored. Logs from all your regional PoPs are transferred to the home POP and stored there. |
|
Backup logging PoP |
The cloud-based location where your Secure Edge and SRX Series Firewall logs are backed up. The backup logging PoP provides log resiliency when the home PoP services are unavailable. |
|
Organization ID |
The auto-generated universally unique identifier (UUID) for an organization. This unique ID is used to identify organizations that have identical names. |
|
Settings |
|
|
Allow Juniper support to debug |
The option to allow Juniper Networks support team to remotely troubleshoot and resolve issues. |
|
Auto-import device after device discovery |
The option to import devices after the device discovery process. |
|
Update disabled rules to device |
The option to automatically delete rules on the device when the rules are disabled in Juniper Security Director Cloud. |
|
Hit count |
The option to track the number of times a policy is used based on traffic flow. The hit count is the number of hits since the last reset. In a large policy set, the hit count helps check the usage frequency of rules. If a rule is unused, you can verify whether the rule is shadowed by other policies. You can then manage the device without having to generate traffic manually. |
|
Hit count start time |
The option to set the time to start tracking the policy use. Juniper Security Director Cloud collects and updates the policy use statistics every 24 hours. The default start time is 0200 hours. |
|
Save rule option |
The option to allow users to create or to edit a policy rule at a zone or global level. |
|
Unnumbered tunnels |
The option to import unnumbered, matching tunnels in a Site-to-Site topology. |
|
Snapshots per policy |
The option to set the number of configuration snapshots to store for each device. You can use the snapshots to revert to a previous configuration of a device. Juniper Security Director Cloud stores the last 10 snapshots. |
| Confirmed commit timeout |
The timeout value after which, if there's no response from the device, the committed configuration changes are not deployed on the device. The device rolls back to the previously committed configuration. |
|
Automatic signature install to devices |
The option to automatically install signature bundles on devices. |
|
Approve/reject device onboarding requests |
The option to manually approve or reject requests to onboard devices through ZTP. |