Skip to content

Black Box Testing

What is Black Box Testing?

A security testing approach where the tester has no prior knowledge of the target system's internal workings, simulating an external attacker.

Information Security

What the standards actually require on black box testing

Requirements naming black box testing across 4 standards, quoted from the control text.

Table A.6 lists the integration techniques: functional (black-box) testing (per Table A.14) HR at every SIL including Basic Integrity, and performance testing (Table A.18) R at SIL 1 and 2 and HR at SIL 3 and 4.

en-50126-en-50128-en-50129-railway-applications-rams::50128:A.6 · Table A.6: integration (7.3 and 7.6) →

For software validation the table lists probabilistic testing, process simulation, modelling, functional and black-box testing (HR at every SIL), and forward traceability from the SSRS to the software validation plan, and backward from that plan to the SSRS (b...

iec-61508-2010-functional-safety-of-e-e-pe-safety-related-systems::3-A.7 · Part 3, Annex A Table A.7 Software aspects of system safety validation techniques →

Table A.7 grades three overall-level techniques: performance testing (Table A.18) HR at SIL 1 and 2 and M at SIL 3 and 4; dynamic analysis and testing, expanded in Table A.13, HR at Basic Integrity to SIL 2 and M at SIL 3 and 4;

en-50716-2023-railway-applications-requirements-for-software-development::A.7 · Table A.7: overall software analysis and testing (6.2 and 7.2) →

Validation shows that the process in the work instruction meets the requirements agreed with the client, by evidence that it gives correct outputs for the defined inputs, without looking at how it is implemented;

iso-iec-27041-2015::5.9.1 · 5.9.1 General principles of validation →

Questions people ask about black box testing

What is Black Box Testing?
A security testing approach where the tester has no prior knowledge of the target system's internal workings, simulating an external attacker.
Why is Black Box Testing important for compliance?
Black Box Testing is a key concept in Information Security. Understanding black box testing helps organizations meet regulatory requirements, reduce risk, and demonstrate due diligence during audits. Our compliance platform maps 1,016 frameworks with 316K cross-framework control mappings.
Which compliance frameworks address Black Box Testing?
Black Box Testing appears in the requirement text of EN 50126 / EN 50128 / EN 50129 - Railway Applications RAMS, IEC 61508:2010 - Functional Safety of E/E/PE Safety-related Systems, EN 50716:2023 - Railway Applications - Requirements for Software Development, ISO/IEC 27041:2015. Across these standards we have identified 8 controls that name it directly, each linked to the control text on the compliance platform.
Where can I learn more about Black Box Testing?
Explore our compliance framework pages to see how black box testing applies across different standards and regulations. Our implementation guides provide step-by-step guidance, and the compliance platform offers AI-powered analysis of how this concept maps across 1,016 frameworks.

See how Black Box Testing applies across compliance frameworks

Our platform maps 1,016 frameworks with 316K cross-framework control mappings. Explore how this concept is addressed across standards.

Written and maintained by Gerard Blokdyk, The Art of Service.