Page 143 - CyberSecurityEssentialsEnglish

● Remember: Section summary
• Key idea: A claim of Arabic support is not a test, because the difficulty sits in dialect,
terminology, numbers, and layout.
• Practical decision: Build cases across the varieties you actually receive, and score
language and fact separately.
• Mistake to avoid: Merging language quality and factual quality into one number, which

hides which of them failed.

3.10 The Seven-Factor Matching Framework

◆ Key idea: gates come before weights.
A tool that fails a legal, security, or verification condition is not rescued by a high score
elsewhere. Apply the mandatory conditions first, then use the weighted factors to choose
among what remains acceptable.

+ Methodological note: the status of this framework

The seven-factor matching framework is a teaching aid prepared by the author. It is not
an international standard or an established research model. Its purpose is to organize a
decision and document it, with the weights adjusted to the context.

Begin with the Mandatory Gates

Before any score is calculated, there are conditions whose failure requires rejecting the tool
or changing the scope of use. Good qualities do not compensate for a legal or security
breach, or for the absence of a verifiable source in a high-impact task.

• The data may lawfully be sent to or stored in this service.
• The tool reads the required file type and medium in a way that can be tested.
• A source, a log, or a method of verification exists that matches the impact of failure.

• The license permits the intended use, and modification or distribution where needed.
• Human review, permissions, and appropriate limits on execution are in place.
• A means of export, rollback, or substitution exists if the process depends on the tool.

142