1266
Comments (23)
sorted by:
You're viewing a single comment thread. View all comments, or full comment thread.
1
Shadowreaper07 1 point ago +1 / -0

If you're aiming to cheat, you make sure your system doesn't have basic logic tests, checks, and balances, that outright prevent you from doing things the system does not expect.

Years ago; I worked for the British Welfare System (I know, the Irony) within the realm of systems and data integrity.

These systems have so many checks and balances that if you even try to alter something to an impossibility (E.g. Over 100%) the system will flag it as an impossibility.

If you then try and bypass it, the system will flag a calculation discrepancy.

If you then try and force it through anyway, it will escalate it to the Security and Integrity who will then review the history of this case and review why these decisions are being made.

If it then passes all of these checks, it then sends off a bug-report to the service provider, is logged within our own systems, and is then passed as an "Anomaly" to the Section 151 Officer.

After all this, it then gets passed through to Audit and is purposefully flagged for Auditors due to the sheer irregularity of it such that if they get this wrong, they would be absolutely crucified.


This doesn't mean that there aren't instances of fraud within the British Welfare system by the administration, there absolutely is, but it is so rare because of the number of external checks are so high.

There isn't a single way that Dominion systems are designed in any way other than to cheat.