Okuzeka
Software Engineering vocabulary · APIs, Networking and Security

Finding

Meaning in software engineering, with examples

/ˈfaɪndɪŋ/nounCommon term

In software engineering, finding means: A security problem or weakness that is identified and documented during an audit, assessment or penetration test, usually with a severity rating.

In Turkish: bulgu, tespit

How it is used

Normally used in the plural in reports: 'key findings', 'high-severity findings'. Each finding has a description, evidence, a risk rating and a remediation recommendation. Teams close or accept findings, and testers retest them.

Example sentences

  1. The report has 14 findings: two high, five medium and seven low.

  2. This finding is a false positive, because the service is not reachable from outside.

Common collocations

  • key findings
  • high-severity finding
  • close a finding
  • audit finding
  • retest a finding
  • penetration testAn authorised, simulated attack on a system, application or network, carried out by security specialists to find weaknesses before real attackers do.
  • auditA formal, independent review that checks whether an organisation's security controls and processes meet a standard, a law or its own policies.
  • remediationThe work of fixing a security problem at its source, such as applying a patch, changing a configuration or rewriting vulnerable code.
  • proof of conceptA small, quick version of an idea, built only to show that it can work technically before the team spends time building it properly.

This word in other fields

The same English word can have a different meaning in another field:

More terms: APIs, Networking and Security

Practise with graded reading

Reading at the right level is the fastest way to make new words stick. Pick free English books by level: