Skip to main content

URL Input Field List

In the URL input field, configure the list of URLs to control, and set policies for the URLs configured in the conditional policy.


Configuring URL List​

Add Individual URL​

Step-by-step progress:

  1. Menu Access
  • Go to "Business System" → "URL Input Field" menu in the admin page.
  1. Start Adding Site
  • "URL List" tab에서**[+Register URL]**Button Click
  1. Enter site information
  • name(Required): Enter a unique name to identify the site
  • Explanation(Optional): Additional description about the site
  • Connection Information(Required): The actual URL address to access
    • http://orhttps://Include in a complete URL format
    • When using wildcards*example.comInput in the form of
    • Example:https://www.example.com, *naver.com
    • The slash (/) at the end of the URL is automatically removed and processed.
  • Group(Optional): Select from existing created groups to manage classification
  1. Save complete
  • After entering all information**[Save]**Button Click

Caution when entering:

  • The name and connection information cannot be duplicated.
  • The URL must be entered in the correct format.
  • protocol(http://, https://) or wildcard(*) must start with
  • The slash (/) at the end of the URL is automatically removed and processed the same way.

Security Level · Label Assignment​

When using the Management Center "Security Classification Label," in the URL input field registration and modification screen,Security LevelandLabelThe specified items are displayed. The upload and download control of files that move in and out of this work system operates based on the grade specified here.

Displayed only when using security classification labels, at this time**Security level and label are required selections.**is. Items will not be displayed when not in use.

Security Level(Required)

  • Select the security level of this business system. It is a value that distinguishes data sensitivity, and the upload and download control of files passing through this business system operates based on this level.
  • Selection Guide: "Please select a security level."
  • To not specify a grade, select "Grade Not Specified".

Label(Required)

  • This is a sub-classification of the grade. Even within the same grade, it can be further divided and managed by purpose, department, etc.
  • You must select a security level first for it to be activated. (If no level is selected, it will be inactive with "Please select a security level first.")
  • Selection Guide: "Please select a label."
  • If there are no labels registered for the selected grade, it will display "There are no labels registered for the selected security grade."

The grade and label are managed in the Security365 Management Center under the "Security Classification Label" menu. If it is not in the list, please register it first.

List display

  • The security level assigned to each item in the URL input field list is displayed with a color badge. Items without a specified level are marked with "-".

Bulk URL Registration​

Bulk Registration Using CSV Files:

  1. Start Batch Registration
  • "URL List" tab에서**[Batch Registration]**Button Click
  1. Template Download
  • **[Download CSV Template]**Button Click
  • Opening the downloaded CSV file in Excel
  1. Creating a CSV file
  • Name: Site Name (Required)
  • URL: Access Address (Required, includes http:// or https://, or starts with *)
  • Description: Description (optional)
  • Enter site information one for each row
  • Wildcard URLs can also be registered.(for example:*naver.com)
  1. File Upload
  • Save the completed CSV file
  • Batch Registration Screen**[Browse Files]**Click to select a file
  • or drag and drop the file into the upload area
  • **[Upload]**Button Click
  1. Check Results
  • The registration results will be displayed:
    • Registration: Total number of processed URLs
    • normal: Number of URLs successfully registered
    • Error: Number of URLs that failed to register
  • In case of an error**[Edit]**Check and correct error details with the button

Common causes of errors:

  • Required fields not entered (Name, Access Information)
  • Duplicate name or access information
  • URL format error

Policy Inspection Method​

Overview of URL Matching Policy​

The URLs registered in the URL input field are matched with the user's actual access attempts, and allow/block policies are applied. You need to understand the system's matching method accurately to configure the policies to work as intended.

Basic Matching Rules​

1. Automatic Wildcard Addition​

  • All registration URLs are automatically appended by the system. *add
  • User input:https://naver.com→ System Save:https://naver.com*
  • User input:*naver.com→ System Storage:*naver.com*

2. Protocol Separation Policy​

  • http://와 https://는Completely handled separately
  • Reason for distinguishing:
    • For security reasons, http and https are completely different protocols.
    • Some sites only support http or only support https.
    • In the case of internal systems (especially IP-based), protocols are often fixed.
    • There are cases where different actions are taken for each protocol due to certificate issues.
  • Correct Registration Method: No need to register both protocols
    • General Site: Most automatically redirect to https when accessing via http, sohttps://or*recommended for registration
    • Internal System: Registered exactly as a protocol that can be accessed in practice
    • Allow all protocols: Wildcard(*domain.com) Usage

Matching Example:

Registered policy: https://naver.com (System storage: https://naver.com*)

✅ Matching connections:
- https://naver.com
- https://naver.com/
- https://naver.com/news
- https://www.naver.com (www automatic processing)

❌ Non-matching connections:
- http://naver.com (Different protocol)
- ftp://naver.com (Different protocol)

3. www Handling Policy​

  • connection address www.is excluded from comparisonTherefore, both protocol URL and wildcard URL are processed the same regardless of the presence of www.
  • access address?Remove the back query and compare

For protocol URLs:

Registration: https://naver.com → System Save: https://naver.com*

✅ Automatically Matching:
- https://naver.com
- https://naver.com/
- https://www.naver.com (www automatically processed)
- https://www.naver.com/ (www + slash all automatically processed)

For wildcard URLs:

Registration: *naver.com → System Save: *naver.com*

✅ Matching:
- https://naver.com
- https://naver.com/
- https://www.naver.com (www automatic processing)
- https://blog.naver.com
- https://news.naver.com

Wildcard Matching Details​

1. Wildcard Position​

  • Available only at the front: *example.com ✅
  • Unavailable for intermediate use: example*.com ❌
  • The back is automatically added by the system.: No user input required

2. Wildcard Matching Operation​

Registration: *naver.com → System Save: *naver.com*

✅ Matching Connections:
- https://naver.com
- https://naver.com/
- https://news.naver.com
- https://news.naver.com/
- https://blog.naver.com
- https://shopping.naver.com

❌ Non-Matching Connections:
- https://naver.co.kr (Different Domain)
- https://navernews.com (Does not contain the string naver.com)

3. Wildcard Precautions​

Possible occurrence of unintended matching:

Registration: *shopping.com → System Save: *shopping.com* (Blocking Policy)

❌ Unintentionally Blocked Access:
- https://blog.example.com/review-shopping.com-site

✅ Access Not Blocked (excluding query for comparison):
- https://google.com/search?q=online-shopping.com

Configuration Methods by Actual Operating Scenarios​

Scenario 1: Allow all access to a specific site​

Requirements: Allow all subdomains and subpages of naver.com

Recommended settings:

Registration 1: https://*naver.com (Wildcard + Protocol)  
Registration 2: http://*naver.com (If HTTP is also supported)

Matching results:

Scenario 2: Allow only specific domains exactly​

Requirements: www.example.com onlyAllow and block subdomains

Recommended settings:

Registration 1: https://www.example.com  
Registration 2: http://www.example.com (if HTTP is also supported)

Matching results:

Scenario 3: Bulk Blocking of Shopping Mall Sites​

Requirements: Block all shopping-related sites

Recommended settings:

Registration 1: *shop.com (blocked)  
Registration 2: *shopping.com (blocked)
Registration 3: *mall.com (blocked)

Caution: Other sites containing the specified string in the address may be unintentionally blocked (?The back query does not compare)

1. How to Register a Protocol​

Recommended registration methods by site characteristics:

✅ General portal/commercial sites (Naver, Google, shopping malls, etc.)
- Automatic redirect on the site: http → https
- Recommended: https://naver.com or *naver.com
- Not recommended: http://naver.com (actually accessed via https)

✅ Internal systems/IP-based sites
- Fixed protocol: supports only http or only https
- Recommended: register exactly with the protocol that can be accessed
- Example: http://192.168.1.100, https://intranet.company.com

✅ When all protocols need to be allowed
- Recommended: *domain.com (using wildcard)
- Not recommended: http://domain.com + https://domain.com (duplicate registration)

2. Use Wildcards with Caution​

✅ Recommended: Use only when subdomain allowance is clear  
- *company.com (Official company domains)

❌ Caution: Use wildcard with general keywords
- *shop.com (Unintended matching may occur)

Troubleshooting Guide​

Problem 1: Registered but cannot access​

Confirmation items:

  1. Protocol Match (http vs https)
  2. Accuracy of Wildcard Patterns

Solution:

  • Register with a pattern exactly identical to the actual URL being accessed.

Problem 2: Should be blocked but is accessible​

Confirmation items:

  1. Whether the blocking policy is set correctly
  2. Does it overlap with other allowance policies?
  3. Isn't the wildcard pattern too broad?

Solution:

  • Reconfirming Block Settings in Conditional Policies
  • Remove Duplicate Allow Policies
  • Change to a more specific pattern

Problem 3: Unintended sites are being blocked​

Cause: The wildcard pattern is too broad

Solution:

  • Use more specific domain patterns
  • Register individual URLs instead of wildcard
  • The sites that are allowed should have a separate allowance policy added.

Group Management​

Group Creation​

Create a group to manage URLs by category.

  1. Start Adding Group
  • At the top of the "URL List" tab**[New Group]**Button Click
  1. Group Information Input
  • name(required): A unique name to identify the group
  • Explanation(Optional): Description of the group's purpose or characteristics
  1. Group creation complete
  • **[Check]**Create a group by clicking the button

Group Edit​

  1. Select the group to edit
  • Select the checkbox of the group you want to modify from the URL list.
  • activated at the top**[Edit]**Button Click
  1. Edit Group Information
  • Change name or description in the group edit window
  • **[Check]**Save changes with the button

Delete Group​

  1. Select the group to delete
  • Select the checkbox of the group you want to delete from the URL list.
  • activated at the top**[Delete]**Button Click
  1. Delete Confirmation
  • "Delete 1 selected item" confirmation message display
  • **[Check]**When clicked, the group and all URLs belonging to the group are deleted together.

⚠️ Important: When deleting a group, all sites included in that group will also be deleted, so please decide carefully.


Modify and Delete URL​

Modify URL​

  1. Select the URL to edit
  • Select the site you want to edit from the URL list
  • **[Edit]**Button Click
  1. Edit Site Information
  • Site edit slide panel opened
  • Modify necessary items such as name, description, access information, group, etc.
  • **[Save]**Save changes with the button

Delete URL​

  1. Select the URL to delete
  • Select the site you want to remove from the URL list.
  • **[Delete]**Button Click
  1. Delete Confirmation
  • "Delete 1 selected item" confirmation message display
  • **[Check]**Click to complete URL deletion

List Management Functionality​

Search and Filtering​

Search Function:

  • You can search by site name or URL in the top search bar.
  • Real-time search displays results immediately upon input

List display information:

  • name: Site Identifier
  • Connection Information: Actual URL address (displayed in system storage format)
  • Explanation: Additional information about the site
  • Modification Date: Last modified date

Bulk Operations​

Multiple Choice:

  • Multiple items can be selected simultaneously with checkboxes.
  • Batch edit/delete is possible for selected items.

Export:

  • **[Download List]**Export the current URL list to a CSV file with a button
  • Used for backup or migration to another system

Problem Solving​

Common Issues​

URL registration failed:

  • Check URL format (whether it includes http:// or https://, or starts with *)
  • Name duplication check
  • Wildcard Position Check (Can only be used at the front)
  • Check for at least one dot (.)

In case of connection issues:

  • Check Protocol Match (Registration: https, Access: http)
  • Reconfirm Allow/Block Settings in Conditional Policies

Group management issues:

  • Check included URLs before deleting the group
  • Preventing Duplicate Group Names
  • Establishing an appropriate group classification system