Skip to content

Commit d31a555

Browse files
committed
feat(intro): add "Introduction" section
* add "Introduction" section * update dist formats
1 parent ec08ff7 commit d31a555

File tree

3 files changed

+27
-0
lines changed

3 files changed

+27
-0
lines changed
-610 Bytes
Binary file not shown.
2.31 KB
Binary file not shown.

2019/en/src/0x03-introduction.md

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,2 +1,29 @@
11
Introduction
22
============
3+
4+
## Welcome to the OWASP API Security Top 10 - 2019!
5+
6+
Welcome to the OWASP API Security Top 10 first edition. If you're familiar with
7+
the OWASP Top 10 series, you'll notice the similarities: they are intended for
8+
readability and adoption. Otherwise, consider visiting the [OWASP API Security
9+
Project wiki page][1], before digging deeper into the then most critical API
10+
security risks.
11+
12+
APIs play a very important role in modern applications architecture.
13+
Because creating security awareness and innovation have different paces, it
14+
urges to focus on common API security weaknesses.
15+
16+
The primary aim of the OWASP API Security Top 10 is to educate those involved
17+
in API development and maintenance being them developers, designers, architects,
18+
managers, or organizations.
19+
20+
In the [Methodology and Data][2] section you can read more about how this first
21+
edition was created. In future versions, we want to involve the security
22+
industry, with a public call for data. For now, we encourage everyone to
23+
contribute with questions, comments and ideas at our [GitHub repository][3] or
24+
[Mailing list][4].
25+
26+
[1]: https://www.owasp.org/index.php/OWASP_API_Security_Project
27+
[2]: ./0xd0-about-data.md
28+
[3]: https://github.com/OWASP/API-Security
29+
[4]: https://groups.google.com/a/owasp.org/forum/#!forum/api-security-project

0 commit comments

Comments
 (0)