The page has been translated by Gen AI.

Policy Rule Management

Policy rules define specific regulations that modify application details or set response values when an API call is made. Depending on the type of policy rule, they are categorized as Rule rules, Compliance rules, Policy Separation rules, and NAT rules, and these detailed rules are managed at the rule‑group level.

Reference
For firewall administrators, check the policy rule usage examples in 「Configuration Usage Example」.

Managing rule groups

Policy rules are managed at the rule group level. For each rule group, you can define Rule rules, Compliance rules, and NAT rules.

Reference
To apply policy rules to a firewall, you must assign a rule group in the firewall information. Refer to Setting Rule Groups on the Firewall and configure the firewall’s rule groups.

Create rule group

Create a rule group. Policy rule usage is possible on all firewalls that belong to the work group of the rule group.

  1. Click Policy > Policy Rule Settings.

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

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

    ItemcontentRequired/Optional
    nameEnter between 2 and 30 characters. Special characters are not allowed (except . _ - + @ ( )). Duplicate names are not allowed.Essential
    Work groupSelect the firewall workgroup to apply the policy rule.required
    codePlease enter within a maximum of 40 characters.Selection
    ExplanationEnter up to 255 characters.Selection
    Table. Rule group input items
  4. Click Create.

Edit rule group

Modify the rule group’s information. If it is a rule group applied to the firewall, changing the work group will cancel the firewall configuration. Before change, check the ‘Applied Firewall List’ on the “Rule Group Details” page.

  1. Click Policy > Policy Rule Settings.
  2. Click the name of the rule group you want to edit on the “Rule Group” page, or select the rule group from the rule group list at the top of the left menu.
  3. Click Edit on the “Rule Group Details” page.
  4. Enter the content to edit on the “Edit Rule Group” page. 4. All items can be edited.
  5. Click Save.

Delete rule group

Deletes the rule group and all rules defined in that rule group. If the rule group is applied to the firewall, deleting it will cancel the firewall settings. Before deletion, check the ‘Applied Firewall List’ on the “Rule Group Details” page.

  1. Click Policy > Policy Rule Settings.
  2. Click the name of the rule group you want to delete on the “Rule Group” page, or select the rule group from the rule group list at the top of the left menu.
  3. Click Delete on the “Rule Group Details” page.
  4. When a popup asking whether to delete appears, click OK.

Setting a rule group on the firewall

To use a rule group, you must configure the rule group on the target firewall.

  1. Execute steps 1–3 to modify the firewall in 「Firewall Management」.

    Firewall Rule Group Settings
    Figure. Firewall Rule Group Settings
  2. Select a rule group from the ‘Rule Group’ list on the “Edit Firewall” page. 2. Only rule groups that correspond to the same work group as the firewall are displayed.

  3. Click Save.

Rule Management

Use the Rule rule when bulk-modifying a ruleset according to a specific rule. The content received from the application system is modified by the Rule policy and turned into a request rule. Rule After creating the rule, add the condition and the action.

Rule Create Rule

Rule is generated for the rule group. In Rule creation, basic information is generated, and through Rule modification, you can add condition lists and action lists.

  1. Click Policy > Policy Rule Settings.

  2. On the “Rule Group” page, click the name of the rule group, or select the rule group from the rule group list at the top of the left menu.

  3. Click the Rule rule in the left menu. 3. (Click is possible only when a rule group is selected.)

  4. Click Create on the “Rule” page.

    Rule Creation
    Figure. Rule Creation
  5. Enter the following items on the “Rule Creation” page.

    ItemContentRequired/Optional
    Rule groupThis is a selected rule group. It cannot be modified.required
    NameEnter between a minimum of 2 characters and a maximum of 30 characters. Special characters cannot be entered (except . _ - + @ ( )).Required
    codeDefine the rule code. Enter up to 40 characters.Selection
    ActivationSet the rule’s activation status.required
    ExplanationExplain the rules. Enter within a maximum of 255 characters.Selection
    Condition list / Execution listCondition and execution statements can be entered only as a list in Edit mode.-
    Execute condition after rule duplicationChoose whether to execute the condition after duplicating the rule without modifying the original. (Can be set only in Rule settings)Selection
    Table. Rule input items
  6. Click Create.

Rule Edit

Rule By modifying the rule, you can add or delete condition lists, execution lists, and modify other information.

  1. Perform steps 1~3 of rule creation.

  2. On the “Rule” page, click the name of the Rule you wish to edit.

  3. Click Edit on the “Rule Details” page.

    Rule edit
    Figure. Rule edit
  4. Enter the content to edit on the “Edit Rule” page. 4. All items can be edited. 4. (For adding condition lists, refer to creating condition statements; for adding execution lists, refer to creating execution statements.)

  5. Click Save.

Create conditional statement

Rule defines the conditions for a rule to be applied. One or more conditional statements can be set.

  1. Perform steps 1~3 of rule editing.

  2. Click Create Condition Statement in the condition list on the “Rule Edit” page. 2. The conditional statement creation popup page appears.

    Create conditional statement
    Figure. Create conditional statement
  3. Enter the following items on the “Condition Creation” popup page.

    ItemcontentRequired/Optional
    objectSelect the object that is the target of the condition. (Refer to the condition object list for object types)required
    conditional operatorSelect an operator to verify the object. (e.g., equal, not equal, include, exclude, contains, greater, etc.)required
    condition valueEnter a value that satisfies the condition for the selected object.required
    Table. Conditional statement input items
  4. Click Create. 4. To continue creating other conditional statements, repeat steps 2–4.

Reference
If a conditional contains the same object/operator combination, operators such as equal·include·has function as OR, while negative operators such as notEqual·exclude function as AND.

The objects and operators that can be used in conditional statements are as follows.

Object nameExplanationRemarks
Default SettingsAll request rules
Network (class)Network class of the source/destination address (operates only when it is a network)a, b, c class
Rule set request detailsRequest content of the rule set
Expiration dateExpiration date of the application policy
Number of destinationsNumber of hosts when the destination is an IP
Destination objectWhether the destination is included in a specific group objectEnter the group object name in the value
Destination interfaceDestination interface name
Destination zone typeZone type of the destination addressinternal, external, etc.
Destination addressDestination address
Destination compartmentName of the compartment that the destination address belongs toMultiple entries can be entered, separated by commas
Destination typeDestination address typeip, fqdn, user, etc.
Destination tagDestination tag
Change to the destination host networkIf the destination is a host, change it to the network of the configured maskbit.8~31
Destination address group object in the firewallIf the destination belongs to a group object created within the firewall where the rule group is set, change the destination to that group object.
Source address group object in the firewallIf the source belongs to a group object created within the firewall where the rule group is set, change the source to that group object.
Number of servicesNumber of service ports
Request ruleGenerated request rulepre‑allow rule, pre‑reject rule, pre‑registration rule, etc.
Request rule request contentRequest content of the request rule
Request rule (application ID)If it matches the request rule for the applying IDEnter the application ID in the value
Number of starting pointsNumber of hosts when the source is an IP
Source objectWhether the departure point is included in a specific group objectEnter the group object name in the value
Source InterfaceSource interface name
Origin zone typeZone type of the origin addressinternal, external, etc.
Origin addressOrigin address
Source compartmentName of the compartment that the source address belongs to,(comma) separated, multiple entries can be entered
Source typeType of the source addressip, fqdn, user, etc.
Origin tagOrigin tag
Change to source host networkIf the source is a host, change it to the network of the configured maskbit.8~31
Origin/Destination compartmentName of the compartment that the origin/destination address belongs to,(comma) separated, multiple entries can be entered
Origin/Destination TypeType of departure/destination addressorigin type or destination type
tagTag of the request rule
Port numberPort number
ProtocolProtocolTCP, UDP, etc.
Permission statusWhether to allow request proposalsallow, deny
Table 7-1. Conditional Statement Object List
Operator nameExplanationRemarks
equalExact match case
not equalIn case of mismatch
includeIf the object is included in the condition value
excludeWhen the object is not included in the condition value
hasWhen the condition value is included in the object
greaterWhen the object is greater than the condition value
greaterOrEqualIf the object is greater than or equal to the condition value
lessIf the object is less than the condition value
lessOrEqualIf the object is less than or equal to the condition value
containIf the object’s content is in the condition valueOnly for string types such as comments
notContainIf the object’s content is not present in the condition value.Only for string types such as comments
Table 7-2. Conditional Operator List

Delete Conditional Statements

  1. Perform steps 1~3 of rule editing.
  2. In the “Rule Edit” page, click the X icon on the right of the condition you want to delete from the condition list
    condition
  3. Click Save.

Create operation statement

Define the actions to be performed when the condition is met. You can configure one or more execution statements.

  1. Perform steps 1~3 of Rule editing.

  2. On the “Rule Edit” page, click Create Execution Statement in the execution list. 2. The execution statement generation popup page appears.

    Create Statement
    Figure. Statement Generation
  3. Enter the following items on the “Create Statement” popup page.

    ItemContentRequired/Optional
    Change targetSelect the target (object) to modify when the condition is met. (Refer to the statement modification target list for target types)Essential
    changed valueEnter or select the value to be changed for the selected target.Essential
    Changed value optionEnter additional options for the changed value. (e.g., if the change target is ‘policy order setting’, you can select After or Before)Selection
    Additional optionsEnter additional options for the changed value. (e.g., if the target to change is ‘Departure Address’ and the changed value option is ‘GROUP’, you can select to add members to the group)Selection
    Data fixationIf the target changes, the object will be locked from that point onward to prevent further data modifications.Selection
    Table 7-3. Statement column description
  4. Click Create. 4. To continue generating other statements, repeat steps 2–4.

The changeable targets that can be used in statements are as follows.

Target NameExplanationRemarks
Destination interfaceInterface name of the destination addressuntrust, trust, etc.
Destination zone typeZone type of the destination addressinternal, external, etc.
Destination addressDestination address
Additional informationAdditional information for the application ruleUsed to exclude only some of the applied rules from optimization.
state valueRequest rule status valueinvalid, not allowed, etc.
ApplicationApplicationicmp, skype, etc.
PriorityPriority of request rules
Policy Order SettingsPolicy order settingSpecific policy ID after etc. (When “ruleId” is entered, it is interpreted as that policy ID)
Source interfaceInterface name of the source addressuntrust, trust, etc.
Origin zone typeZone type of the origin addressinternal, external, etc.
Origin addressDeparture address
tagTag of the request rule
Port numberPort number
ProtocolProtocolTCP, UDP, TCP+UDP, ICMP, IP(ANY: TCP+UDP+ICMP)
Permission statusThe role of the request ruleallow, deny, etc.
Table 7-4. List of Statements to be Modified

Delete operation

  1. Perform steps 1~3 of rule editing.
  2. On the “Rule Edit” page, click the X icon on the right of the statement you want to delete from the execution list
    Statement
    .
  3. Click Save.

Rule Change rule priority

The rule is applied according to priority. The priority of a Rule is set to the last priority when created, and can be changed through priority adjustment.

  1. Click Policy > Policy Rule Settings.

  2. On the “Rule Group” page, click the name of the rule group, or select the rule group from the rule group list at the top of the left menu.

  3. Click the Rule in the left menu.

  4. Click the arrow in the ‘Priority Adjustment’ column of the “Rule” page. 4. To increase the priority, click

    Up
    , and to decrease it, click
    Down
    . 4. Clicking the arrow changes the priority one step at a time.

    Rule priority
    Figure. Rule priority change

Rule testing

Rule can be tested to ensure it operates correctly.

  1. Click Policy > Policy Rule Settings.

  2. On the “Rule Group” page, click the name of the rule group, or select the rule group from the rule group list at the top of the left menu.

  3. Click the Rule rule in the left menu.

  4. Click test at the bottom of the “Rule rule” page. 4. “Policy Rule Configuration Test” popup page opens.

    Rule rule test input
    Figure. Rule rule test input
  5. Please enter the policy to test. 5. The origin address, destination address, protocol, port number, and allowance status are required input fields.

  6. Click test. 6. When the test is complete, the changed values are displayed in blue in the result. 6. (Only the activated rules among the rules are tested.)

    Rule Test Result
    Figure. Rule Test Result

Compliance Rule Management

Set the compliance API call response value. The response returns both code and description, and if it applies to multiple compliances, it returns the code and description for all responses.

Reference
Compliance rules do not change the contents of the application.

Compliance rule example: If the usage period is 12 months or longer and the use of port 8080 is requested, it falls under Compliance, so the corresponding code is returned when the API is called.

  • Configured compliance rules

    Compliance Example Rule
    Figure. Compliance Example Rule
  • API call

    {
        "srcAddr":"1.1.1.1",
        "dstAddr":"2.2.2.2",
        "dstPort":"8080",
        "protocol":"TCP",
        "expireDate":"20230101",
        "withDiscovery":"true",
        "checkDuplicated":"true"
    }
    
  • Response value

    {
        "complianceComment":"DURATION,CODE02",
        "compliance":true
    }
    

Create compliance rule

Compliance rules are created for rule groups. In Compliance rule creation, basic information is generated, and through rule modification, a condition list can be added.

  1. Click Policy > Policy Rule Settings.

  2. Select a rule group on the “Rule Group” page.

  3. Click Compliance Rule in the left menu. 3. (Click is possible only when a rule group is selected.)

  4. Click Create on the “Compliance rule” page.

    Compliance Rule Creation
    Figure. Compliance Rule Creation
  5. Enter the following items on the “Compliance Rule Creation” page.

    ItemcontentRequired/Optional
    Rule GroupThis is a selected rule group. It cannot be modified.Required
    nameEnter between a minimum of 2 characters and a maximum of 30 characters. Special characters cannot be entered (except . _ - + @ ( )).required
    Risk levelSelect the risk level (CRITICAL, HIGH, LOW, MEDIUM).Required (default: MEDIUM)
    codeDefine the rule code. Enter up to 40 characters.Selection
    ActivationSet the rule’s activation status.Essential
    ExplanationExplain the rules. Enter within a maximum of 255 characters.Selection
    Condition listCondition statements are listed; input is allowed only in edit mode.-
    Table. Compliance rule input items
  6. Click Create.

Edit compliance rules

Through editing the Compliance rule, you can add/delete condition lists and modify other information.

  1. Perform steps 1–3 of creating a Compliance rule.

  2. Click the name of the Compliance rule you want to edit on the “Compliance rule” page.

  3. Click Edit on the “Compliance Rule Details” page.

    Compliance Rule Modification
    Figure. Compliance Rule Modification
  4. Enter the content to edit on the “Edit Rule” page. 4. All items can be edited. 4. (For adding condition lists, refer to creating condition statements.)

  5. Click Save.

Create conditional statement

Defines the conditions for the Compliance rule to be applied. One or more condition statements can be set.

  1. Perform steps 1–3 of modifying the Compliance rule.

  2. Click Create Condition Statement in the condition list on the “Rule Edit” page. 2. The conditional statement creation popup page appears.

    Compliance condition statement generation
    Figure. Compliance condition statement generation
  3. Enter the object, condition operator, and condition value on the “Create Condition” popup page. 3. Refer to the conditional object list (Table 7-1) in Rule Management for object types.

  4. Click Create. 4. Repeat steps 2–4 to continue creating other conditional statements.

Delete condition

  1. Perform steps 1–3 of modifying the Compliance rule.
  2. In the “Rule Edit” page, click the X icon on the right of the condition statement you want to delete
    condition statement
    .
  3. Click Save.

Compliance rule testing

You can test whether the Compliance rule is functioning properly.

  1. Click Policy > Policy Rule Settings.

  2. Select a rule group on the “Rule Group” page.

  3. Click the Compliance rule in the left menu.

  4. Click test at the bottom of the “Compliance Rule” page. 4. The “Policy Rule Configuration Test” popup page opens.

    Compliance test input
    Figure. Compliance rule test input
  5. Please enter the policy to test. 5. The origin address, destination address, protocol, port number, and allowance status are required input fields.

  6. Click test. 6. When the test is completed, the applicable rule will be displayed in the results. 6. (Only test the enabled rules among the Compliance rules.)

    Compliance test result
    Figure. Compliance rule test result

Manage policy separation rules

Configure rules concerning the separation of firewall policies. Set the criteria for the 「Policy Management」 firewall policy separation function.

Create policy separation rule

Policy separation rules are created for rule groups. Policy separation rule creation generates basic information, and you can add condition lists by modifying the rule.

  1. Click Policy > Policy Rule Settings.

  2. Select a rule group on the “Rule Group” page.

  3. Click Policy Separation Rules in the left menu. 3. (Click is enabled only when a rule group is selected.)

  4. Click Create on the “Policy Separation Rule” page.

    Create Policy Separation Rule
    Figure. Create Policy Separation Rule
  5. Enter the following items on the “Policy Separation Rule Creation” page.

    ItemcontentRequired/Optional
    Rule groupThis is a selected rule group. It cannot be changed.Required
    nameEnter at least 2 characters and at most 30 characters. Special characters cannot be entered (except . _ - + @ ( )).Required
    codeDefine the rule code. Enter up to 40 characters.Required (although not marked as required on the screen, it must be entered for the separation rule to work.)
    EnableSet the rule’s activation status.Required
    ExplanationExplain the rules. Enter within a maximum of 255 characters.Selection
    Condition listCondition statements are listed; input is allowed only in Edit.-
    Table. Policy separation rule input items
  6. Click Create.

Edit policy separation rule

  1. Perform steps 1~3 of creating a policy separation rule.

  2. Click the name of the policy separation rule you want to edit on the “Policy Separation Rule” page.

  3. Click Edit on the “Policy Separation Rule Details” page.

    Policy Separation Rule Modification
    Figure. Policy Separation Rule Modification
  4. Enter the content to edit on the “Edit Rule” page. 4. You can edit all items. 4. (For adding condition lists, refer to creating condition statements.)

  5. Click Save.

Create Conditional Statement

Defines the conditions for the policy separation rule to be applied. You can configure one or more conditional statements.

  1. Perform steps 1~3 of modifying the policy separation rules.

  2. Click Create Condition Statement in the condition list on the “Edit Rule” page. 2. The conditional statement creation popup page appears.

    Create Policy Separation Condition Statement
    Figure. Policy Separation Rule Condition Statement Creation
  3. Enter the object, conditional operator, and condition value on the “Create Condition” popup page. 3. Refer to the conditional object list (Table 7‑1) in Rule Management for object types.

  4. Click Create. 4. To continue creating other conditional statements, repeat steps 2~4.

Delete Conditional Statement

  1. Perform steps 1~3 of modifying the policy separation rules.
  2. On the “Rule Edit” page, in the condition list, click the X on the right of the condition you want to delete
    condition
    .
  3. Click Save.

Managing NAT Rules

Set additional rules when the request rule is changed by the NAT policy.

Create NAT rule

NAT rules are created for rule groups. In NAT rule creation, basic information is generated, and conditions can be added to the list through rule modification.

  1. Click Policy > Policy Rule Settings.

  2. Select a rule group on the “Rule Group” page.

  3. Click the NAT rule in the left menu. 3. (Click is possible only when a rule group is selected.)

  4. Click Create on the “NAT Rule” page.

    Create NAT rule
    Figure. Create NAT rule
  5. Enter the following items on the “NAT Rule Creation” page.

    ItemcontentRequired/Optional
    Rule GroupThis is a selected rule group. It cannot be modified.required
    NameEnter at least 2 characters and at most 30 characters. Special characters cannot be entered (except . _ - + @ ( )).required
    codeDefine the rule code. Enter up to 40 characters.Selection
    ActivationSet the rule’s activation status.required
    ExplanationExplain the rules. Enter within a maximum of 255 characters.Selection
    Condition listCondition statements are listed; input is allowed only in edit mode.-
    Table. NAT rule input items
  6. Click Create.

Edit NAT rule

  1. Perform steps 1–3 of creating a NAT rule.

  2. Click the name of the NAT rule you want to edit on the “NAT Rule” page.

  3. Click Edit on the “NAT Rule Details” page.

    Edit NAT rule
    Figure. Edit NAT rule
  4. Enter the content to edit on the “Edit Rule” page. 4. You can edit all items. 4. (For adding condition lists, refer to creating condition statements.)

  5. Click Save.

Create a conditional statement

Defines the conditions for a NAT rule to be applied. You can configure one or more conditional statements.

  1. Perform steps 1~3 of modifying the NAT rule.

  2. On the “Rule Edit” page, click Create Condition Statement in the condition list. 2. The conditional statement creation popup page appears.

    NAT condition statement creation
    Figure. NAT rule condition statement creation
  3. Enter the object, condition operator, and condition value on the “Create Condition” popup page. 3. Refer to the conditional object list (Table 7‑1) in Rule Management for object types.

  4. Click Create. 4. To continue creating other conditional statements, repeat steps 2–4.

Delete conditional statements

  1. Perform steps 1~3 of modifying the NAT rule.
  2. On the “Rule Edit” page, in the condition list, click the X on the right of the condition statement you want to delete.
    Condition statement
  3. Click Save.

Bulk upload rule settings

Provides a bulk upload feature for rule settings within a rule group.

Reference
Provided only via text copy & paste, not file upload.
  1. Click Policy > Policy Rule Settings.

  2. Select a rule group on the “Rule Group” page.

  3. In the left menu, click the rule to start batch upload. 3. (Click is enabled only when a rule group is selected.)

  4. Click Batch Upload on the rule list page.

    Bulk Rule Settings Upload
    Figure. Bulk Rule Settings Upload
  5. Download the template, fill in the batch upload data in the Excel file, and then copy and paste the completed content exactly as is. 5. (Even if you copy and paste both the header and the example from the Excel file, it will be recognized correctly.)

  6. Click Batch Upload to proceed.

The descriptions for each item in the Excel file are as follows.

ItemContentRequired/Optional
LambdaActionNameName of the rule to addrequired
enableRule activation statusSelect (default: true)
codeRule codeSelection
priorityPriority of rulesRule is required only in rule settings (other rule settings default to 0)
ruleCopyRun after cloningOptional (default: false)
useAnalysisUse of analysis (compliance analysis within security analysis)Optional (applies only to compliance rules, default: true)
descriptionExplanationSelection
lambda_objectConditional statement objectRequired when entering a conditional statement
lambda_operatorConditional operator in a conditional statementRequired when entering a conditional statement
labda_valueCondition value of the conditional statementRequired when entering a conditional statement
operation_targetTarget of statement changeRequired when entering a statement
operation_valueChanged value of the execution statementRequired when entering a statement
operation_compareObjectExecution statement change value optionSelection
operation_isFixWhether the execution query data is fixedSelect (default: false)
operation_additionalOperationAdditional options for execution statementsSelection
Table. Batch upload items
Reference
  • Conditional statements/execution statements are required fields, but you can enter only one of the two and leave the other blank, and it will still be recognized correctly for batch generation.
  • The condition statement objects are the condition object list (Table 7-1), the execution statement change values are the execution statement change target list (Table 7-4), and the selectable columns of the execution statement refer to the execution statement column description (Table 7-3).

Reference notes for condition operator input in conditional statements

When creating conditional statements, refer to the following and input the condition operators for each object. An error will be displayed if it does not meet the criteria below.

Conditional statement objectconditional operator
Source address, destination address, protocol, port numberequal, notEqual, include, exclude, has
Source/Destination Interface, Source/Destination Zone Type, Source/Destination Type, Source/Destination Compartment, Allowanceequal, notEqual
Request rule request content, rule set request contentcontains, notContains
Expiration date, number of origins, number of destinations, number of servicesgreaterOrEqual
Origin/Destination type, tagequal
request rule, source object, destination objectinclude, exclude
Network (class)equal, less, lessOrEqual, greater, greaterOrEqual
Request rule (application ID)include, notInclude, exclude, related, notRelated
Table 7-5. Conditional Operator
Object Management
Completed Task Management