Protecting sensitive payment data represents a fundamental challenge for modern digital businesses. Specifically, PCI DSS (Payment Card Industry Data Security Standard) v4.0 establishes even more stringent criteria for access control and user authentication mechanisms within the Cardholder Data Environment (CDE). This standard extends beyond mere compliance, aiming for substantial security enhancement and data protection against potential threats. This document provides an in-depth analysis focusing on PCI DSS v4.0's core requirements 7 (Assigning Access to System Components and Cardholder Data) and 8 (Identifying Users and Authenticating Access), exploring how Seekurity SIEM v3 can be leveraged to effectively meet these requirements and maximize the efficiency of security operations.
Scenario Introduction: A Financial Service Enterprise's Transition to PCI DSS v4.0
A mid-sized financial service enterprise in South Korea is actively pursuing business expansion by launching a new mobile payment platform, adapting to the rapidly evolving payment landscape. This platform processes a significant volume of cardholder data, and obtaining PCI DSS v4.0 certification was recognized as an essential step to secure corporate credibility and market competitiveness. The existing security infrastructure had been initially designed to comply with PCI DSS v3.2.1; however, the transition to v4.0 was deemed a comprehensive undertaking, requiring a complete overhaul of the overall security architecture and operational processes rather than a simple update. Specifically, access control and user authentication areas were highlighted as requiring the most significant changes, aligning with shifts in the threat environment. The enterprise established objectives to strengthen its capabilities for detecting and responding to the latest security threats while simultaneously establishing a systematic framework for regulatory compliance.
Challenges: Regulatory Compliance and Security Enhancement in a Complex Environment
During the PCI DSS v4.0 transition, this enterprise encountered several multifaceted challenges. First, operating a hybrid infrastructure that combined on-premises environments with cloud-based services (AWS, Azure) presented difficulties in establishing and applying consistent access control policies. Integrating and managing disparate access control mechanisms across each environment resulted in substantial operational overhead. Second, user access privileges for numerous system components and applications were not clearly defined, and control over third-party vendor and partner accounts was particularly insufficient. This presented a high potential for violating the Principle of Least Privilege, thereby increasing potential security threats. Third, existing user authentication methods predominantly relied on Single Factor Authentication, necessitating the urgent introduction of strong authentication and Multi-Factor Authentication (MFA). Specifically, the application of MFA for administrative access to the CDE and external remote access is a core requirement of PCI DSS v4.0, making the development of practical implementation strategies crucial. These challenges extended beyond mere technological adoption, acting as significant impediments to the organization's security governance and operational efficiency.
Technology Selection Process: Seekurity SIEM v3 as an Integrated Security Platform
The enterprise evaluated the adoption of an integrated security solution capable of meeting the stringent requirements of PCI DSS v4.0 while effectively managing complex hybrid environments and strengthening threat detection and response capabilities. Initially, the option of deploying individual access control solutions, IAM (Identity and Access Management) solutions, and SIEM solutions separately was considered. However, these disparate solutions were anticipated to present difficulties in integrated management and limitations in data correlation and analysis. Furthermore, increased licensing and operational costs for each separate solution also posed a significant burden. In contrast, the necessity for a solution capable of performing log collection, threat detection, access control monitoring, and authentication management within a unified platform emerged. Following a comparative analysis of various candidate solutions, the comprehensive functionalities and flexible scalability offered by Seekurity SIEM v3 were deemed most suitable for fulfilling PCI DSS v4.0 requirements. Seekurity SIEM v3's robust log analysis and correlation capabilities enable diligent monitoring of all access activities within the CDE, and its native support for access control features and user authentication management was particularly noteworthy. Specifically, NGINX-based network segment access control, its proprietary firewall, and per-account IP control features served as powerful advantages for effectively addressing the access control model definition in Requirement 7. Moreover, individual account creation for users, password policy management, and Google OTP/Apple OTP integrated MFA functionality were identified as essential elements for meeting the user identification and authentication requirements of Requirement 8. Seekurity SIEM v3's integrated management capabilities were thus evaluated as contributing to increased operational efficiency and an overall enhancement of security posture.
Implementation Process: Integrated Implementation of PCI DSS v4.0 Requirements 7 and 8 Based on Seekurity SIEM v3
The process of implementing PCI DSS v4.0's core requirements, 7 and 8, using Seekurity SIEM v3 requires systematic planning and a phased approach. Specific implementation strategies were established by mapping Seekurity SIEM v3's functionalities to each requirement.
PCI DSS v4.0 Requirement 7: Assigning Access to System Components and Cardholder Data
Requirement 7 mandates strict control over access to all system components and cardholder data within the CDE, based on the 'Need-to-Know' principle. Seekurity SIEM v3 addresses this requirement with the following functionalities:
- 7.1 Define an Access Control Model: An appropriate access control model must be defined based on the organization's business and access requirements, and minimum privileges should be assigned according to user job classifications and functions.
Seekurity SIEM v3 offers native network and account-based access control functionalities. NGINX-based network segment access control allows for the configuration of an IP whitelist for web interface access, ensuring that access to the Seekurity SIEM v3 console is restricted to authorized network segments only. This constitutes the most fundamental level of network access control.
# /etc/nginx/conf.d/seekurity.conf 예시
location / {
allow 192.168.1.0/24; # 내부 네트워크 대역 허용
allow 10.0.0.0/8; # 관리자 VPN 대역 허용
deny all;
proxy_pass http://backend_seekurity;
# ... 기타 설정
}
Furthermore, by utilizing Seekurity SIEM v3's KOVAN proprietary firewall network segment access control feature, granular control over communication between internal SIEM system components and specific port communication with external entities can be implemented. This enhances access control at the Network and Transport layers of the OSI 7-layer model. Additionally, the per-account IP control feature enables enforcement where specific user accounts can only log in from designated IP addresses, proactively blocking unauthorized access attempts from unexpected locations. This is particularly valuable for accounts with sensitive privileges, such as administrator accounts. Finally, the feature for assigning accessible accounts by linked Device/Type further refines the RBAC (Role-Based Access Control) model, allowing access privileges to specific device groups or log sources to be granted only to particular account groups. For instance, this enables network equipment log analysis personnel to be restricted from accessing server logs. These functionalities provide a solid foundation for effectively implementing the Principle of Least Privilege and role-based access control models mandated by PCI DSS v4.0.
- 7.2 Review All User Accounts and Privileges: All user accounts and access privileges, including those for third-party/vendor accounts, must be reviewed at least once every six months, maintained appropriately according to job functions, and inappropriate access must be addressed immediately.
Seekurity SIEM v3 provides detailed information through its account management status feature, including the last login timestamp of end-users and assigned privileges (indicating all groups). This functionality supports periodic account and privilege reviews, enabling the identification and remediation of accounts with prolonged inactivity or unnecessary privileges. Based on this information, responsible managers can approve the appropriateness of access and maintain records, thereby satisfying PCI DSS v4.0 Requirement 7.2. For third-party vendor accounts in particular, processes can be established through Seekurity SIEM v3's management features to limit their usage period and automatically deactivate or block access upon expiration.
PCI DSS v4.0 Requirement 8: Identifying Users and Authenticating Access
Requirement 8 emphasizes establishing robust identification and authentication mechanisms for all users within the CDE to prevent unauthorized access. Seekurity SIEM v3 effectively addresses this requirement by providing powerful user authentication and management functionalities.
- 8.1 Identify Users/Administrators and Manage Accounts: Assign unique IDs to all users, grant accounts and privileges only after approval by the responsible manager, immediately delete or deactivate accounts/privileges upon employee termination or departmental transfer, and delete/deactivate unused accounts within 90 days.
Seekurity SIEM v3 supports the individual account creation feature for each user, which inherently prevents the use of shared accounts. Each user accesses the system via a unique ID, enhancing the traceability of all activities for auditing purposes. An operational policy must be established to ensure that account creation and privilege assignment processes receive approval from the responsible manager, and a change history must be recorded. Furthermore, by utilizing Seekurity SIEM v3's account management interface, processes for immediately deleting or deactivating accounts and privileges for terminated employees or transferred personnel can be automated or handled swiftly manually. For accounts inactive for more than 90 days, the system notification feature can alert administrators, and a scheduling function to automatically deactivate such accounts in accordance with policy can also be considered.
- 8.2 Configure Password Policy: A robust password policy must be configured, including a password change cycle of 90 days, deactivation of unused accounts after 90 days, password complexity (combination of uppercase/lowercase letters, numbers, special characters), minimum password length, password history management, and lockout thresholds (e.g., 30-minute lockout after 10 failed attempts).
Seekurity SIEM v3 supports the global password policy setting feature. Administrators can centrally define password length, complexity requirements, change frequency, history management, and account lockout policies. The following is a hypothetical example of Seekurity SIEM v3's password policy configuration:
# Seekurity SIEM v3 Password Policy Configuration Example
password_policy:
min_length: 12
require_uppercase: true
require_lowercase: true
require_digit: true
require_special: true
max_age_days: 90 # 90일 마다 패스워드 변경 강제
history_count: 10 # 이전 10개 패스워드 재사용 금지
lockout_threshold: 10 # 10회 실패 시 계정 잠금
lockout_duration_minutes: 30 # 30분 동안 계정 잠금
idle_account_deactivation_days: 90 # 90일 미사용 시 비활성화
By applying such policies, users will adhere to the strict password requirements of PCI DSS v4.0. It is crucial to note that beyond merely setting password policies, clearly communicating them to users and encouraging compliance through regular training is equally important.
- 8.3 & 8.4 Establish Strong Authentication and Implement MFA: Use at least one authentication factor from passwords, tokens/smart cards, or biometrics, and implement MFA for all administrator non-console access to the CDE, all CDE access, and internal remote access from external networks.
Seekurity SIEM v3 supports MFA integration with Google OTP/Apple OTP in addition to ID/Password, thereby satisfying PCI DSS v4.0's strong authentication requirements. MFA combines two authentication factors—knowledge-based (password) and possession-based (OTP)—significantly reducing the likelihood of unauthorized access. The MFA implementation architecture is configured such that after a user enters their ID and password on the Seekurity SIEM v3 login page, they then provide a one-time password generated from their registered OTP app (Google OTP or Apple OTP). This authentication flow is as follows:
- The user accesses the Seekurity SIEM v3 login page and enters their user ID and password.
- The Seekurity SIEM v3 backend verifies the entered ID and password.
- If password verification is successful, the system requests the user to enter their registered OTP.
- The user enters the 6-digit code generated via their Google OTP or Apple OTP app on their smartphone.
- Seekurity SIEM v3 verifies the validity of the OTP based on the entered OTP code and the OTP seed value stored in the backend.
- Upon successful OTP verification, the user is granted access to the Seekurity SIEM v3 dashboard.
Such MFA must be mandatorily applied, especially for all administrative access to the CDE and remote access from external networks. A frequently overlooked aspect is interactive logins for system service accounts where MFA is not applied, thus requiring strict control over these areas.
- 8.5 Manage Interactive Logins: Restrict interactive use of system/application service accounts, and for exceptions, document time limits and business justification, obtaining administrator approval.
Seekurity SIEM v3's core service accounts (sekurity: Shell privileges for service execution, postgres: DB execution Shell privileges, nginx: web server) are fundamentally designed to restrict interactive logins. In exceptional cases where interactive login is necessary, administrators must clearly document the purpose, duration, access method, and business justification, and obtain approval from senior management. This approach involves minimizing Shell access privileges and DB connection privileges at the operating system level within Seekurity SIEM v3, and escalating privileges temporarily only when necessary. All interactive login attempts are logged by Seekurity SIEM v3, and threat detection rules can immediately identify and generate alerts for abnormal interactive login attempts.
- 8.6 Manage Service Accounts: Application/system account passwords must adhere to complexity of 3 combinations/15+ characters, encryption key management, and regular password changes must be managed.
Service account passwords within Seekurity SIEM v3 must also be rigorously managed in accordance with PCI DSS v4.0 requirements. The current state, where DB connection passwords within the ss-api.service file are stored in plaintext, is noted as slated for encryption improvement. Such sensitive information should be managed by integrating with a centralized secret management solution like Vault, or by leveraging features of cloud services such as Secrets Manager to securely store and control access. Establishing an encryption key management strategy and regularly performing key rotation policies is essential. Service account passwords should also have regular change cycles, and the change process should be implemented through automated scripts or a secret management solution. Seekurity SIEM v3 can collect logs of these internal system changes to provide audit information to administrators.
- 8.7 & 8.8 Password Reset and Account Authentication Methods: Functionality for individual password resets, beyond administrator resets, is planned for addition. The direction is toward resetting rather than retrieving existing passwords, identity verification via registered name/phone number/email, and improvement to allow separate account IDs rather than email addresses.
Considering both user convenience and enhanced security, Seekurity SIEM v3 is expected to add a feature in the future that allows users to reset their passwords directly. This improvement will guide users to set new passwords through a secure identity verification process (e.g., multi-factor identity verification via registered name, phone number, and email) rather than simply retrieving existing passwords. Furthermore, the system is planned to move away from using email addresses as account IDs, allowing for separate, unique account IDs. This will help reduce the risk of user ID exposure and ensure independence from potential threats arising from email system compromises. These enhancements are anticipated to play a crucial role in simultaneously securing strong authentication and flexible user management, as emphasized by PCI DSS v4.0.
Results and Achievements: Concurrent Growth in Regulatory Compliance and Security Operational Efficiency
The implementation of PCI DSS v4.0 Requirements 7 and 8 using Seekurity SIEM v3 yielded several quantitative and qualitative achievements for the enterprise. Quantitatively, a high compliance rate of over 95% was achieved for access control and user authentication-related items during the PCI DSS v4.0 audit process. Qualitatively, security personnel's understanding of PCI DSS v4.0 requirements significantly improved, and the overall security governance framework was assessed as having become more robust. Administrators gained the ability to monitor real-time access control status and user authentication logs through the Seekurity SIEM v3 dashboard, enabling swift responses in the event of abnormal activities.
Lessons Learned and Retrospection: Importance of an Integrated Platform and Necessity for Continuous Improvement
The most significant lesson learned from this PCI DSS v4.0 transition project was that utilizing an integrated platform is far more effective for regulatory compliance and security enhancement than relying on disparate security solutions. An integrated solution like Seekurity SIEM v3 significantly reduced operational complexity by enabling consistent management of access control, authentication, log management, and threat detection from a single dashboard. Contrary to initial expectations, it was reaffirmed that substantial effort is required to align the solution with existing operational processes, extending beyond mere solution adoption. For instance, initial resistance was encountered during the process of educating users and applying new RBAC models and MFA policies; however, these were successfully institutionalized through continuous explanation and feedback incorporation. If undertaken again, greater emphasis would be placed on user experience (UX) aspects from the initial planning stage to proactively secure resources necessary for change management. An unexpected tangential benefit was the additional strengthening of potential threat detection capabilities for general IT infrastructure outside the CDE, thanks to Seekurity SIEM v3's powerful log collection and analysis functionalities. This further clarified the value of the integrated threat detection and response platform offered by Seekurity SIEM/SOAR.
Application Guide: Phased Adoption Roadmap and Key Strategies for Success
Enterprises planning PCI DSS v4.0 certification and enhanced access control in similar environments can consider the following phased adoption roadmap. First, current environment analysis and scope definition are essential. The boundaries of the CDE must be clearly delineated, and the current status of access control and authentication must be thoroughly assessed. Second, focus must be placed on designing a new RBAC model and establishing policies. Leveraging Seekurity SIEM v3's feature for assigning accounts per linked Device/Type, roles based on the Principle of Least Privilege should be defined. Third, the introduction of MFA and strong password policies should be prioritized. MFA for CDE access and administrative access should be established using Seekurity SIEM v3's OTP integration features, and stringent password policies should be applied. Fourth, establish a log integration and monitoring system based on Seekurity SIEM v3. All access control and authentication-related events must be collected into the SIEM, and real-time threat detection rules should be configured to immediately detect abnormal activities. Finally, regular reviews and audits are critical to continuously verify the appropriateness of access privileges and periodically evaluate the effectiveness of security policies. Additionally, a strategic approach should consider leveraging AI-based analysis tools such as KYRA AI Guardrail for in-depth analysis of detected threats, and continuously optimizing cloud environment security through FRIIM CNAPP. This integrated approach will serve as a crucial turning point, elevating the organization's overall security posture beyond mere PCI DSS v4.0 compliance.







