ISO-IEC-27001-LEAD-AUDITOR · Question #204
Scenario 1: Fintive is a distinguished security provider for online payments and protection solutions. Founded in 1999 by Thomas Fin in San Jose, California, Fintive offers services to companies…
The correct answer is C. Preventive and technical. Black box testing is a preventive control because it is applied before software deployment to stop defects and vulnerabilities from ever reaching production - exactly what Fintive's new policy mandates. It is technical because it involves a systematic, tool-supported software…
Question
Scenario 1: Fintive is a distinguished security provider for online payments and protection solutions. Founded in 1999 by Thomas Fin in San Jose, California, Fintive offers services to companies that operate online and want to improve their information security, prevent fraud, and protect user information such as PII. Fintive centers its decision-making and operating process based on previous cases. They gather customer data, classify them depending on the case, and analyze them. The company needed a large number of employees to be able to conduct such complex analyses. After some years, however, the technology that assists in conducting such analyses advanced as well. Now, Fintive is planning on using a modern tool, a chatbot, to achieve pattern analyses toward preventing fraud in real-time. This tool would also be used to assist in improving customer service. This initial idea was communicated to the software development team, who supported it and were assigned to work on this project. They began integrating the chatbot on their existing system. In addition, the team set an objective regarding the chatbot which was to answer 85% of all chat queries. After the successful integration of the chatbot, the company immediately released it to their customers for use. The chatbot, however, appeared to have some issues. Due to insufficient testing and lack of samples provided to the chatbot during the training phase, in which it was supposed "to learn" the queries pattern, the chatbot failed to address user queries and provide the right answers. Furthermore, the chatbot sent random files to users when it received invalid inputs such as odd patterns of dots and special characters. Therefore, the chatbot was unable to properly answer customer queries and the traditional customer support was overwhelmed with chat queries and thus was unable to help customers with their requests. Consequently, Fintive established a software development policy. This policy specified that whether the software is developed in-house or outsourced, it will undergo a black box testing prior to its implementation on operational systems. What type of security control does the use of black box testing represent? Refer to scenario 1.
Options
- ACorrective and technical
- BDetective and managerial
- CPreventive and technical
How the community answered
(18 responses)- A11% (2)
- B6% (1)
- C83% (15)
Explanation
Black box testing is a preventive control because it is applied before software deployment to stop defects and vulnerabilities from ever reaching production - exactly what Fintive's new policy mandates. It is technical because it involves a systematic, tool-supported software testing methodology rather than a governance or administrative process.
Option A (Corrective and Technical) is wrong on the first word: corrective controls restore a system after an incident has already occurred (e.g., patching a live vulnerability). Testing before release is the opposite - it prevents the incident from happening.
Option B (Detective and Managerial) is wrong on both words: detective controls discover incidents after they occur (e.g., log monitoring, IDS alerts), and managerial/administrative controls are policy-based (e.g., writing the testing policy itself is managerial, but performing the test is technical).
Memory tip: Think "Pre-ventive = Pre-deployment." Any control that happens before a threat materializes is preventive; any control that uses software/hardware methods is technical. Black box testing sits squarely in the "before + technical" box - you test the software so the problem never reaches the customer.
Topics
Community Discussion
No community discussion yet for this question.