CISSP-KR 문제 631
다음 중 "이그레스 포인트 데이터 유출 카나리 토큰(허니토큰)"의 목적을 가장 잘 설명하는 것은 무엇입니까?
정답: B
Canary tokens (a form of honeytoken) are fake but uniquely identifiable pieces of data-such as a bogus database credential, a fake API key, or a decoy document-strategically planted within an environment. Since no legitimate process should ever access or transmit them, any interaction with a canary token generates a high-fidelity alert, indicating potential unauthorized access, insider threat, or active data exfiltration.
CISSP-KR 문제 632
어떤 유형의 DRP(재해 복구 계획) 테스트가 운영상의 위험을 가장 많이 수반합니까?
정답: A
The type of disaster recovery plan (DRP) testing that carries the most operational risk is cutover.
DRP testing is the process of verifying and validating the effectiveness and readiness of the DRP, which is a plan that defines the procedures and resources for restoring the critical business functions and systems after a disaster or an outage. DRP testing can be performed using different methods, such as:
Cutover: This method involves switching the entire production environment to the backup or recovery site, and testing the functionality and performance of the systems and processes at the recovery site. This method provides the most realistic and comprehensive test of the DRP, but it also carries the most operational risk, as it may disrupt the normal business operations, cause data loss or inconsistency, or introduce errors or failures in the systems or processes.
Walkthrough: This method involves reviewing and discussing the DRP with the relevant stakeholders, such as the management, the staff, or the vendors, and identifying any gaps, issues, or improvements in the plan. This method provides the least realistic and comprehensive test of the DRP, but it also carries the least operational risk, as it does not involve any actual execution or switching of the systems or processes.
Tabletop: This method involves simulating a disaster scenario and testing the DRP with a selected group of participants, such as the DRP team, the business owners, or the auditors, and evaluating the roles, responsibilities, and actions of the participants. This method provides a moderate level of realism and comprehensiveness in testing the DRP, but it also carries a moderate level of operational risk, as it may require some preparation, coordination, or documentation of the simulation and the results.
Parallel: This method involves running the systems and processes at both the production and the recovery sites simultaneously, and comparing the outputs and outcomes of the sites. This method provides a high level of realism and comprehensiveness in testing the DRP, but it also carries a high level of operational risk, as it may consume more resources, cause data synchronization or duplication issues, or create conflicts or confusion between the sites.
DRP testing is the process of verifying and validating the effectiveness and readiness of the DRP, which is a plan that defines the procedures and resources for restoring the critical business functions and systems after a disaster or an outage. DRP testing can be performed using different methods, such as:
Cutover: This method involves switching the entire production environment to the backup or recovery site, and testing the functionality and performance of the systems and processes at the recovery site. This method provides the most realistic and comprehensive test of the DRP, but it also carries the most operational risk, as it may disrupt the normal business operations, cause data loss or inconsistency, or introduce errors or failures in the systems or processes.
Walkthrough: This method involves reviewing and discussing the DRP with the relevant stakeholders, such as the management, the staff, or the vendors, and identifying any gaps, issues, or improvements in the plan. This method provides the least realistic and comprehensive test of the DRP, but it also carries the least operational risk, as it does not involve any actual execution or switching of the systems or processes.
Tabletop: This method involves simulating a disaster scenario and testing the DRP with a selected group of participants, such as the DRP team, the business owners, or the auditors, and evaluating the roles, responsibilities, and actions of the participants. This method provides a moderate level of realism and comprehensiveness in testing the DRP, but it also carries a moderate level of operational risk, as it may require some preparation, coordination, or documentation of the simulation and the results.
Parallel: This method involves running the systems and processes at both the production and the recovery sites simultaneously, and comparing the outputs and outcomes of the sites. This method provides a high level of realism and comprehensiveness in testing the DRP, but it also carries a high level of operational risk, as it may consume more resources, cause data synchronization or duplication issues, or create conflicts or confusion between the sites.
CISSP-KR 문제 633
강력한 인증 사용, 데이터베이스 서버에서 개인 식별 정보(PII) 암호화, 애플리케이션 보안 검토 및 네트워크를 통해 전송되는 데이터 암호화는 다음과 같은 이점을 제공합니다.
정답: B
Defense in depth is a security strategy that involves applying multiple layers of protection to a system or network to prevent or mitigate attacks. The use of strong authentication, the encryption of Personally Identifiable Information (PII) on database servers, application security reviews, and the encryption of data transmitted across networks are examples of defense in depth measures that can enhance the security of the system or network.
CISSP-KR 문제 634
미디어 마킹과 미디어 라벨의 차이점은 무엇입니까?
정답: B
According to the CISSP CBK Official Study Guide, the difference between media marking and media labeling is that media labeling refers to the use of human-readable security attributes, while media marking refers to the use of security attributes in internal data structures. Media marking and media labeling are two methods or techniques of applying security attributes to the media, which are the physical or tangible devices or materials that store or contain the data or information, such as the disks, tapes, or papers. Security attributes are the tags or markers that indicate the classification, sensitivity, or clearance of the media, data, or information, such as top secret, secret, or confidential. Security attributes help to protect the media, data, or information from unauthorized or unintended access, disclosure, modification, corruption, loss, or theft, as well as to support the access control and audit mechanisms. Media labeling is the method or technique of applying security attributes to the media in a human-readable form, such as the words, symbols, or colors that are printed, stamped, or affixed on the media. Media labeling helps to identify and distinguish the media, data, or information based on their security attributes, as well as to inform and instruct the users or handlers of the media, data, or information about the proper and secure handling and disposal of them. Media marking is the method or technique of applying security attributes to the media in an internal data structure form, such as the bits, bytes, or fields that are embedded, encoded, or encrypted in the media. Media marking helps to verify and validate the media, data, or information based on their security attributes, as well as to enforce and monitor the access control and audit mechanisms for them. Media marking refers to security attributes required by public policy/law, while media labeling refers to security required by internal organizational policy is not the difference between media marking and media labeling, as it is not related to the form or format of the security attributes, but to the source or authority of the security attributes. Media marking and media labeling may both refer to security attributes required by public policy/law, such as the Controlled Unclassified Information (CUI) or the Personal Identifiable Information (PII), or to security attributes required by internal organizational policy, such as the proprietary or confidential information. The difference between media marking and media labeling is not based on who or what requires the security attributes, but on how the security attributes are applied or represented on the media.
CISSP-KR 문제 635
다음 중 소프트웨어 취득 중 보안 평가 요구 사항을 설명하는 것은 무엇입니까?
정답: A
A software assurance policy is a document that defines the standards, guidelines, and best practices for ensuring the quality, security, and reliability of software products and services. A software assurance policy can help address the requirements of security assessment during software acquisition, as it establishes the criteria and methods for evaluating and testing the software, as well as the roles and responsibilities of the stakeholders involved. A software assurance policy can help ensure that the software meets the functional and non-functional requirements, as well as the security and compliance requirements, of the organization.
Continuous monitoring is a process that involves collecting, analyzing, and reporting data on the performance and security of the systems and networks. Continuous monitoring can help maintain the security and availability of the systems and networks, but it does not address the security assessment during software acquisition. Software configuration management (SCM) is a process that involves controlling and tracking the changes and versions of the software products and components. SCM can help ensure the consistency and integrity of the software products and components, but it does not address the security assessment during software acquisition. Data loss prevention (DLP) policy is a document that defines the rules and actions for preventing the unauthorized disclosure, transfer, or leakage of sensitive data. DLP policy can help protect the data from being exposed, but it does not address the security assessment during software acquisition.
Continuous monitoring is a process that involves collecting, analyzing, and reporting data on the performance and security of the systems and networks. Continuous monitoring can help maintain the security and availability of the systems and networks, but it does not address the security assessment during software acquisition. Software configuration management (SCM) is a process that involves controlling and tracking the changes and versions of the software products and components. SCM can help ensure the consistency and integrity of the software products and components, but it does not address the security assessment during software acquisition. Data loss prevention (DLP) policy is a document that defines the rules and actions for preventing the unauthorized disclosure, transfer, or leakage of sensitive data. DLP policy can help protect the data from being exposed, but it does not address the security assessment during software acquisition.
- 최근 업로드
- 148Microsoft.DP-700-KR.v2026-08-20.q47
- 268ISC.CISSP-KR.v2026-08-20.q862
- 195Microsoft.SC-100-KR.v2026-08-20.q141
- 235Microsoft.AZ-305-KR.v2026-08-20.q223
- 842IIA.IIA-CIA-Part1-KR.v2026-08-19.q374
- 1336IIA.IIA-CIA-Part3-KR.v2026-08-19.q374
- 180Microsoft.DP-700-KR.v2026-08-19.q59
- 234AMP.CRL.v2026-08-18.q46
- 893Microsoft.AZ-305-KR.v2026-08-17.q162
- 235IIA.IAA-IAP-KR.v2026-08-17.q41
[×]
PDF 파일 다운로드
메일 주소를 입력하시고 다운로드 하세요. ISC.CISSP-KR.v2026-08-20.q862 모의시험 시험자료를 다운 받으세요.