Anti-subversion software | Wikipedia audio article
Channel: wikipedia tts
Date: 18/01/2019

This is an audio version of the Wikipedia Article:
https://en.wikipedia.org/wiki/Anti-Subversion_Software





Listening is a more natural way of learning, when compared to reading. Written language only began at around 3200 BC, but spoken language has existed long ago.

Learning by listening is a great way to:
- increases imagination and understanding
- improves your listening skills
- improves your own spoken accent
- learn while on the move
- reduce eye strain

Now learn the vast amount of general knowledge available on Wikipedia through audio (audio article). You could even learn subconsciously by playing the audio while you are sleeping! If you are planning to listen a lot, you could try using a bone conduction headphone, or a standard speaker instead of an earphone.

Listen on Google Assistant through Extra Audio:
https://assistant.google.com/services/invoke/uid/0000001a130b3f91
Other Wikipedia audio articles at:
https://www.youtube.com/results?search_query=wikipedia+tts
Upload your own Wikipedia articles through:
https://github.com/nodef/wikipedia-tts
Speaking Rate: 0.8102679966038787
Voice name: en-AU-Wavenet-B


"I cannot teach anybody anything, I can only make them think."
- Socrates


SUMMARY
=======
Software subversion is the process of making software perform unintended actions either by tampering with program code or by altering behavior in another fashion. For example, code tampering could be used to change program code to load malicious rules or heuristics, SQL injection is a form of subversion for the purpose of data corruption or theft and buffer overflows are a form of subversion for the purpose of unauthorised access. These attacks are examples of computer hacking.
Anti-Subversion Software detects subversion and attempts to stop the effects of the hack. Software applications are vulnerable to the effects of subversion throughout their lifecycle from development to deployment, but particularly in operation and maintenance.Anti-subversion protection can be accomplished in both a static and dynamic manner:

Static anti-subversion is performed during the construction of the code.  The code is statically tested and verified against various attack types by examining the program source code.  Examples of static anti-subversion include security auditing, code verification, and fuzzing. Static anti-subversion is generally seen as a good coding practice, and is deemed necessary in some compliance regimes. However, static solutions cannot prevent all types of subversion attacks.
Dynamic anti-subversion is performed during code execution.  The code is dynamically protected against subversion by continuously checking for unintended program behaviours.  Examples of dynamic anti-subversion include application firewalls, security wrappers, and protection embedded in the software.Software applications running on desktops, corporate servers, mobile devices and embedded devices are all at risk from subversion.