# data[].attributes.body
Ransomware is a malware which threatens the victim and stops them from accessing their data or even steal it. The malware wants you to pay for your data back.
It happens commonly by email with attachments to download which then infects the computer and takes over therefore allowing the attacker to control the computer.
Another way could be criminal software so you won't have to send emails to get access.
The ransomware can only be decrypted with the key the attackers has so they would ask for an untraceable bitcoin.
Ransomware could happen to anyone but most likely people who pay fast or businesses.

# data[].attributes.body
"A data breach is a security incident in which sensitive, protected or confidential data is copied, transmitted, viewed, stolen or used by an individual unauthorized to do so."

# data[].attributes.body
Injection flaws are a class of security vulnerability that allows a user to “break out” of the web application context. If your web application takes user input and inserts that user input into a back-end database, shell command, or operating system call, your application may be susceptible to an injection flaw.

A user exploits this by breaking out the intended "context" and appends additional and often unintended functionality. By allows injection flaws in your application you are allowing an attacker to create, read, update or delete and arbitrary data available to the application.

# data[].attributes.body
There are many types of injection flaws. The most common being SQL injection.

# data[].attributes.body
loss or theft of hard copy notes, USB drives, computers or mobile devices

an unauthorised person gaining access to your laptop, email account or computer network

sending an email with personal data to the wrong person

a bulk email using 'to' or 'cc', but where 'bcc' (blind carbon-copy) should have been used

a disgruntled employee copying a list of contacts for their personal use

a break-in at the office where personnel files are kept in unlocked storage

# data[].attributes.body
Cross site scripting is a security flaw that exists because of how web browsers treat their information, such as cookies.
it involves injecting malicious code in a website, and using the websites permission to access information.
XSS requires a vector of attack such as an injection flaw, to add the malicious code to the website.

# data[].attributes.body
Create complex passwords.

Watch for fraud.

Guard against identity theft.

Set up account alerts.

Anti-malware software

# data[].attributes.body
There are multiple variants of cross site scripting meaning there is no single standardised classification. The primary variants are persistent and non-persistent.

Non-persistent (reflected):
Example of a non-persistent XSS flaw
Non-persistent XSS vulnerabilities in Google could allow malicious sites to attack Google users who visit them while logged in.
The non-persistent (or reflected) cross-site scripting vulnerability is by far the most basic type of web vulnerability. These holes show up when the data provided by a web client, most commonly in HTTP query parameters (e.g. HTML form submission), is used immediately by server-side scripts to parse and display a page of results for and to that user, without properly sanitizing the content.

Because HTML documents have a flat, serial structure that mixes control statements, formatting, and the actual content, any non-validated user-supplied data included in the resulting page without proper HTML encoding, may lead to markup injection. A classic example of a potential vector is a site search engine: if one searches for a string, the search string will typically be redisplayed verbatim on the result page to indicate what was searched for. If this response does not properly escape or reject HTML control characters, a cross-site scripting flaw will ensue.

A reflected attack is typically delivered via email or a neutral web site. The bait is an innocent-looking URL, pointing to a trusted site but containing the XSS vector. If the trusted site is vulnerable to the vector, clicking the link can cause the victim's browser to execute the injected script.

Persistent (or stored):
Example of a persistent XSS flaw
A persistent cross-zone scripting vulnerability coupled with a computer worm allowed execution of arbitrary code and listing of filesystem contents via a QuickTime movie on MySpace.
The persistent (or stored) XSS vulnerability is a more devastating variant of a cross-site scripting flaw: it occurs when the data provided by the attacker is saved by the server, and then permanently displayed on "normal" pages returned to other users in the course of regular browsing, without proper HTML escaping. A classic example of this is with online message boards where users are allowed to post HTML formatted messages for other users to read.

For example, suppose there is a dating website where members scan the profiles of other members to see if they look interesting. For privacy reasons, this site hides everybody's real name and email. These are kept secret on the server. The only time a member's real name and email are in the browser is when the member is signed in, and they can't see anyone else's.

Suppose that Mallory, an attacker, joins the site and wants to figure out the real names of the people she sees on the site. To do so, she writes a script designed to run from other users' browsers when they visit her profile. The script then sends a quick message to her own server, which collects this information.

To do this, for the question "Describe your Ideal First Date", Mallory gives a short answer (to appear normal) but the text at the end of her answer is her script to steal names and emails. If the script is enclosed inside a <script> element, it won't be shown on the screen. Then suppose that Bob, a member of the dating site, reaches Mallory's profile, which has her answer to the First Date question. Her script is run automatically by the browser and steals a copy of Bob's real name and email directly from his own machine.

Persistent XSS vulnerabilities can be more significant than other types because an attacker's malicious script is rendered automatically, without the need to individually target victims or lure them to a third-party website. Particularly in the case of social networking sites, the code would be further designed to self-propagate across accounts, creating a type of client-side worm.

The methods of injection can vary a great deal; in some cases, the attacker may not even need to directly interact with the web functionality itself to exploit such a hole. Any data received by the web application (via email, system logs, IM etc.) that can be controlled by an attacker could become an injection vector.

Server-side versus DOM-based vulnerabilities:
Example of a DOM-based XSS flaw
Before the bug was resolved, Bugzilla error pages were open to DOM-based XSS attacks in which arbitrary HTML and scripts could be injected using forced error messages.
Historically XSS vulnerabilities were first found in applications that performed all data processing on the server side. User input (including an XSS vector) would be sent to the server, and then sent back to the user as a web page. The need for an improved user experience resulted in the popularity of applications that had a majority of the presentation logic (maybe written in JavaScript) working on the client-side that pulled data, on-demand, from the server using AJAX.

As the JavaScript code was also processing user input and rendering it in the web page content, a new sub-class of reflected XSS attacks started to appear that was called DOM-based cross-site scripting. In a DOM-based XSS attack, the malicious data does not touch the web server. Rather, it is being reflected by the JavaScript code, fully on the client side.

An example of a DOM-based XSS vulnerability is the bug found in 2011 in a number of jQuery plugins. Prevention strategies for DOM-based XSS attacks include very similar measures to traditional XSS prevention strategies but implemented in JavaScript code and contained in web pages (i.e. input validation and escaping). Some JavaScript frameworks have built-in countermeasures against this and other types of attack — for example, Angular.js.

Self-XSS:
Self-XSS is a form of XSS vulnerability which relies on Social Engineering in order to trick the victim into executing malicious JavaScript code into their browser. Although it is technically not a true XSS vulnerability due to the fact it relies on socially engineering a user into executing code rather than a flaw in the affected website allowing an attacker to do so, it still poses the same risks as a regular XSS vulnerability if properly executed.

Mutated XSS (mXSS):
Mutated XSS happens when the attacker injects something that is seemingly safe but rewritten and modified by the browser while parsing the markup. This makes it extremely hard to detect or sanitize within the websites application logic. An example is rebalancing unclosed quotation marks or even adding quotation marks to unquoted parameters on parameters to CSS font-family.

# data[].attributes.body
Before calling an external function, verify that the data is what you expect. This is referred to as validation. For instance, if you expect your function to be passed a string that contains a user’s first name, should it contain any special characters? (John) is a valid name. But, (J<o>hn) isn’t. Both user names need to be ran through a validation function and in order for the web application to determine whether the data is what the developer expects.

# data[].attributes.body
SQL injection is a code injection technique that might destroy your database.

SQL injection is one of the most common web hacking techniques.

SQL injection is the placement of malicious code in SQL statements, via web page input.

# data[].attributes.body
Worm -  Worms are often disguised as attachments, or hidden inside attachments. When an infected attachment is opened, the worm is installed. Once a worm is on your computer, it can spread in a variety of ways, such as emailing itself to an address in your address book or searching your hard drive for email addresses.

Trojan -  They are a form of malware disguised as useful programs, or hidden inside of useful programs. Trojans are usually installed on people’s computers through trickery. A person receives a file or attachment, thinks it is legitimate, and downloads or installs it. Then, in the dark of night (or in broad daylight) the Trojan springs into action, deleting files, destroying information, and/or allowing outsiders to gain access and control the computer. Trojans do not reproduce or infect other files, and they do not replicate themselves.

Spyware -  This type of malware includes any type of program that spies on a person’s computer activities. Spyware may gather personal information such as usernames, passwords, or account numbers. It may track which websites you visit and what emails you write and receive. Spyware is usually installed unknowingly along with a product that was deliberately installed.

Viruses -  Viruses pass from one computer to another, much like biological viruses pass from one person to another. Computer viruses cannot reproduce on their own; like biological viruses, they need a host (i.e., a program or document) to do so. Viruses must be actively launched in order to cause trouble.

# data[].attributes.body
"the fraudulent practice of sending emails purporting to be from reputable companies in order to induce individuals to reveal personal information, such as passwords and credit card numbers."

# data[].attributes.body
Scammers sometimes send out emails that say "you have won the lottery" this is jjust a way for them to steal your personal info like name age address credit card info etc.
the "Nigerien scam" where someone stating that they are a Nigerian prince who has a large amount of money frozen in an account somewhere which they can give you a large amount of if you just give them some money to unfreeze the account

# data[].attributes.body
Elk Cloner, written in 1982 by then-15-year-old Rich Skrenta of Pittsburgh, was a boot-sector virus designed to infect Apply II computers and was the first to be detected in the wild.

# data[].attributes.body
ILOVEYOU - What it did was use social engineering to get people to click on the attachment; in this case, a love confession. The attachment was actually a script that poses as a TXT file, due to Windows at the time hiding the actual extension of the file. Once clicked, it will send itself to everyone in the user’s mailing list and proceed to overwrite files with itself, making the computer unbootable.

Code Red -  The worm targeted computers with Microsoft IIS web server installed, exploiting a buffer overflow problem in the system. It leaves very little trace on the hard disk as it is able to run entirely on memory, with a size of 3,569 bytes. Once infected, it will proceed to make a hundred copies of itself but due to a bug in the programming, it will duplicate even more and ends up eating a lot of the systems resources.

Melissa -  It started as an infected Word document that was posted up on the alt.sex usenet group, claiming to be a list of passwords for pornographic sites. This got people curious and when it was downloaded and opened, it would trigger the macro inside and unleash its payload. The virus will mail itself to the top 50 people in the user’s email address book and this caused an increase of email traffic, disrupting the email services of governments and corporations. It also sometimes corrupted documents by inserting a Simpsons reference into them.

Sasser -  it was created by computer science student Sven Jaschan, who also created the Netsky worm. While the payload itself may be seen as simply annoying (it slows down and crashes the computer, while making it hard to reset without cutting the power), the effects were incredibly disruptive, with millions of computers being infected, and important, critical infrastructure affected. The worm took advantage of a buffer overflow vulnerability in Local Security Authority Subsystem Service (LSASS), which controls the security policy of local accounts causing crashes to the computer. It will also use the system resources to propagate itself to other machines through the Internet and infect others automatically.

Zeus -  Zeus is a Trojan horse made to infect Windows computers so that it will perform various criminal tasks. The most common of these tasks are usually man-in-the-browser keylogging and form grabbing. The majority of computers were infected either through drive-by downloads or phishing scams.  It managed to compromise thousands of FTP accounts and computers from large multinational corporations and banks such as Amazon, Oracle, Bank of America, Cisco, etc. Controllers of the Zeus botnet used it to steal the login credentials of social network, email and banking accounts.

# data[].attributes.body
Identity theft online is mostly referred to as "Phishing" (or targeted attempts as spear phishing)
Phishing is a social engineering tactic designed to fool a victim into thinking the attacker is a trusted party, like a bank or company, that has request user details. Most of the time there is a sense of urgency to instill panic in the victim and have a higher chance of them responding.

The issue with Phishing is that the attempts are very broad and are easy to pick out, so this tactic unfortunately preys on the elderly or technically illiterate.

The lesser-known and more dangerous variant of Phishing is Spear Phishing, which is a targeted attack on a user or group of users that have a connection with one another (Like employees)
This is more dangerous than regular Phishing because the attacker can use information specific to an individual that may increase the perceived credibility of the attacker.

A famous example is the WannaCry ransomware. While it is ransomware in itself, the method of distribution was a form of Phishing, received via email with the attacker trying to fool victims into downloading the program.

Identity theft is the crime of impersonating someone else, mostly using stolen information or documents to falsely validate their claim.

A bad actor with your details can spend money on your behalf, impersonate you when talking to others and could possibly recover accounts by posing as you as if you had lost your password. These are the affects of identity fraud. This is as the fraudster gains a financial advantage over your loss. This is done through the use of obtaining credit or debit card information in the other parties name.

# data[].attributes.body
Identity theft is the deliberate use of someone else's identity, usually as a method to gain a financial advantage or obtain credit and other benefits in the other person's name, and perhaps to the other person's disadvantage or loss.

# data[].attributes.body
Identity fraud is the use by one person of another person's personal information, without authorization, to commit a crime or to deceive or defraud that other person or a third person

# data[].attributes.headline
What can a fraudster do with your details

# data[].attributes.subject
What can a fraudster do with your details

# data[].attributes.body
If they have your card details they can buy practically anything. if they have your account details they can use the certain account without you knowing to which they might beadle to get more information or just use the subscription you have paid for but they haven't

# data[].attributes.body
A computer program that records every keystroke made by a computer user, especially in order to gain fraudulent access to passwords and other confidential information.

# data[].attributes.body
A polymorphic virus is a complicated computer virus that affects data types and functions. It is a self-encrypted virus designed to avoid detection by a scanner. Upon infection, the polymorphic virus duplicates itself by creating usable, albeit slightly modified, copies of itself.

# data[].attributes.body
1. 123456

2. 123456789

3. qwerty

4. password

5. 111111

6. 12345678

7. abc123

8. 1234567

9. password1

10. 12345

# data[].attributes.body
Examples of firewall services:
- Tinywall
- Anti NetCut3
- PeerBlock

Types of firewalls:
- Proxy firewall
- Stateful inspection firewall
- Unified threat management (UTM)
- Next-generation firewall (NGFW)

# data[].attributes.body
A password is a string of characters used to verify the identity of a user during the authentication process. Passwords are typically used in conjuncture with a username; they are designed to be known only to the user and allow that user to gain access to a device, application or website.

Creating a secure password
Many organizations set password policies so employees create strong passwords and use best practices for their login credentials. Some of the best practices for password requirements include:

A minimum length of eight characters with a limit of anywhere from 16 to 64 characters or possibly even higher;
-The inclusion of both uppercase and lowercase letters with case sensitivity;
-The use of at least one number; and
-The use of at least one special character.

Policies should prohibit certain characteristics in weak passwords. For instance, any recognizable personal information -- such as birth dates, names of children, or favorite sports teams -- should not be part of a password, as well as any words or phrases that are on a password blacklist. Password blacklists are lists of passwords that are too easily cracked and thus are not secure enough to use. Common offenders that wind up on blacklists include "123456", "password", "football", "qwerty" and so on.

The use of passwords in computing dates back to 1961 when the Massachusetts Institute of Technology introduced the Compatible Time-Sharing System or CTSS. The CTSS was one of the first time-sharing operating systems and had a LOGIN command that required a user password.

In the 1970's Robert Morris, the cryptographer who famously created the Robert Morris worm, built a system for storing hashed passwords as a part of UNIX operating systems. This early form of encryption translated passwords into numeric values.

# data[].attributes.body
SSL Provides secure end to end encryption to connections between a host web server and a client. This means that attackers that try to intercept communications only get encrypted data they cannot decrypt with ease.

# data[].attributes.body
A firewall is a network security system that monitors and controls incoming and outgoing network traffic based on predetermined security rules. This means that it helps to prevent malicious content from being able to access the system and subsequently harm the system.

There are two main forms of Firewalls which are network firewalls or host-based firewalls. Network firewalls filter traffic between two or more networks and run on network hardware. Host-based firewalls run on host computers and control network traffic in and out of those machines.

Types of Firewalls
Packet-filtering firewalls
Stateful inspection firewalls
Circuit-level gateways
Application-level gateways (a.k.a. proxy firewalls)
Next-gen firewalls

port 80 - internet
port 25 - email , close unused ports

Next gen Firewalls
A next-generation firewall is a part of the third generation of firewall technology, combining a traditional firewall with other network device filtering functionalities, such as an application firewall using in-line deep packet inspection, an intrusion prevention system.

Packet filtering firewalls
Packet filtering fire walls monitoring outgoing and incoming packets and allowing them to pass or halt based on the source and destination Internet Protocol (IP) addresses, protocols and ports.

# data[].attributes.body
they are strings of letter and or numbers/symbols that are entered into something to gain access to said thing

# data[].attributes.body
Firewall is a network security system that monitors and controls incoming and outgoing network traffic based on predetermined security rules. A firewall typically establishes a barrier between a trusted internal network and untrusted external network, such as the Internet.