CSV Directory Synchronization
Menu Path: Settings > Inbound Provisioning > CSV Directory Synchronization
Table of Contents
- Overview
- Before You Start
- Screen Configuration
- How to Set Up (4 Steps)
- Step 1: Connect to the server
- Step 2: User Settings
- Step 3: Group Settings
- Step 4: Synchronization Settings
- Manual Synchronization
- Check Synchronization Results
- Error Handling
- Caution
- Example of Configuration Scenario
Overview
This is a feature that periodically monitors CSV files uploaded to an FTP or SFTP server and automatically synchronizes user and group information to the Security365 management center. It is used when integrating CSV files regularly generated by external systems such as HR systems.
Once the administrator sets the server access information, file path, conversion rules, and execution cycle, the system will automatically detect and reflect file changes thereafter.
Action Flow:
| step | Content |
|---|---|
| 1 | Connecting to FTP/SFTP Server |
| 2 | Download CSV file from the specified path |
| 3 | Check for file changes compared to the previous synchronization (file content hash comparison) |
| 4 | CSV Data Transformation and Validation (Field Mapping, Filtering, etc.) |
| 5 | Reflecting Management Center User/Group Information (Group → User Order) |
**Reference:**You can only enable one inbound provisioning method. When you enable CSV directory synchronization, other methods (SCI Server, Microsoft365, local Active Directory) will be disabled.
**Reference:**If the file content is the same as the previous synchronization, the synchronization will be skipped. This is normal behavior that prevents unnecessary processing.
Before You Start
Before starting the setup, please prepare the information below in advance.
| Preparation Items | Description | example |
|---|---|---|
| FTP/SFTP server address | Customer file server's IP or domain | ftp.example.com |
| Port Number | SFTP Basic 22, FTP Basic 21 | 22 |
| Access Account | Server Login ID / Password | ftpuser |
| CSV file path | Directory where the CSV file is located on the server | /data/hr/users/ |
| CSV file name pattern | Whether the file name is fixed or changes by date | users.csvorusers_yyyyMMdd.csv |
| CSV Column Information | Header names or column order of the client CSV | 사원번호, 이름, 메일, 부서ID, 재직상태 |
Screen Configuration
Before Configuration: A message "Available after setup." will be displayed on the CSV directory synchronization card.
After completing the setup: The following information is displayed on the card.
| Information | Description |
|---|---|
| Connection Method and Server Information | Connection method (SFTP/FTP), host address, port, connection ID |
| Last synchronization date and result | Recent synchronization execution time and success/failure status |
| Synchronization Period | Automatic synchronization setting time |
| [Edit] button | Change Settings |
| [Manual Sync] Button | Immediate synchronization execution |
How to Set Up (4 Steps)
[Step 1] Connect to Server
Enter the FTP/SFTP server connection information.
| item | Description | example |
|---|---|---|
| Connection Method (Protocol) | Choose FTP or SFTP | SFTP |
| Host (Server Address) | Server IP or domain address | ftp.example.com |
| port | Connection port number (automatically changes when the protocol changes) | 22 |
| Access ID | Server Account ID | ftpuser |
| Access Password | Server account password (encrypted storage) |
Connection Method Selection Criteria:
| Method | Default Port | Description | Recommended Situation |
|---|---|---|---|
| SFTP | 22 | SSH-based encrypted transmission | External network or environment requiring security (recommended) |
| FTP | 21 | Non-encrypted transmission | Low-security environments such as internal networks |
After setting**[Integration Test]**Please click the button to check the server connection status.
**Reference:**The password is stored encrypted with RSA and is not exposed in plaintext on the settings screen.
button: Cancel | Save temporarily | Next
[Step 2] User Settings
Set the monitoring method and data transformation rules for the user CSV file.
Surveillance Path
Select Monitoring Mode
It depends on how the client company's server manages files.
| situation | Selection Mode | File Pattern Example |
|---|---|---|
| Always overwrite with the same filename | Single File | users.csv |
| A new file is created by date. | Directory > Filename 기준 | users_yyyyMMdd |
| Automatically detect recently modified files | Directory > By Modification Date | *users* |
When selecting directory mode — criteria for determining the latest file
| standard | Description | Usage Scenario |
|---|---|---|
| As of the revision date | Select the file that contains the specified keyword and has the most recent modification date. | When there is no date in the file name |
| File Name Criteria | Select the file with the most recent date by parsing the date in the filename. | When the HR system includes the date in the filename |
Support Date Format (when selected based on filename):
| format | File Name Example |
|---|---|
| yyyyMMdd | users_20260101.csv |
| yyyy-MM-dd | users_2026-01-01.csv |
| yy-MM-dd | users_26-01-01.csv |
| yyMMdd | users_260101.csv |
Path and File Patterns
| item | Description | example |
|---|---|---|
| path | Absolute path of the directory where the CSV file is located on the server | /data/hr/users |
| File Pattern | File name pattern to monitor | users_yyyyMMdd |
**Reference:**file name is
#Files starting with __PH_0__ are commented out and excluded from synchronization targets.
Synchronization Options
| item | Option | Description |
|---|---|---|
| Handling Items Not Included in CSV | Maintenance (default) | Maintain existing users not in the CSV as is. Recommended when the omission may be a simple mistake. |
| Deactivate | Deactivate existing users not present in the CSV. Suitable for environments where leavers are removed from the CSV in the HR system. | |
| Stop synchronization on validation error | use | If there is even one validation error, stop the entire synchronization. Used when prioritizing data integrity. |
| Not used (default) | Skip error records and reflect only the remaining normal data. |
Caution:
비활성화When selected, all existing users not included in the CSV file will be deactivated. Please make sure to check the contents of the file in advance.
CSV Converting Settings
Set the CSV file format and field mapping rules. If using user synchronizationField mapping is requiredis.
Input CSV delimiter
| Option | separator | Usage Example |
|---|---|---|
| Comma (default) | , | EMP01,홍길동,영업 |
| pipe | | | EMP01|홍길동|영업(Safe when data contains commas) |
| tab | (tab character) | EMP01 홍길동 영업 |
Field Mapping Method
| Method | Description | Usage Scenario |
|---|---|---|
| Header-based (default) | Mapping with column names of the first row (header) in CSV | When there is a header row in the CSV file |
| Index-based | Mapping by column order (starting from 0) | When there is no header row in the CSV file |
Header-based Mapping Example(Customer CSV Column Name → Standard Field):
| Customer CSV Column Names | Standard Field | Required 여부 |
|---|---|---|
| Employee Number | USER_ID | Required |
| name | USER_NAME | Required |
| email address | Selection | |
| Affiliated Department ID | GROUP_ID_LIST | Selection |
| Employment Status | ACTIVE_STATUS | Selection |
Index-based mapping example(CSV without header):
| Column Order | Standard Field | Required 여부 |
|---|---|---|
| 0 (first column) | USER_ID | Required |
| 1 (Second Column) | USER_NAME | Required |
| 2 (third column) | Selection | |
| 3 (fourth column) | GROUP_ID_LIST | Selection |
| 4 (fifth column) | ACTIVE_STATUS | Selection |
Standard Field List (User)
| Standard Field | Required 여부 | Description |
|---|---|---|
| USER_ID | Required | User Unique ID (Email format recommended) |
| USER_NAME | Required | username |
| Selection | Email address | |
| GROUP_ID_LIST | Selection | Affiliated Group ID (multiple groups are separated by commas) |
| ACTIVE_STATUS | Selection | Activation Status |
ACTIVE_STATUS recognition value:
| Recognition value | Processing Result |
|---|---|
ACTIVE, Y, 1, true(case insensitive) | Process as active user |
All other values (재직, 사용, N, empty value, etc.) | InactiveProcess as a user |
**Caution:**If the ACTIVE_STATUS column is incorrectly mapped or a value that the system cannot recognize is entered,All users deactivatedIt can be done. After changing the settings, be sure to conduct a small-scale test first.
**Common Mistakes:**client company
재직/퇴직,사용/미사용If the same Korean value is used, the system processes all as inactive. In this case, filter records to pass only active users, or check the status manually after synchronization without ACTIVE_STATUS mapping.
Record Filtering (Optional)
You can include only records that meet specific conditions as synchronization targets. When entering multiple conditions, only records that satisfy all conditions (AND) will be processed.
wildcard(*) Pattern Example:
| pattern | Matching Example | meaning |
|---|---|---|
ACTIVE | ACTIVE | Exactly matches 'ACTIVE' |
*@company.com | hong@company.com | Value ending with a specific domain |
EMP_* | EMP_001, EMP_HR | Values starting with a specific prefix |
*부서* | 영업부서, 개발부서 | Value containing a specific string |
Default Email Domain (Optional)
USER_ID must be in email format (@If it is not included, it automatically adds the configured domain and converts it to an email format. If the EMAIL field is empty, it will be filled in together.
| USER_ID (input) | EMAIL (Input) | Domain Settings | USER_ID (output) | Note |
|---|---|---|---|---|
EMP001 | (empty value) | company.com | EMP001@company.com | Converted, EMAIL is also auto-filled. |
EMP001 | hong@other.com | company.com | EMP001@company.com | EMAIL retains the existing value |
user@a.com | (empty value) | company.com | user@a.com | If it is already in email format, no changes. |
button: Cancel | Save as Draft | Previous | Next
[Step 3] Group Settings
Set the monitoring method and data transformation rules for the group CSV file. The configuration is the same as the user settings, with the following differences.
Difference from User Settings:
| item | User Settings | Group Settings |
|---|---|---|
| CSV Excluded Item Handling Options | Maintain / Disable | maintenance /delete |
| Stop synchronization on validation error | exists (optional) | None(Always stop completely on error) |
| Default Email Domain | exists | None |
Synchronization Options (Group)
| item | Option | Description |
|---|---|---|
| Handling Items Not Included in CSV | Maintenance (default) | Maintain existing groups that are not in the CSV |
| delete | Delete Existing Groups Not in CSV (Only Empty Groups Without Members Can Be Deleted) |
Standard Field List (Group)
| Standard Field | Required 여부 | Description |
|---|---|---|
| GROUP_ID | Required | Group Unique ID |
| GROUP_NAME | Required | Group Name |
| DESCRIPTION | Selection | Group Description |
| PARENT_GROUP_ID | Selection | Parent Group ID (used when configuring hierarchy) |
Header-based Mapping Example(Group):
| Customer CSV Column Names | Standard Field |
|---|---|
| Department Code | GROUP_ID |
| Department Name | GROUP_NAME |
| Description | DESCRIPTION |
| superiorDepartmentCode | PARENT_GROUP_ID |
**Caution:**If an error occurs during group synchronization, the group will be applied without partial reflection.All stoppedIt is possible. However, user synchronization runs independently of the group, so it will continue regardless of any group errors. Please thoroughly review the data integrity of the group CSV file in advance.
**Reference:User settings and group settings betweenAt least one side must complete field mapping.**You can save it.
button: Cancel | Save as Draft | Previous | Next
[Step 4] Synchronization Settings
Set the automatic synchronization period and backup options.
| item | Description |
|---|---|
| Automatic Synchronization | Automatically executed at the set interval when in use. If not in use, it can only be executed with the [Manual Sync] button. |
| Synchronization Period | When using automatic synchronization, set the time (hour/minute) to run daily. |
| Backup Before Synchronization | Automatically back up current user/group data before executing synchronization when in use. |
Setting Example(Automatically executed every day at 2 AM):
| item | Settings |
|---|---|
| Automatic Synchronization | use |
| cycle | every day |
| Start Time | 02:00 |
| Backup Before Synchronization | Usage (Recommended for Production Environment) |
**Reference:**All execution times are based on KST (Korea Standard Time).
**Reference:**Currently, only one execution per day is supported.
**Caution:**If backup is enabled before synchronization, synchronization will not proceed in case of backup failure. The first synchronization (no backup target data) will skip the backup step and proceed.
button: Cancel | Previous | Save
Manual Synchronization
After saving the settings, in the CSV directory synchronization card on the inbound provisioning list screen**[Manual Synchronization]**Clicking the button will execute synchronization immediately.
Execution Flow:
- [Manual Synchronization] Click → Click [Run] in the confirmation popup
- Synchronization in progress — Disable button and display in progress message
- Complete — The last synchronization information of the card is updated with success/failure messages.
**Reference:**Group → User will be processed in order.
**Caution:**During synchronization, duplicate execution is not possible. Please run it again after the previous synchronization is complete.
Check Synchronization Results
After completing the setup, you can check the last synchronization result on the card.**[Last Synchronization Information]**Clicking the link will open the detailed slide.
Last synchronization status types:
| status | Description |
|---|---|
| success | File monitoring and data reflection completed |
| Partial failure | Some records failed to reflect, the rest are reflected normally (can occur during user synchronization) |
| No changes | No changes in file content compared to the previous synchronization (normal operation) |
| Connection failed | Unable to connect to FTP/SFTP server |
| File not found | The file does not exist at the specified path. |
| failure | Error occurred during data transformation, validation, or reflection process |
Detailed slide display items:
In the slide, you can check the results of group synchronization and user synchronization respectively.
| item | Display content |
|---|---|
| status | Success / Partial Failure / No Change / Failure etc. |
| Surveillance Target | Configured paths and file patterns |
| Last synchronization date and time | Completion Time |
| Failure Reasons (In Case of Failure) | Error Messages and Error Codes |
**Reference:**In the case of a failure state, an error message along with an error code will be displayed. Check the code for reference on how to handle the error.
Error Handling
| Error Type | Main Symptoms | Action Method |
|---|---|---|
| Connection Error | Status: Connection Failed | Check server address, port, and account information / Check if the port is open in the firewall |
| File Error | Status: No file | Check specified path and file pattern / Check if the file is uploaded to the server |
| Conversion error | Status: Failure | Check CSV delimiter settings / Check field mapping settings / Check CSV file encoding (UTF-8) |
| Validation Error | Status: Failure | Check for missing required fields (USER_ID, USER_NAME / GROUP_ID, GROUP_NAME) |
| Reflection Error | Status: Failure | Check the error details in the synchronization log and contact the responsible team. |
| Backup failed | Synchronization Not Executed | Check Backup Settings Before Synchronization / Check Backup Storage Space |
Caution
- User settings and group settings**At least one side must complete field mapping.**You must do it. Neither side will be saved in an unset state.
- ACTIVE_STATUSIf the field mapping is incorrect, all users may be deactivated. After changing the settings, be sure to conduct a small-scale test first.
- When a group synchronization error occurs, the entire group is halted without partial reflection. However, user synchronization runs independently of the group, so it continues regardless of group errors.
- file name is
#Files starting with __PH_0__ are commented out and excluded from synchronization targets. - If the file content has not changed, synchronization will be skipped. This is normal behavior.
- When the backup option is enabled before synchronization, if a backup failure occurs, synchronization will also be halted.
- All execution times are**KST(Korea Standard Time)**It is a standard.
- Even if you directly modify the synchronized user/group information in the management center, it will be overwritten based on the CSV file during the next synchronization execution. If permanent changes are needed, please modify the original CSV file or the source system first.
- You can only activate one inbound provisioning method, and if another method is already activated, you must use it after switching.
Example of Configuration Scenario
Scenario: When the HR system generates daily date-based CSV files on the FTP server
The HR system at 1 AM every day./hr/export/pathusers_20260101.csvAutomatically generate user files in the format, and the group file isgroups.csvIt is an environment where it always overwrites with the same name.
Step 1 — Server Connection Settings:
| item | Settings |
|---|---|
| Connection Method | SFTP |
| host | ftp.company.com |
| port | 22 |
| Access ID | hrexport |
Step 2 — User Settings:
| item | Settings |
|---|---|
| Surveillance Mode | directory |
| Latest file judgment criteria | File Name Criteria |
| path | /hr/export |
| File Pattern | users_yyyyMMdd |
| Handling Items Not Included in CSV | Deactivation (Automatic Processing of Departed Employees) |
| CSV delimiter | comma |
| Mapping Mode | Header-based |
| Field Mapping | USER_ID → USER_ID / USER_NAME → USER_NAME / EMAIL → EMAIL / GROUP_ID_LIST → GROUP_ID_LIST / ACTIVE_STATUS → ACTIVE_STATUS |
| Record Filtering | The value of ACTIVE_STATUS isY(Excluding resigners) |
| Default Email Domain | company.com(Email auto-generation when only employee number is present) |
Step 3 — Group Settings:
| item | Settings |
|---|---|
| Surveillance Mode | Single File |
| path | /hr/export |
| File Pattern | groups.csv |
| Handling Items Not Included in CSV | maintenance |
| Field Mapping | GROUP_ID → GROUP_ID / GROUP_NAME → GROUP_NAME / PARENT_GROUP_ID → PARENT_GROUP_ID |
Step 4 — Synchronization Settings:
| item | Settings |
|---|---|
| Automatic Synchronization | use |
| Start Time | 02:00 AM (1 hour after HR file creation) |
| Backup Before Synchronization | use |