-
-
Notifications
You must be signed in to change notification settings - Fork 394
Add Persian (fa) edition for API Security 2023 #134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @This-is-Neo,
The PR needs some changes before becoming ready for merge.
Please kindly review my comments.
Remember that you can render the site locally using docker. To add the Persian translation to the languages selector you should do the following change:
diff --git a/editions/2023/mkdocs.yml b/editions/2023/mkdocs.yml
index e4f73e3..505c4d2 100644
--- a/editions/2023/mkdocs.yml
+++ b/editions/2023/mkdocs.yml
@@ -9,3 +9,5 @@ extra:
lang: en
- name: Français
lang: fr
+ - name: Persian
+ lang: fa
Also note that we are no longer providing the ODT
/PDF
versions of the document due to the additional effort required to keep them up to date. In the future we may consider providing distributable formats as long as they can be compiled from the source.
Cheers,
Paulo A. Silva
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @PauloASilva ,
I wanted to let you know that the updates and revisions you requested in this part have been completed and committed.
Please feel free to review them, and let me know if any further adjustments are needed.
Best regards,
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @PauloASilva ,
Just a quick update—I’m actively working on the revisions you requested. I’ll make sure to commit the changes as soon as possible. If there’s anything else you’d like me to address, feel free to let me know!
Best Regards,
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @PauloASilva ,
I believe I’ve addressed all the revisions you mentioned, and my latest commit is ready for your review.
Looking forward to your feedback and any additional input you may have.
Thanks,
@@ -0,0 +1,89 @@ | |||
<div dir="rtl" align='right'> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @PauloASilva
I'm progressing with the revisions and just wanted to confirm a couple of details to ensure everything aligns with your expectations:
You mentioned that "MkDocs already takes care of it." Could you confirm which elements I can leave as-is, so I avoid unnecessary changes?
Regarding the "code blocks," I assume they’re properly handled, but is there anything specific you’d like adjusted, or can I proceed with the current setup?
Once I have your input, I’ll finalize and commit the changes as soon as possible. Feel free to let me know if there's anything else.
Best regards,
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @PauloASilva ,
I believe I’ve addressed all the revisions you mentioned, and my latest commit is ready for your review. In my last reply, I had a few questions, which I believe I've now resolved—if so, there's no need for further clarification.
Looking forward to your feedback and any additional input you may have.
Thanks,
Hi @PauloASilva , Also, is there anything else I should consider adding or refining in the Mkdocs.yml file, particularly related to content structure or editing configurations? For example, should I include something like this for additional markdown support:
Best regards, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @This-is-Neo,
Carefully review my comments: some requested changes apply to all translation sources.
Please compare you sources with the original ones in terms of structure e.g. headings, unnecessary ---
, use of markup instead of markdown when not required, ...
Take your time to carefully review the translation source making sure it follows the original EN
source as much as possible. Keep in mind that reviews like this one require a lot of time and effort from all of us.
Cheers,
Paulo A. Silva
editions/2023/fa/0x00-toc.md
Outdated
* [ ریسکهای امنیت API](0x10-api-security-risks.md) | ||
* [ ده ریسک امنیت API OWASP 2019](0x11-t10.md) | ||
* [API1:2023 مجوزدهی نادرست در سطح اشیا](0xa1-broken-object-level-authorization.md) | ||
* [API2:2023 احرازهویت نادرست کاربر](0xa2-broken-autentication.md) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
editions/2023/fa/0x00-toc.md
Outdated
* [API2:2023 احرازهویت نادرست کاربر](0xa2-broken-autentication.md) | ||
* [API3:2023 افشای مفرط داده](0xa3-broken-object-property-level-authorization.md) | ||
* [API4:2023 کمبود منابع و نبود محدودیت بر نرخ ارسال](0xa4-unrestricted-resource-consumption.md) | ||
* [API5:2023 مجوزدهی نادرست در سطح توابع](0xa5-broken-function-level-authorizaion.md) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
editions/2023/mkdocs.yml
Outdated
i18n: | ||
nav: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're not supposed to change this: it should remain alternate
otherwise the language selector is not rendered.
Please revert these changes.
Keep in mind that you can render the documentation locally following this instructions.
editions/2023/fa/index.md
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please remove this file since instructions are already provided here otherwise it may lead to issues like those introduced in the mkdocs.yml
file.
editions/2023/fa/0x00-header.md
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| دسترسی غیرمجاز میتواند منجر به افشای اطلاعات، از دست رفتن داده یا دستکاری آن شود. همچنین دسترسی غیرمجاز به اشیا میتواند سبب کنترل کامل حساب کاربری توسط مهاجم گردد. | این حمله رایجترین آسیبپذیری APIها بوده و بیشترین پیامدها را نیز در پی دارد. مکانیزمهای مجوزدهی و کنترل دسترسی در اپلیکیشنهای مدرن، پیچیده و گسترده هستند. حتی اگر اپلیکیشن زیرساخت مناسب را برای کنترلهای مجوزدهی پیادهسازی نماید، ممکن است توسعه دهندگان پیش از دسترسی به اشیا حساس، استفاده از این کنترلها را فراموش نمایند. تشخیص نقایص مربوط به کنترل دسترسی از طریق تستهای ایستا یا پویا به صورت خودکار غالبا امکان پذیر نیست. | مهاجمین میتوانند از نقاط و توابع آسیبپذیر (از منظر مجوزدهی نادرست در سطح اشیا) با دستکاری شناسه شیء ارسالی درون درخواست سوءاستفاده و بهره برداری نمایند. این امر میتواند منجر به دسترسی غیرمجاز به داده حساس شود. دسترسی غیرمجاز به داده حساس، مسالهای رایج در اپلیکیشنهای مبتنی بر API است چرا که مولفه سرور غالبا به طور کامل وضعیت کلاینت را رهگیری نمیکند و در عوض برای تصمیم گیری درباره دسترسی کلاینت به اشیاء از پارامترهایی نظیر شناسه شی که از سوی خود کلاینت ارسال میشوند، تکیه دارند. | | ||
|
||
### آیا API از نظر نقض مجوزدهی در سطح اشیاء آسیبپذیر است؟ | ||
--- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No need: check the original (en
) markdown source
در مسئلهی Broken Object Level Authorization (BOLA)، امنیت کاربران در دسترسی به اطلاعات و منابع در سیستم به خطر میافتد. این مشکل زمانی رخ میدهد که سیستم یک درخواست API حاوی یک شناسه (مثلاً شناسه یک مورد یا اشیاء خاص) را دریافت میکند و بدون بررسی دقیق این شناسه و اعتبارسنجی آن، به منابع مرتبط با آن شناسه دسترسی میدهد. مهاجمان با تغییر شناسه در درخواستهای خود میتوانند به اطلاعاتی دسترسی پیدا کنند که به طور عادی نباید به آنها دسترسی داشته باشند. | ||
|
||
### مثالهایی از سناریوهای حمله | ||
--- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No need: check the original (en
) markdown source
یک سرویس ذخیرهسازی اسناد آنلاین به کاربران این امکان را میدهد که اسناد خود را مشاهده، ویرایش، ذخیره و حذف کنند. هنگامی که کاربری یکی از اسناد خود را حذف میکند، یک عملیات درخواستی به نام GraphQL Mutation با استفاده از شناسه (ID) مربوط به سند حذفشده به API ارسال میشود. این درخواست GraphQL به API اطلاع میدهد که یک سند باید حذف شود و API مسئول انجام این عملیات حذف است. | ||
|
||
### چگونه از آسیبپذیری مجوزدهی نادرست در سطح اشیاء پیشگیری کنیم؟ | ||
--- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No need: check the original (en
) markdown source
- طراحی آزمونهایی برای ارزیابی صحت عملکرد مکانیزمهای مجوزدهی. | ||
|
||
### مراجع | ||
--- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No need: check the original (en
) markdown source
- [Authorization Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/Authorization_Cheat_Sheet.html) | ||
- [Authorization Testing Automation Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/Authorization_Testing_Automation_Cheat_Sheet.html) | ||
|
||
#### خارجی | ||
- [CWE-285: Improper Authorization](https://cwe.mitre.org/data/definitions/285.html) | ||
- [CWE-639: Authorization Bypass Through User-Controlled Key](https://cwe.mitre.org/data/definitions/639.html) | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Consider moving the URLs to the bottom of the source file as in the original EN source.
If you decide to adhere then review and change the whole translation source accordingly.
Hi @PauloASilva , I have completed the revisions as requested. Below is a summary of the updates I made:
These changes should now make the document fully aligned with the original English source and address all of your previous comments. Please feel free to review and let me know if any further adjustments are needed. Best regards, |
Unfortunately, they don't: build process is broken I guess due to I may take a while to put this together so that it can be merged. Cheers, |
Add Persian (fa) edition for API Security 2023