Computer fraud is the use of a computer system, network or digital data to deceive someone and obtain an unlawful gain or cause a loss. It covers acts such as altering records, spoofing identities, or using unauthorised access to manipulate transactions or information.
What Computer Fraud Means in Practice
Computer fraud is not just “fraud that happens on a computer”, it is fraud enabled by digital systems themselves, where false data, manipulated access, or deceptive system activity is used to create an unlawful gain or cause a loss.
In practice, the defining feature is that the computer environment is part of the fraud method, not merely the record-keeping layer. That makes it broader than a simple financial scam, because the abuse can involve records, identities, transactions, workflows, or system controls.
Common Forms of Computer Fraud
Computer fraud often appears as record tampering, account or identity spoofing, transaction manipulation, or unauthorized changes to data that downstream systems trust. The fraud may be obvious, such as altering payment details, or subtle, such as changing reference data that later drives an approved business action.
It also includes misuse of privileged access or application logic to make a system produce a false outcome. A key pattern is trust abuse: the system continues to operate “normally”, but its inputs, outputs, or approvals have been corrupted.
Why Computer Fraud Is Dangerous
Computer fraud is dangerous because digital systems scale deception. A single successful manipulation can propagate into many records, many transactions, or many automated decisions, creating losses that are hard to unwind. It can also undermine confidence in the integrity of the platform, not just the affected transaction.
When fraud uses stolen credentials, manipulated sessions, or unauthorised access, the harm often extends beyond the immediate financial loss. The same access path may expose customer records, internal workflows, or business-critical data used for later abuse.
Detection and Control Signals
Detection usually depends on correlating data integrity, access, and transaction patterns rather than looking for one obvious alert. Unusual changes to master data, mismatched approvals, repeated failed sign-ins followed by success, or transactions that diverge from normal timing and routing can all be indicators.
Controls are strongest when organisations combine strong access governance, segregation of duties, transaction review, logging, and integrity checks. For identity-related abuse patterns, practitioners can use US Computer Fraud and Abuse Act Guide and Computer Misuse and Anti-Hacking Laws Guide to connect technical misuse with authorisation and legal-risk boundaries.
Risk and Threat Considerations
Computer fraud is risky because it turns trusted digital workflows into attack surfaces. The most common failure mode is not a single “broken system”, but a chain of weak authentication, excessive access, weak reconciliation, and over-trusted records that lets false data move through ordinary business processes.
Failure mechanism: An attacker, insider, or unauthorised user alters records, impersonates a legitimate actor, or abuses access in a way the organisation’s controls treat as valid, so the fraud is accepted as ordinary system activity.
Impact: The result can include direct financial loss, fraudulent transfers, corrupted reporting, disputed transactions, customer harm, and costly forensic review to determine what was changed and what downstream decisions were affected.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP API Security Top 10 and MITRE ATT&CK address the attack and risk surface, while NIST SP 800-53 Rev 5 sets the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | AU-6 — Audit Review, Analysis, and Reporting | Computer fraud relies on hidden manipulations that audit review can surface. |
| AC-6 — Least Privilege | Excessive access is a common enabler of computer fraud through unauthorized data manipulation. | |
| IA-5 — Authenticator Management | Compromised or misused credentials are a frequent route into computer fraud cases. | |
| Recommendation — Correlate transaction and access logs to detect suspicious record changes and fraudulent sequences. Limit users and processes to the minimum access needed to change records or approve transactions. Protect, rotate, and monitor authenticators to reduce account abuse that enables fraudulent activity. | ||
| OWASP API Security Top 10 | API5 — Broken Function Level Authorization | Computer fraud often abuses application functions to perform unauthorized changes or approvals. |
| Recommendation — Verify function-level authorization so only permitted actors can invoke sensitive state-changing actions. | ||
| MITRE ATT&CK | T1078 — Valid Accounts | Fraud frequently uses legitimate accounts or stolen credentials to blend in with normal activity. |
| Recommendation — Hunt for misuse of valid accounts when activity looks operationally normal but business logic is abnormal. | ||
Practitioner Guidance
Why practitioners should care: Computer fraud is usually a cross-control problem, not a single-control problem. Security teams, fraud teams, and business owners all need to understand where trusted data becomes decision-making input, because that is where manipulation turns into loss.
What to watch for: Focus on identity anomalies, privileged changes, unusual transaction sequences, and edits to reference data or approvals. Where the environment exposes APIs or automated workflows, review access paths that can change records without a human reviewing the business consequence.
Practitioner takeaway: The most effective countermeasure is to make deception expensive, visible, and reversible, by reducing standing trust in both users and data.