Skip to content

Conversation

@KadirArslan
Copy link
Contributor

You're A Rockstar

@jmanico I mistakenly closed my previous PR and deleted my branch. So I've created new one with changes you suggested.

#1931

🚩 If your PR is related to grammar/typo mistakes, please double-check the file for other mistakes in order to fix all the issues in the current cheat sheet.

Please make sure that for your contribution:

  • In case of a new Cheat Sheet, you have used the Cheat Sheet template.
  • All the markdown files do not raise any validation policy violation, see the policy.
  • All the markdown files follow these format rules.
  • All your assets are stored in the assets folder.
  • All the images used are in the PNG format.
  • Any references to websites have been formatted as [TEXT](URL)
  • You verified/tested the effectiveness of your contribution (e.g., the defensive code proposed is really an effective remediation? Please verify it works!).
  • The CI build of your PR pass, see the build status here.

If your PR is related to an issue, please finish your PR text with the following line:

This PR fixes issue #1931 .

AI Tool Usage Disclosure (required for all PRs)

Please select one of the following options:

  • I have NOT used any AI tool to generate the contents of this PR.
  • I have used AI tools to generate the contents of this PR. I have verified
    the contents and I affirm the results. The LLM used is [llm name and version]
    and the prompt used is [your prompt here]. [Feel free to add more details if needed]

Thank you again for your contribution 😃

Copy link
Member

@jmanico jmanico left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is pretty beefy for a cheatsheet. Can I get others to review? cc @szh @mackowski

I think this is good quality, but my main concern is the length. I wonder if we can make this more of a "cheat" and more concise.

@szh szh linked an issue Dec 30, 2025 that may be closed by this pull request
@KadirArslan
Copy link
Contributor Author

The reason it's so long is actually because of the code examples. I'm unsure too, but I thought code examples would be important for understanding.

@szh
Copy link
Collaborator

szh commented Dec 31, 2025

Agreed, it's not so long without the code samples. I think we have a way to make sections collapsible - maybe we can make the code samples collapsible so it's easier to read?

szh
szh previously approved these changes Dec 31, 2025
Copy link
Collaborator

@szh szh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm a fan. Great work @KadirArslan!

@KadirArslan
Copy link
Contributor Author

Hey, thank you for the valuable comment @szh
I've updated the cheatsheet, made code examples collapsible.

@KadirArslan KadirArslan requested review from jmanico and szh January 1, 2026 09:06
Copy link
Collaborator

@szh szh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, LGTM!

Copy link
Collaborator

@mackowski mackowski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perfect!

@mackowski
Copy link
Collaborator

Thanks @KadirArslan

@mackowski mackowski merged commit 46f8d04 into OWASP:master Jan 5, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

New CS proposal: Multi-Tenant Application Security Cheat Sheet

5 participants