CISA-KR 문제 176
IS 감사인이 공유 CRM(고객 관계 관리) 시스템에 대한 액세스 제어를 평가하고 있습니다. 다음 중 가장 큰 관심사는 무엇입니까?
정답: B
Explanation
The greatest concern for an IS auditor evaluating the access controls for a shared customer relationship management (CRM) system is that audit logging is not enabled. Audit logging is a process that records and tracks the activities and events that occur on a system, such as who accessed what data, when, how, and why.
Audit logging can help monitor and verify the compliance and effectiveness of the access controls, as well as detect and investigate any unauthorized or suspicious access or actions. Audit logging can also provide evidence and accountability for the security and integrity of the system and the data.
Without audit logging, the IS auditor would not be able to audit the access controls for the shared CRM system, as there would be no reliable or traceable records of the access history or patterns. Without audit logging, the organization would also not be able to identify or respond to any potential breaches or incidents that may compromise the confidentiality, availability, or accuracy of the CRM data. Without audit logging, the organization would also not be able to demonstrate or prove its compliance with any applicable policies, regulations, or standards that may require audit logging for CRM systems.
Single sign-on is not enabled is not a great concern for an IS auditor evaluating the access controls for a shared CRM system, but rather a potential improvement or enhancement. Single sign-on is a process that allows users to access multiple systems or applications with one set of credentials, such as a username and password. Single sign-on can help simplify and streamline the user experience, as well as reduce the risk of password fatigue or compromise. However, single sign-on is not a mandatory or essential requirement for access controls, and it may also introduce some challenges or risks, such as dependency on a single point of failure or vulnerability.
Security baseline is not consistently applied is not a great concern for an IS auditor evaluating the access controls for a shared CRM system, but rather a minor issue or gap. Security baseline is a set of minimum security standards or requirements that apply to a system or application, such as password policies, encryption protocols, or firewall rules. Security baseline can help ensure that the system or application meets a certain level of security and compliance. However, security baseline is not a sufficient or comprehensive measure for access controls, and it may also need to be customized or adjusted according to the specific needs and risks of each system or application.
Complex passwords are not required is not a great concern for an IS auditor evaluating the access controls for a shared CRM system, but rather a common practice or recommendation. Complex passwords are passwords that are composed of a combination of different types of characters, such as letters, numbers, symbols, and cases. Complex passwords can help prevent or deter brute-force attacks or guessing attempts by making the passwords harder to crack or predict. However, complex passwords are not a guarantee or guarantee of security, and they may also have some drawbacks or limitations, such as user inconvenience, memorability issues, or reuse across multiple systems or applications.
References:
Customer Relationship Management Risks and Controls - CRM Simplified 1
Customer relationship management: A guide - Zendesk 2
How to Protect Your Customer Relationship Management (CRM) Data from Hackers 3 What is CRM? | A Definition by Salesforce 4
The greatest concern for an IS auditor evaluating the access controls for a shared customer relationship management (CRM) system is that audit logging is not enabled. Audit logging is a process that records and tracks the activities and events that occur on a system, such as who accessed what data, when, how, and why.
Audit logging can help monitor and verify the compliance and effectiveness of the access controls, as well as detect and investigate any unauthorized or suspicious access or actions. Audit logging can also provide evidence and accountability for the security and integrity of the system and the data.
Without audit logging, the IS auditor would not be able to audit the access controls for the shared CRM system, as there would be no reliable or traceable records of the access history or patterns. Without audit logging, the organization would also not be able to identify or respond to any potential breaches or incidents that may compromise the confidentiality, availability, or accuracy of the CRM data. Without audit logging, the organization would also not be able to demonstrate or prove its compliance with any applicable policies, regulations, or standards that may require audit logging for CRM systems.
Single sign-on is not enabled is not a great concern for an IS auditor evaluating the access controls for a shared CRM system, but rather a potential improvement or enhancement. Single sign-on is a process that allows users to access multiple systems or applications with one set of credentials, such as a username and password. Single sign-on can help simplify and streamline the user experience, as well as reduce the risk of password fatigue or compromise. However, single sign-on is not a mandatory or essential requirement for access controls, and it may also introduce some challenges or risks, such as dependency on a single point of failure or vulnerability.
Security baseline is not consistently applied is not a great concern for an IS auditor evaluating the access controls for a shared CRM system, but rather a minor issue or gap. Security baseline is a set of minimum security standards or requirements that apply to a system or application, such as password policies, encryption protocols, or firewall rules. Security baseline can help ensure that the system or application meets a certain level of security and compliance. However, security baseline is not a sufficient or comprehensive measure for access controls, and it may also need to be customized or adjusted according to the specific needs and risks of each system or application.
Complex passwords are not required is not a great concern for an IS auditor evaluating the access controls for a shared CRM system, but rather a common practice or recommendation. Complex passwords are passwords that are composed of a combination of different types of characters, such as letters, numbers, symbols, and cases. Complex passwords can help prevent or deter brute-force attacks or guessing attempts by making the passwords harder to crack or predict. However, complex passwords are not a guarantee or guarantee of security, and they may also have some drawbacks or limitations, such as user inconvenience, memorability issues, or reuse across multiple systems or applications.
References:
Customer Relationship Management Risks and Controls - CRM Simplified 1
Customer relationship management: A guide - Zendesk 2
How to Protect Your Customer Relationship Management (CRM) Data from Hackers 3 What is CRM? | A Definition by Salesforce 4
CISA-KR 문제 177
데이터 센터의 폐쇄 회로 텔레비전(CCTV) 감시 카메라와 관련된 다음 문제 중 IS 감사인이 가장 우려해야 하는 문제는 무엇입니까?
정답: A
Explanation
The most concerning issue associated with a data center's CCTV surveillance cameras is that the recordings are not regularly reviewed. This means that any unauthorized access, theft, vandalism, or other security incidents may go unnoticed and unreported. CCTV recordings are a valuable source of evidence and deterrence for data center security, and they should be monitored and audited periodically to ensure compliance with policies and regulations. If the recordings are not reviewed, the data center may face legal, financial, or reputational risks in case of a security breach or an audit failure.
The other options are less concerning because they do not directly affect the security of the data center. CCTV cameras are not required to be installed in break rooms, as they are not critical areas for data protection. CCTV records can be deleted after one year, as long as they comply with the data retention policy of the organization and the applicable laws. CCTV footage does not need to be recorded 24 x 7, as long as there is sufficient coverage of the data center during operational hours and when access is granted to authorized personnel.
References:
ISACA Journal Article: Physical security of a data center1
Data Center Security: Checklist and Best Practices | Kisi2
Video Surveillance Best Practices | Taylored Systems
The most concerning issue associated with a data center's CCTV surveillance cameras is that the recordings are not regularly reviewed. This means that any unauthorized access, theft, vandalism, or other security incidents may go unnoticed and unreported. CCTV recordings are a valuable source of evidence and deterrence for data center security, and they should be monitored and audited periodically to ensure compliance with policies and regulations. If the recordings are not reviewed, the data center may face legal, financial, or reputational risks in case of a security breach or an audit failure.
The other options are less concerning because they do not directly affect the security of the data center. CCTV cameras are not required to be installed in break rooms, as they are not critical areas for data protection. CCTV records can be deleted after one year, as long as they comply with the data retention policy of the organization and the applicable laws. CCTV footage does not need to be recorded 24 x 7, as long as there is sufficient coverage of the data center during operational hours and when access is granted to authorized personnel.
References:
ISACA Journal Article: Physical security of a data center1
Data Center Security: Checklist and Best Practices | Kisi2
Video Surveillance Best Practices | Taylored Systems
CISA-KR 문제 178
조직의 소프트웨어 개발자는 특정 데이터 형식으로 저장된 개인 식별 정보(Pll)에 액세스해야 합니다. 다음 중 개발자가 개발 및 테스트 환경에서 사용하도록 허용하면서 이 민감한 정보를 보호하는 가장 좋은 방법은 무엇입니까?
정답: A
Explanation
The best way to protect sensitive information such as personally identifiable information (PII) stored in a particular data format while allowing the software developers to use it in development and test environments is data masking. Data masking is a technique that replaces or obscures sensitive data elements with fictitious or modified data elements that retain the original format and characteristics of the data. Data masking can help protect sensitive information such as PII stored in a particular data format while allowing the software developers to use it in development and test environments by preventing the exposure or disclosure of the real data values without affecting the functionality or performance of the software or application. The other options are not as effective as data masking in protecting sensitive information such as PII stored in a particular data format while allowing the software developers to use it in development and test environments, as they have different limitations or drawbacks. Data tokenization is a technique that replaces sensitive data elements with non-sensitive tokens that have no intrinsic value or meaning. Data tokenization can protect sensitive information such as PII from unauthorized access or theft, but it may not retain the original format and characteristics of the data, which may affect the functionality or performance of the software or application.
Data encryption is a technique that transforms sensitive data elements into unreadable or unintelligible ciphertext using an algorithm and a key. Data encryption can protect sensitive information such as PII from unauthorized access or modification, but it requires decryption to restore the original data values, which may introduce additional complexity or overhead to the software development process. Data abstraction is a technique that hides the details or complexity of data structures or operations from users or programmers by providing a simplified representation or interface. Data abstraction can help improve the usability or maintainability of software or applications, but it does not protect sensitive information such as PII from exposure or disclosure. References: CISA Review Manual (Digital Version), Chapter 5, Section 5.3.2
The best way to protect sensitive information such as personally identifiable information (PII) stored in a particular data format while allowing the software developers to use it in development and test environments is data masking. Data masking is a technique that replaces or obscures sensitive data elements with fictitious or modified data elements that retain the original format and characteristics of the data. Data masking can help protect sensitive information such as PII stored in a particular data format while allowing the software developers to use it in development and test environments by preventing the exposure or disclosure of the real data values without affecting the functionality or performance of the software or application. The other options are not as effective as data masking in protecting sensitive information such as PII stored in a particular data format while allowing the software developers to use it in development and test environments, as they have different limitations or drawbacks. Data tokenization is a technique that replaces sensitive data elements with non-sensitive tokens that have no intrinsic value or meaning. Data tokenization can protect sensitive information such as PII from unauthorized access or theft, but it may not retain the original format and characteristics of the data, which may affect the functionality or performance of the software or application.
Data encryption is a technique that transforms sensitive data elements into unreadable or unintelligible ciphertext using an algorithm and a key. Data encryption can protect sensitive information such as PII from unauthorized access or modification, but it requires decryption to restore the original data values, which may introduce additional complexity or overhead to the software development process. Data abstraction is a technique that hides the details or complexity of data structures or operations from users or programmers by providing a simplified representation or interface. Data abstraction can help improve the usability or maintainability of software or applications, but it does not protect sensitive information such as PII from exposure or disclosure. References: CISA Review Manual (Digital Version), Chapter 5, Section 5.3.2
CISA-KR 문제 179
감사 중에 IS 감사인은 시스템에서 과도한 권한이 제거되지 않은 경우가 많다는 사실을 발견했습니다.
다음 중 감사인이 가장 추천하는 것은 무엇입니까?
다음 중 감사인이 가장 추천하는 것은 무엇입니까?
정답: D
Explanation
The best recommendation for the auditor to make is D. Line management should regularly review and request modification of access rights. Access rights are the permissions and privileges granted to users to access, view, modify, or delete data or resources on a system or network1. Excessive rights are access rights that are not necessary or appropriate for a user's role or function, and may pose a risk of unauthorized or inappropriate use of data or resources2. Therefore, it is important to ensure that access rights are aligned with the principle of least privilege, which means that users should only have the minimum level of access required to perform their duties2.
Line management is responsible for overseeing and supervising the activities and performance of their staff, and ensuring that they comply with the organization's policies and standards3. Therefore, line management should regularly review and request modification of access rights for their staff, as they are in the best position to:
Understand the roles and functions of their staff, and determine the appropriate level of access rights needed for them to perform their duties effectively and efficiently.
Monitor and evaluate the usage and behavior of their staff, and identify any changes or anomalies that may indicate excessive or inappropriate access rights.
Communicate and collaborate with IT security or system administrators, who are responsible for granting, revoking, or modifying access rights, and request any necessary adjustments or corrections.
The best recommendation for the auditor to make is D. Line management should regularly review and request modification of access rights. Access rights are the permissions and privileges granted to users to access, view, modify, or delete data or resources on a system or network1. Excessive rights are access rights that are not necessary or appropriate for a user's role or function, and may pose a risk of unauthorized or inappropriate use of data or resources2. Therefore, it is important to ensure that access rights are aligned with the principle of least privilege, which means that users should only have the minimum level of access required to perform their duties2.
Line management is responsible for overseeing and supervising the activities and performance of their staff, and ensuring that they comply with the organization's policies and standards3. Therefore, line management should regularly review and request modification of access rights for their staff, as they are in the best position to:
Understand the roles and functions of their staff, and determine the appropriate level of access rights needed for them to perform their duties effectively and efficiently.
Monitor and evaluate the usage and behavior of their staff, and identify any changes or anomalies that may indicate excessive or inappropriate access rights.
Communicate and collaborate with IT security or system administrators, who are responsible for granting, revoking, or modifying access rights, and request any necessary adjustments or corrections.
CISA-KR 문제 180
IS 감사인은 주요 인터넷 연결 시스템이 공격에 취약하고 패치를 사용할 수 없음을 발견했습니다. 감사인이 가장 먼저 수행해야 할 작업은 무엇입니까?
정답: D
Explanation
The first step in addressing a vulnerability is to evaluate the associated risk, which involves assessing the likelihood and impact of a potential exploit. Based on the risk assessment, the appropriate mitigation strategy can be determined, such as implementing a new system, adding firewalls, or decommissioning the server.
References: ISACA CISA Review Manual 27th Edition, page 280
The first step in addressing a vulnerability is to evaluate the associated risk, which involves assessing the likelihood and impact of a potential exploit. Based on the risk assessment, the appropriate mitigation strategy can be determined, such as implementing a new system, adding firewalls, or decommissioning the server.
References: ISACA CISA Review Manual 27th Edition, page 280
- 다른 버전
- 3874ISACA.CISA-KR.v2026-05-16.q709
- 1778ISACA.CISA-KR.v2026-05-06.q261
- 3096ISACA.CISA-KR.v2026-03-16.q665
- 4449ISACA.CISA-KR.v2026-03-07.q651
- 9187ISACA.CISA-KR.v2025-04-07.q633
- 4439ISACA.CISA-KR.v2025-04-03.q628
- 3640ISACA.CISA-KR.v2025-04-02.q544
- 4200ISACA.CISA-KR.v2025-03-31.q534
- 5303ISACA.CISA-KR.v2025-03-28.q617
- 3101ISACA.CISA-KR.v2025-03-19.q581
- 3962ISACA.CISA-KR.v2025-03-03.q807
- 2793ISACA.CISA-KR.v2024-01-31.q392
- 5260ISACA.CISA-KR.v2023-10-24.q329
- 5189ISACA.CISA-KR.v2023-07-31.q266
- 3098ISACA.CISA-KR.v2023-06-23.q324
- 최근 업로드
- 133Microsoft.DP-900-KR.v2026-08-13.q130
- 227Microsoft.PL-600.v2026-08-11.q206
- 168Microsoft.DP-100.v2026-08-11.q160
- 167Oracle.1Z0-1048-25.v2026-08-11.q68
- 140ISQI.CTAL-TAE.v2026-08-11.q37
- 185ServiceNow.CIS-HR.v2026-08-11.q84
- 255Salesforce.Plat-Arch-201.v2026-08-10.q101
- 240Databricks.Databricks-Machine-Learning-Professional.v2026-08-10.q76
- 189F5.F5CAB2.v2026-08-10.q41
- 297APA.CPP-Remote.v2026-08-08.q109
[×]
PDF 파일 다운로드
메일 주소를 입력하시고 다운로드 하세요. ISACA.CISA-KR.v2024-02-07.q421 모의시험 시험자료를 다운 받으세요.