Skip to content
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

There is one error I cannot find. Otherwise it is fine.wise it seems fine. #1402

Closed
wants to merge 2 commits into from

Conversation

thornshadow99
Copy link
Contributor

Thank you for submitting a Pull Request (PR) to the Cheat Sheet Series.

🚩 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 covers issue #.

Thank you again for your contribution 😃

Comment on lines +13 to 14
Generally, mobile and online applications will require users a second factor to check whether they are authorized to perform a sensitive operation (such as wire transfer authorization). In this document, we say that this action is called *transaction authorization*.

Copy link
Member

Choose a reason for hiding this comment

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

This sentence is missing something. "Will require users to use.." perhaps?


For the purpose of this document we will call that process: *transaction authorization*.
Transaction authorization is typically used in financial systems, but the need for secure transactions has driven its adoption across the internet. For example, an email that allows users to unlock a user account by providing them with a secret code or a link that has a token contains a transaction authorization. A transaction authorization can be implemented with methods such as:
Copy link
Member

Choose a reason for hiding this comment

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

The "for example" sentence looks run-on. Can you review?

Comment on lines +19 to +21
- A OTP sent by SMS or provided by phone
- A digital signature provided by a smart card or a smartphone,
- A challenge-response token, including unconnected card readers or solutions which scan transaction data from the user's computer screen.
Copy link
Member

Choose a reason for hiding this comment

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

Some of these end with a comma, some do not

Some of these can be implemented on a physical device or in a mobile application.

Transaction authorization is implemented in order to protect for unauthorized wire transfers as a result of attacks using malware, phishing, password or session hijacking, CSRF, XSS, etc.. Unfortunately, as with any piece of code, this protection can be improperly implemented and as a result it might be possible to bypass this safeguard.
Most often, transaction authorizations are used to prevent for unauthorized wire transfers, but unfortunately, this protection can be improperly implemented and at might be possible to bypass this safeguard.
Copy link
Member

Choose a reason for hiding this comment

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

"For unauthorized wire" looks off.

For example when an SMS message is used to send significant transaction data, it is possible to send the target account, amount and type of transfer. However, for an unconnected [CAP reader](https://en.wikipedia.org/wiki/Chip_Authentication_Program) it is perceived to be inconvenient for a user to enter these data. In such cases, entering only the most significant transaction data (e.g. partial target account number and amount) can be considered sufficient.

In general, significant transaction data should always be presented as an inherent part of the transaction authorization process. Whereas the user experience should be designed to encourage users to verify the transaction data.
For example, if an SMS message is used to confirm significant transaction data, the developer could respond by returning the target account, amount and type of transfer to the user. However, for an unconnected [CAP reader](https://en.wikipedia.org/wiki/Chip_Authentication_Program) it is inconvenient for a user to enter these data. In such cases, the developer should probably returm the minimium amount of significant transaction data (e.g. partial target account number and amount) for confirmation.
Copy link
Member

Choose a reason for hiding this comment

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

Returm...

@jmanico
Copy link
Member

jmanico commented May 11, 2024

I see a lot of small errors, can you give you edits a review one more time?

@thornshadow99
Copy link
Contributor Author

thornshadow99 commented May 11, 2024 via email

@thornshadow99
Copy link
Contributor Author

thornshadow99 commented May 11, 2024 via email

@thornshadow99 thornshadow99 marked this pull request as draft May 12, 2024 00:21
@@ -2,111 +2,107 @@

## Purpose and audience

The Purpose of this cheat sheet is to provide guidelines on how to securely implement transaction authorization to protect it from being bypassed. These guidelines can be used by:
This cheat sheet discusses how developers can secure transaction authorizations and prevent them from being bypassed These guidelines are for:
Copy link
Collaborator

Choose a reason for hiding this comment

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

Missing period:

Suggested change
This cheat sheet discusses how developers can secure transaction authorizations and prevent them from being bypassed These guidelines are for:
This cheat sheet discusses how developers can secure transaction authorizations and prevent them from being bypassed. These guidelines are for:

jmanico
jmanico previously approved these changes May 13, 2024
@jmanico
Copy link
Member

jmanico commented May 13, 2024

Can I assume we can delete this branch I assume the other change we committed is the live one and this is legacy?

@jmanico jmanico dismissed their stale review May 13, 2024 18:18

Mistake

@thornshadow99
Copy link
Contributor Author

thornshadow99 commented May 13, 2024 via email

@jmanico
Copy link
Member

jmanico commented May 13, 2024

So it is ok to delete it? :) Just double checking before I do.

@thornshadow99
Copy link
Contributor Author

thornshadow99 commented May 13, 2024 via email

@jmanico jmanico closed this May 13, 2024
@kwwall
Copy link
Collaborator

kwwall commented May 19, 2024 via email

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.

None yet

4 participants