The page has been translated by Gen AI.

Additional feature

Describes the additional features of FPMS, such as work groups, licenses, account/session add-on features, access control, network topology, daily analysis·synchronization, excessive permission policy analysis, and unused object analysis.

Manage Work Groups

A work group is the basic unit of firewall operation tasks. Administrators are granted permission to manage only the firewalls belonging to their own work group (process application rules, search applied rules, etc.). Creating a work group based on the operational firewalls makes management easier.

Task Group Definition
Figure. Task Group Definition
Reference
Creation·modification·membership approval/cancellation of work groups can be performed only by super administrators, and work group deletion is limited to system administrators.

Create Work Group

When a work group is created, the administrator who created it and all system administrators are automatically added.

  1. Click Management > Work Group.

  2. Click Create on the “Job Group” page.

  3. Enter the following items on the “Create Work Group” page.

    Create Work Group
    Figure. Create Work Group
    ItemcontentRequired/Optional
    Task group nameEnter between 2 and 30 characters. Special characters are not allowed (except . _ - + @ ( )). Duplicate names are not allowed.Required
    DepartmentBy entering the affiliated department in the work group, you can link the department and work group. (Based on ESB integration)Selection
    ExplanationEnter up to 255 characters.Selection
    Table. Work group input items
  4. Click Create.

Reference
For accurate billing, you must enter your department correctly and update it immediately if any changes occur.

Edit Work Group

You can change the name of the work group or its affiliated department. When a work group is modified, it does not affect the associated firewalls or administrators.

  1. Click Management > Work Group.
  2. Click the work group you want to edit.
  3. Click Edit on the “Job Group Details” page.
  4. Enter the content to edit and click Edit.

Approve work group join request

Approve the membership request for the work group. Approved administrators can manage firewalls within the work group.

Approve in Work Group

  1. Click Management > Work Group.

  2. Click the work group that has a join request.

  3. Click the administrator with a pending join request status in the admin list on the “Work Group Details” page.

    Work group join approval
    Figure. Approve membership in the work group
  4. On the “Edit Work Group Membership” page, change the work group status to ‘Join’ and click Save.

Approve as admin

  1. Click Management > Administrator.

  2. Click the approval target administrator.

  3. Click the work group with a pending join request in the work group join list on the “Admin Details” page.

    Admin Registration Approval
    Figure. Admin registration approval
  4. On the “Edit Work Group Membership” page, change the work group status to ‘Joined’ and click Save.

Reference
Only the administrator themselves can submit a registration request, and a super administrator or system administrator cannot assign other administrators to a work group.

Leave workgroup

Change the administrator’s work group membership status to terminated. A revoked administrator loses all permissions for that work group.

Cancel in Work Group: Administration > Work Group > Click the work group to be canceled > Click the administrator to be canceled in the administrator list > Change the work group status to ‘Canceled’ > Save

Leave work group
Figure. Unsubscribe from work group

Cancel via Administrator: Manage > Administrator > Click the administrator to be cancelled > In the work group membership list, click the work group to be cancelled > Change the work group status to ‘Cancelled’ > Save

Admin Unsubscribe
Figure. Unsubscribe in Admin
Reference
Resigned employees are automatically terminated, and the account is automatically deleted after six months.

Delete Workgroup

Delete the work group, its firewalls, and related data. Work group deletion is only allowed for system administrators.

  1. Click Management > Work Group.
  2. Click the work group to be deleted.
  3. Click Delete > OK on the “Work Group Details” page.
Caution
When a work group is deleted, the firewalls and related data within the work group are permanently deleted.

License Settings

After the initial three months of use, you must register a license to use firewall policy/object synchronization and application, as well as the rule analysis feature.

  1. Click Management > Node System.
  2. Click the Default node system and click License in the left menu.
  3. After clicking the Create button, enter the issued license information.
  4. In the Default node system items, the “Applied Firewall” entry indicates the number of firewalls (Active/Standby) registered in the system.
Node System License
Figure. Node System License

Configuring add-on features

You can configure settings for additional features such as account information and web session management.

  1. Click Management > Node System.
  2. Click the Default node system.
  3. On the “Edit” page, click CREATE SYSTEMSETTINGS in system configuration.
Node system configuration
Figure. Node system configuration

Login session timeout

You can set the session duration after login (in seconds).

Login session timeout
Figure. Login session timeout setting
Session time information display
Figure. Session time information display after login

Maximum login attempts

You can set the maximum number of login attempts.

Maximum login attempts
Figure. Maximum login attempts setting

Password change cycle setting

You can set the account password change interval (default 3 months, number of months). If the allowed number of days has passed, you will be redirected to the password change page.

Password Change Frequency
Figure. Password Change Frequency Settings

Web access event notification settings

You can set notifications for each web access type (login, logout, view (Access), edit (Audit)).

Web Access Event Notification
Figure. Web Access Event Notification Settings

Change notification method settings

You can configure notifications using SMTP mail or syslog.

Change History Notification Method
Figure. Change History Notification Method Settings

Syslog: When a firewall policy change occurs, it is sent to the configured syslog server.

Syslog Settings
Figure. Syslog Settings
Syslog Settings
Figure. Syslog Settings

Mail Server: It can be sent to the configured SMTP mail server when a policy enforcement notification occurs. (The outgoing mail type setting value is stored as smtpMailSender)

Mail Server Settings
Figure. Mail Server Settings
Mail Server Settings
Figure. Mail Server Settings
Mail server configuration
Figure. Mail server configuration
Mail server configuration
Figure. Mail server configuration
Mail server configuration
Figure. Mail server configuration

Managing Access Control

Configure all accounts accessing from a specific IP range to have READ ONLY permissions only. Even with the same user account, it is useful when you must connect and work only in a specific server room, or when you need to grant only READ permission for external access.

Reference
Access control management is only available to super administrators and system administrators.

Register Access Control Range

  1. Management > Access ControlClick.

  2. Click Create on the “Access Control” page.

  3. Enter the following items on the “Create Access Restriction” page.

    Access Restriction Creation
    Figure. Access Restriction Creation
    ItemcontentRequired/Optional
    Band namePlease enter between 2 and 30 characters. Duplicate names are not allowed.Required
    AliasIP range for access controlrequired
    Enable connection restrictionWhen enabled, access from the specified IP range will be changed to READ permission and logged in, even if WRITE permission is present.required
    Table. Access control input items
  4. Click Create.

Edit Access Control Range

  1. Management > Access Control click.
  2. Click the band name you want to edit on the “Access Control” page.
  3. Click Edit on the “Access Control Details” page.
  4. Enter the content to edit and click Edit.

Network topology

You can collect network connection information via SNMP of L3 or higher network devices, or view the network topology by domain group using firewall Zone information registered in the FPMS system. During the initial setup, a radial diagram is displayed in view form for each domain group, and the network layer configuration identical to the actual production network is edited directly by the user using the Edit function for nodes and edges.

  1. Click Management > Topology.

  2. Click the “Topology” button at the bottom of the “Topology” page.

    Topology List
    Figure. Topology
  • ① Path Finding: Check segment firewall information using the source and destination addresses.
  • ② Node Search: Confirm the location by searching for the firewall name.
  • ③ Application Status: Verify the applied status for each segment firewall by searching the application ID.
  • ④ Applied Policy Status: Check the applied firewall information by searching for source, destination, port, and protocol information.

Setting up the network topology

Domain Group Configuration: Management > Domain Group > Click the name of the domain group you want to configure > Edit > Change the Topology Collector mode to ‘Yes’ > Edit

Domain Group Settings
Figure. Domain Group Settings

Domain Settings: Administration > Domain Groups > Left menu Domain > Click the domain you want to configure > Edit > Select the previously set domain group > Edit

Domain Settings
Figure. Domain Settings

Setting up manual topology collection

Firewall Domain Settings: Management > Firewall > Select target firewall for topology management > Edit > Select the previously configured domain > Edit

Firewall Domain Settings
Figure. Firewall Domain Settings
Reference
The manual collection topology features (such as path finding) are provided based on the internal ZONE registered in FPMS. The firewall subject to topology management must have a ZONE registered.

Create topology node: After executing Jenkins’s wallbrain-batch-job-topology, go to Administration > Component and verify the component whose name starts with ‘D-’.

Topology Node
Figure. Topology Node
Topology Node
Figure. Topology Node

Setting up automatic topology collection

Apply for Firewall: To automatically collect firewall ranges, apply for the firewall required for SNMP communication. (FPMS → firewall, UDP 161. Target IP: firewall-integrated FPMS node system IP) Also configure the SNMP settings (community values, etc.) of the devices to be collected.

Firewall Request
Figure. SNMP Firewall Request

Register Collection Target Device

  1. Click Management > Domain Group.

  2. Click the domain group name to register the devices to be collected.

  3. Click Edit on the “Domain Group Details” page.

  4. Click CREATE PROVIDERS on the “Domain Group Edit” page. 4. “Create providers” popup window appears.

  5. Please enter the following item.

    ItemExplanation
    Typefirewall: L3 firewall (firewall integrated with FPMS) / network: L3 network device (router that includes the L2 firewall zone)
    FirewallFirewall integrated with FPMS
    addressIP address of the collection device
    PortSNMP collection port number 161
    Communitycommunity value
    Passwordcommunity String(password)
    Table. Provider input items
  6. Click Create. 6. “Domain Group Edit” page’s Servers from SNMP list shows that a Provider has been added.

Create topology node: After running Jenkins’s wallbrain-batch-job-topology, check the compartment in Administration > Compartment whose name starts with ‘D-’.

Topology Node
Figure. Topology Node
Topology Node
Figure. Topology Node

Configuring Firewall SNMP: Refer to each vendor > Configuring Firewall SNMP in the 「Firewall Vendor Configuration Guide」. (Secui MF2, Secui Bluemax, Fortinet, Paloalto, Ahnlab, Axgate, Checkpoint, Cisco, Juniper support)

Using the Topology View feature

Configure Topology View: Management > Topology > Click the “Topology” button in the lower right > Click Edit in the lower left of the Topology View area

Reference
When the initial topology is created, all firewall nodes are connected to the Root node. To configure the topology View, you can modify it via Edit.
Topology View Edit
Figure. Topology View Edit

Edit Edge: Select the edge (Edge) you want to modify, click Edit Edge, then drag the edge to the top firewall node to connect it and draw the line.

Edit Edge
Figure. Edit Edge
Edit Edge
Figure. Edit Edge

Delete Node and Edge (Edge): After selecting the node or edge (Edge) to delete, click Delete Edge.

Node/Edge Deletion
Figure. Node and Edge Deletion
Node/Edge Deletion
Figure. Node and Edge Deletion

Add Node: Click Add Node at the lower left, enter the node information, and then connect the added node.

Add node
Figure. Add node
Node connection
Figure. Node connection

View in Hierarchical Structure (Hierarchical View): Click the hierarchical checkbox in the layout at the lower left.

Hierarchy View
Figure. View hierarchy

Using the shared group object firewall feature

Set up a firewall that manages shared group objects, allowing you to manage and use address group objects that must be used consistently across all firewalls registered in FPMS.

Reference
Shared group object management is available only when objects are created or modified in the application system, and this setting can be configured only by the system administrator.

Configure shared group object options

  1. In Management > Firewall, create a firewall for managing shared group objects. 1. (Vendor is set to simulation FW)

  2. After selecting Management > Node System > Default, click Edit.

  3. In the system configuration, select “Shared Group Object Management Representative Firewall Name” and then enter the firewall name for shared group object management.

    Shared Group Object Options
    Figure. Shared Group Object Options Configuration
  4. Click Create. 4. The generated option can be viewed in the node system Default.

Using the Representative Firewall Feature for AD Segment Management

This feature allows you to input an address group object when creating an AD user or group policy, enabling you to reference and use the firewall’s group objects to create policies.

Reference
AD segment management and representative firewall object management are only available when objects are created or modified in the request system, and only system administrators can configure these settings.

Setting AD Segment Management Options

  1. In Management > Firewall, create a firewall for AD segment management. 1. (Vendor is set to simulation FW)

  2. Select Management > Node System > Default, then click Edit.

  3. In system configuration, select “AD Segment Management Representative Firewall Name” and then enter the AD Segment Management Representative Firewall Name.

    AD Segment Management Options
    Figure. AD Segment Management Options Settings
  4. Click Create. 4. The generated option can be viewed in the node system Default.

Daily, Using Comparative Analysis Between Policies

Provides the ability to perform security analysis periodically.

Reference
  • Daily analysis: It is performed periodically only for analyses that do not involve comparisons between policies such as duplicate rules and shadow. - (Set interval in days, default 1)
  • Policy comparison analysis: It is performed periodically only for analyses that require comparisons between policies, such as duplicate rules, shadowing, etc. - (Set interval in weeks, default 4)

Set daily analysis options

  1. Click Management > Node System > Default > Left System Configuration.

  2. Click Create, then select “Perform daily analysis” and enter the value true.

  3. To run on a cycle other than the default provided cycle, select “Daily Analysis Cycle” and then enter a value that matches the unit.

    Daily Analysis Options
    Figure. Daily Analysis Options Settings
    Daily analysis option
    Figure. Daily analysis option setting
  4. Click Create.

Reference
  • Analyses generated by performing daily analysis have job IDs that start with “DA”.
  • Daily analysis does not support duplicate rules, Shadow, or partial Shadow, which are comparative analyses between policies.

Set comparison analysis options between policies

  1. Click Management > Node System > Default > Left System Configuration.

  2. Click Create, then select “whether to perform comparative analysis between policies” and input the value true.

  3. To run on a cycle other than the default provided cycle, select “Policy Comparison Analysis Cycle” and enter a value appropriate to the unit.

    Policy comparison analysis options
    Figure. Policy comparison analysis options setting
    Policy comparison analysis options
    Figure. Policy comparison analysis options configuration
  4. Click Create. 4. (Analyses generated through comparative analysis between policies have job IDs that start with “CA”.)

Using Daily Policy Sync

Provides the ability to perform policy synchronization periodically. (Daily synchronization: Periodically synchronize firewall device objects and policy contents to FPMS. Set the interval in days, default value 1)

Configure Daily Policy Sync Option

  1. Click Management > Node System > Default > Left System Configuration.

  2. After clicking Create, select “Perform Daily Policy Sync” and set the value to true.

  3. To perform on a cycle other than the default provided, select “Daily policy synchronization cycle” and enter a value appropriate to the unit.

    Daily policy synchronization
    Figure. Daily policy synchronization option settings
    Daily Policy Sync
    Figure. Daily Policy Sync Option Settings
  4. Click Create.

Over-Permission Policy Analysis

Analyze the log files of the over‑allowance policy, then create a file or generate a ruleset.

Reference
To perform analysis, you need the log files from the log analysis system. The log file format includes policy ID (rule_id), source address (src_addr), destination address (dst_addr), protocol (dst_protocol), and port (dst_port). IP type and allowance are set to ipv4, allow. (e.g., logfile.txt → 1213,1.1.1.1,2.2.2.2,tcp,443)

Configure Over-Permission Policy Analysis Options

  1. Create a “log analysis firewall” for log analysis. 1. (Created as Simulation FW vendor)

    Firewall for log analysis
    Figure. Create firewall for log analysis
  2. Click Management > Node System > Default > Left System Configuration.

  3. Click Create, then select “Representative Log Analysis Firewall” and enter the name of the created log analysis firewall.

    Representative log analysis firewall
    Figure. Representative log analysis firewall configuration
  4. Create policy rule groups, policy rules, etc., to set up policy rules for log analysis conversion. 4. (Depending on the situation RULE rule — when a policy change is needed, policy separation rule — setting when policy separation is required)

    Policy Rule Settings
    Figure. Policy rule settings for log analysis conversion
  5. If you performed step 4, you need to configure the rule group in Management > Firewall > Firewall for Log Analysis.

    Rule Group Settings
    Figure. Firewall rule group settings for log analysis
  6. Execute the LOG convert command in the provided Jenkins cmd.

    LOG convert
    Figure. LOG convert execution
Reference

log-convert command example

RUN_CMD="-c log-convert -f {경로}/ff.csv -s rr -t dst,svc -u NG_OCAM"
RUN_CMD="-c log-convert -f {경로}/ff.csv -s rs -t dst,svc -u NG_OCAM -a t -d 정책ID -i 방화벽이름"

Option description

  • f: file name
  • t: Items to include in the analysis among source/destination/service (if omitted, all are analyzed, e.g., -t src,dst)
  • O: (When using Rule) If there is no mapped group object, default group object name
  • u: (when using a split rule) If there is no mapping rule, default split keyword
  • s: Analysis result export method rr/fr/rs (rr: request rule bundle file, fr: firewall policy bundle file, rs: FPMS rule set generation, multiple supported separated by commas)
  • d: Policy ID for inserting the analysis result above a specific location when the s option is set to rs
  • i: d option’s firewall name with policy ID (when export mode is rs, the rule set is created on that firewall; default: primary log firewall)
  • a: Option to generate with requesting when rule set creation takes a long time (t: requesting / f: requested)

Unused Object Analysis

This function determines whether firewall objects (Address/Service/AddressGroup/ServiceGroup) are unused and returns the results in Excel.

Reference
  • To perform the analysis, the firewall must be integrated with the log analysis system.
  • Logs from a redundant firewall (when the log server has two logServerKey values) are aggregated and analyzed.
  • The Address type supports only CIDR-based objects.
  • Objects with duplicate names according to the FPMS DB are excluded from the analysis.

Analysis of Unused Objects by Firewall

API-based: Execute the object-unused-check command in the provided Jenkins cmd. The job results can be viewed in the Jenkins workspace.

API-based unused object analysis
Figure. API-based unused object analysis
Reference

object-unused-check command example

RUN_CMD="-c object-unused-check -i 방화벽이름 -O 90"
RUN_CMD="-c object-unused-check -i 방화벽이름 -O 90 -t 1 -s 2417"

Option description

  • i: Firewall name (required)
  • O: Valid period (days) of logs to analyze, only logs within that date range are analyzed (default 90 days if not entered)
  • t: When analyzing per rule, start index (if t, s are not provided, execute all rules)
  • s: When analyzing by rule unit, end index
  • a: When calling the log API, Page size (if not entered, 100,000 items)

File-based: Extract the firewall’s flow/archive logs to be analyzed from the log server using a script, upload them to FPMS, and then execute the object-unused-check-file command in the provided Jenkins cmd.

File-based Unused Object Analysis
Figure. File-based Unused Object Analysis
Reference

object-unused-check-file command example

RUN_CMD="-c object-unused-check-file -i 방화벽이름 -f flow_0.csv,flow_1.csv -d archive_0.csv,archive1.csv -t file -d true -s true"
RUN_CMD="-c object-unused-check-file -i 방화벽이름 -d archive_0.csv,archive_1.csv -t api -O 90"

Option description

  • i: Firewall name (required)
  • f: flow file name (comma-separated, without spaces)
  • d: archive file name (comma-separated, without spaces)
  • t: flow analysis type (api/file)
  • s: Perform single-file unit when analyzing archive files (true/false)
  • O: Validity period of logs to be analyzed (days) (default 90 days if not entered)
  • a: When calling the log API, Page size (if not entered, 100,000 entries)

Analysis of Unused Status by Firewall Object

Execute the object-unused-check-input command in the provided Jenkins cmd. The job results can be viewed in the Jenkins workspace.

Analysis of Unused Status per Object
Figure. Firewall Unused Status per Object Analysis
Reference

object-unused-check-input command example

RUN_CMD="-c object-unused-check-input -i 방화벽이름 -t address -s 객체1,객체2,객체3 -O 90"
RUN_CMD="-c object-unused-check-input -i 방화벽이름 -t addressGroup -s 그룹객체1,그룹객체2 -O 90"
RUN_CMD="-c object-unused-check-input -i 방화벽이름 -t service -s object_all -O 90"

Option description

  • i: Firewall name (required)
  • O: Validity period of logs to be analyzed (days) (default 90 days if not entered)
  • t: Object to be analyzed Type (select from address/addressGroup/service/serviceGroup, required)
  • s: List of object names to analyze (comma-separated, without spaces / “object_all” input selects the entire type, required)
  • a: When calling the log API, Page size (if not entered, 100,000 entries)
Detailed guide by menu
Policy analysis