Skip to content

Commit

Permalink
Update Why our work matters “_index”
Browse files Browse the repository at this point in the history
  • Loading branch information
ser1aa authored Aug 1, 2024
1 parent 800b897 commit dbd77c6
Show file tree
Hide file tree
Showing 2 changed files with 43 additions and 84 deletions.
79 changes: 24 additions & 55 deletions content/why-our-work-matters/_index.en.md
Original file line number Diff line number Diff line change
@@ -1,113 +1,82 @@
---
title: DIVD's work is of great importance, here is why
intro: >-
Working for DIVD, we aim to make the digital world safer by reporting
vulnerabilities we find in digital systems to the people who can mitigate
them.
intro: |-
Working for DIVD, we aim to make the digital world safer by reporting vulnerabilities we find in digital systems to the people who can mitigate them.
But what are exactly are (zero-day) vulnerabilities, and why is it so important to find them as soon as possible? Find these (and other) frequently used cyber security definitions on this page.
leftblock:
image: ""
alt: null
content: >-
content: |-
## **Security Vulnerability**
According to [NIST](https://csrc.nist.gov/glossary/term/vulnerability#:~:text=Definitions%3A,triggered%20by%20a%20threat%20source.) (National Institute of Standards and Technology), a vulnerability is a “w*eakness in an information system, system security procedures, internal controls, or implementation that could be exploited or triggered by a threat source.*”
Essentially, a security vulnerability is a weakness or flaw in a computer system, network, or software that can be exploited by cybercriminals to gain unauthorized access to systems and/or cause damage. Common examples of vulnerabilities are misconfigurations, unpatched software or firmware, the use of weak or default passwords, and the use of old protocols and standards.
Essentially, a security vulnerability is a weakness or flaw in a computer system, network, or software that can be exploited by cyber attackers to gain unauthorized access or cause damage. Examples of vulnerabilities can be software bugs, or systems that lack the latest security updates.
Let’s compare a system vulnerability to a misplaced or broken lock, using the analogy of a house. Inside your house, you keep your valuable belongings and sensitive secrets. If there’s a hole in the wall or the doors are accidentally left unlocked, it provides an opportunity for intruders to get inside.
When cybercriminals discover a vulnerability on a system, they will try to create a way to *exploit* it, to achieve actions on objectives. An *exploit* is basically a malicious piece of code or script that can be used to take advantage of a system's vulnerability.
When cybercriminals are able to exploit a vulnerability in a system to gain access to critical systems, they can potentially view, modify, delete and/or extract sensitive data. As soon as an intruder gets in, secrets are no longer secret. If an organisation doesn't find and mitigate vulnerabilities in time, the consequences can be severe, ranging from financial losses to irreparable damage to the organisation's reputation.
If an organisation doesn't find and mitigate vulnerabilities, the consequences can be severe, ranging from financial losses to irreparable damage to its reputation.
learnmore: /
rightblock:
Cybercriminals often prefer to create exploits for big, well-known issues because they can use those exploits to create powerful, cheap attacks that work for many years and on many systems.
image: ""
Alt tag for image: ""
learnmore: /
alt: null
content: >-
rightblock:
content: |-
## **Zero-day Vulnerability**
Ideally, a discovered vulnerability is directly reported to the vendor. The vendor rewards the finder (often via a bug bounty program) and agrees with the finder to keep the software vulnerability a secret. The vendor then creates a patch and (periodically) releases updates containing one or more security patches. Thus, the vendor is aware of the issue and provides a fix.
However, sometimes a “zero-day vulnerability” occurs. A zero-day (0-day) vulnerability is a specific type of security flaw that is unknown to the software developers and the security community at the time it is discovered by hackers. Because the vulnerability is not yet known, no one can properly protect against it.
Returning to the house analogy, imagine advertising on the internet that you’ve left your front door open while you’re away for the weekend. Because you are away, you can not protect your house and all your precious belongings.
🤓 *The term ‘zero-day’ reflects that the developers had zero days to develop a fix.*
🤓 *Eternal Blue is a very infamous zero-day exploit that was originally was developed by the NSA and later leaked by a hacking group. It was used in the [WannaCry ransomware attack](https://en.wikipedia.org/wiki/WannaCry_ransomware_attack), which affected hundreds of thousands of computers worldwide.*
learnmore: null
belowwoordenboek: >-
image: ""
Alt tag for image: ""
learnmore: ""
alt: null
contenttitle: "## DIVD’s efforts are invaluable to society for several reasons"
belowwoordenboek: |-
**Availability**\
At DIVD, we adhere to the ‘Principle of Proportionality’ and the ‘Principle of Subsidiarity’, as described in our [Code of Conduct](https://www.divd.nl/what-we-do/code-of-conduct/). This means that our research should increase and not decrease the integrity and availability of any and all online systems. If several means are available to meet the need, we opt for the one which has the least impact on the availability of the systems and services.
**Case**\
When DIVD talks about a “case” we refer to a record or file created to document and manage the process of addressing a specific vulnerability. It typically includes details such as:
* Description of the Vulnerability: Information about the nature and specifics of the vulnerability.
* Fingerprint Creation: A unique identifier or signature for the vulnerability to help in identifying affected systems.
* Scanning and Identification: The process of scanning systems to find instances that are vulnerable.
* Notification: Informing the owners of the vulnerable systems about the issue so they can take corrective action.
* This structured approach helps ensure that vulnerabilities are tracked, managed, and resolved systematically.
- Description of the Vulnerability: Information about the nature and specifics of the vulnerability.
- Fingerprint Creation: A unique identifier or signature for the vulnerability to help in identifying affected systems.
- Scanning and Identification: The process of scanning systems to find instances that are vulnerable.
- Notification: Informing the owners of the vulnerable systems about the issue so they can take corrective action.
- This structured approach helps ensure that vulnerabilities are tracked, managed, and resolved systematically.
**Confidentiality**\
At DIVD, we work with sensitive data every day. Think about lists of IP addresses, types of vulnerabilities found, contact information, and metadata (e.g. timestamps, scripts, researchers working on the data). [The members of DIVD](https://www.divd.nl/who-we-are/team/) take all precautions necessary to protect the confidentiality of this data.
**(Ethical) Hacker / White Hat Hacker**\
DIVD members belong to the “white hat” hackers. A white hat hacker is someone who breaks into a computer system with positive intentions, without disrupting any services or processes. The motivation of a white hat hacker is to detect security vulnerabilities, without misusing or exploiting them. A white hat hacker is sometimes also referred to as an ethical hacker. Our members are skilled professionals that must always operate within legal boundaries. Please read our [Code of Conduct](https://www.divd.nl/what-we-do/code-of-conduct/) for more information. *The term ‘white hat’ comes from cowboy movies in which the hero always wore a white hat.*
**Exploit**\
An exploit is a malicious application, piece of code or script that can be used to take advantage of a system's vulnerability. At DIVD, we don’t use or run intrusive exploits to verify the existence of a vulnerability in a system. Destructive commands like “$ rm -rf /” or testing for denial of service are not permitted in any scenario. If several means are available to meet the need, we opt for the one which has the least impact on the availability of the systems and services.
An exploit is a malicious application, piece of code or script that can be used to take advantage of a system's vulnerability. At DIVD, we don’t use or run intrusive exploits to verify the existence of a vulnerability in a system. Destructive commands like “$ rm -rf /” or testing for denial of service are not permitted in any scenario. If several means are available to meet the need, we opt for the one which has the least impact on the availability of the systems and services.
**Responsible disclosure**\
In cybersecurity, responsible disclosure refers to the procedure where a security analyst, ethical hacker, or ethical hacker organisation such as DIVD notifies an organisation about a detected vulnerability in its systems or software. Notifying is done in such a way that the organisation has the opportunity to mitigate the weakness before it becomes public knowledge and possibly misused by hackers with malicious intentions. By privately notifying organisations, they can address the vulnerabilities before they are exploited by malicious hackers, thereby improving the security of their systems.
Responsible disclosure helps protect users, maintains trust between (DIVD) researchers and organisations, and contributes to the ongoing improvement of cybersecurity practices.
**Security.txt**\
Security.txt is a proposed standard for websites to provide a clear and consistent way for security researchers to report security vulnerabilities. It involves placing a simple text file named security.txt in the well-known location /.well-known/ directory of a website (e.g., https://example.com/.well-known/security.txt). This file contains contact information and other details that guide researchers on how to responsibly disclose security issues to the organization. Wanna make DIVD's work easier? Put our [security.txt](https://securitytxt.org/) in the code of your website and our IP 194.5.73.0-255 on your allow list.
Security.txt is a proposed standard for websites to provide a clear and consistent way for security researchers to report security vulnerabilities. It involves placing a simple text file named security.txt in the well-known location /.well-known/ directory of a website (e.g., https://example.com/.well-known/security.txt). This file contains contact information and other details that guide researchers on how to responsibly disclose security issues to the organization. Wanna make DIVD's work easier? Put our [security.txt](https://securitytxt.org/) in the code of your website and our IP 194.5.73.0-255 on your allow list.
**Types of vulnerabilities**\
There are different types of vulnerabilities. Since DIVD scans IP addresses over the public internet, we mainly focus on web-based vulnerabilities. A good example of a database filled with web-based vulnerabilities is The [OWASP Top 10](https://owasp.org/www-project-top-ten/).
**Vulnerability versus exploit**\
A vulnerability is an issue or weakness in a system or application, whereas an exploit is an active component used to carry out an attack. The purpose of an exploit is to ‘exploit’ a vulnerability. A vulnerability itself does not cause harm by itself but creates an opportunity for an attacker to exploit it.
opener: DIVD's work is of great importance, here is why
main:
title: More text here
contenttitle: "## DIVD’s efforts are invaluable to society for several reasons"
---
✨ First of all, DIVD scans for both known ánd zero-day vulnerabilities. When vulnerable URLs or systems are detected, we send the owners of the website or system a notification email.

Expand Down
48 changes: 19 additions & 29 deletions content/why-our-work-matters/_index.nl.md
Original file line number Diff line number Diff line change
@@ -1,33 +1,23 @@
---
title: Why our work matters
opener: Why our work matters
intro: DIVD is a non-profit organisation run by volunteers, and a network of
likeminded organisations. We’d love for you to sign up as a volunteer.
corevaluestitle: Core values
intro: DIVD is a non-profit organisation run by volunteers, and a network of likeminded organisations. We’d love for you to sign up as a volunteer.
leftblock:
content: .
learnmore: ""
rightblock:
content: .
contenttitle: .
belowwoordenboek: .
corevalues:
- title: Ethical Integrity
description: Volunteers must demonstrate a strong commitment to ethical conduct
in their work. They should prioritise the well-being and safety of
internet users and respect privacy and legal boundaries while conducting
vulnerability research.
- title: Societal Responsibility
description: Volunteers should be driven by a sense of societal responsibility,
understanding the importance of their role in making the digital world
safer. Their motivation should stem from the desire to serve the common
good, rather than pursuing personal benefits, political objectives, or
individual interests.
- title: Collaborative Mindset
description: "It is essential for volunteers to appreciate the importance of
collaboration and teamwork. They should be open to engaging with a variety
of stakeholders, such as vendors, researchers, and reliable partners.
Their role involves orchestrating vulnerability disclosure and efficiently
reducing risks. The accomplishment of DIVD’s mission heavily relies on
effective communication and cooperation. "
- title: Technical Proficiency
description: It is crucial for volunteers to have a robust knowledge of
cybersecurity principles and methods. If they are considering joining one
of our technical teams, they need to possess the necessary technical
expertise to effectively detect and scrutinize vulnerabilities in online
systems. Keeping up-to-date with the latest technologies and threats
through continuous learning is indispensable.
- description: Volunteers must demonstrate a strong commitment to ethical conduct in their work. They should prioritise the well-being and safety of internet users and respect privacy and legal boundaries while conducting vulnerability research.
title: Ethical Integrity
- description: Volunteers should be driven by a sense of societal responsibility, understanding the importance of their role in making the digital world safer. Their motivation should stem from the desire to serve the common good, rather than pursuing personal benefits, political objectives, or individual interests.
title: Societal Responsibility
- description: It is essential for volunteers to appreciate the importance of collaboration and teamwork. They should be open to engaging with a variety of stakeholders, such as vendors, researchers, and reliable partners. Their role involves orchestrating vulnerability disclosure and efficiently reducing risks. The accomplishment of DIVD’s mission heavily relies on effective communication and cooperation.
title: Collaborative Mindset
- description: It is crucial for volunteers to have a robust knowledge of cybersecurity principles and methods. If they are considering joining one of our technical teams, they need to possess the necessary technical expertise to effectively detect and scrutinize vulnerabilities in online systems. Keeping up-to-date with the latest technologies and threats through continuous learning is indispensable.
title: Technical Proficiency
corevaluestitle: Core values
opener: Why our work matters
---
..

0 comments on commit dbd77c6

Please sign in to comment.