dogear

enter for all results · esc to close

Back-End Development

4,701 items in 32 lists

  1. Getting started with security keys web.archive.org

    A practical guide to stay safe online and prevent phishing with FIDO2, WebAuthn and security keys.

    site link ↗
  2. 163 AWS services explained in one line each web.archive.org

    Help makes sense of their huge service catalog. In the same spirit: AWS In Plain English.

    site link ↗
  3. GCP's IAM syntax is better than AWS's web.archive.org

    The minutiae of permission design in GCP improves the developer's experience.

  4. What is BeyondCorp? What is Identity-Aware Proxy? web.archive.org

    More companies add extra layers of VPNs, firewalls, restrictions and constraints, resulting in a terrible experience and a slight security gain. There's a better way.

    site link ↗
  5. Mitigating Cloud Vulnerabilities web.archive.org

    “This document divides cloud vulnerabilities into four classes (misconfiguration, poor access control, shared tenancy vulnerabilities, and supply chain vulnerabilities)”.

    site link ↗
  6. Google's Macaroons in Five Minutes or Less web.archive.org

    If I'm given a Macaroon that authorizes me to perform some action(s) under certain restrictions, I can non-interactively build a second Macaroon with stricter restrictions that I can then give to you.

    site link ↗
  7. In Search For a Perfect Access Control System web.archive.org

    The historical origins of authorization schemes. Hints at the future of sharing, trust and delegation between different teams and organizations.

  8. After Car2Go eased its background checks, 75 of its vehicles were stolen in one day. web.archive.org

    Why background check are sometimes necessary.

    site link ↗
  9. SAML vs. OAuth web.archive.org

    “OAuth is a protocol for authorization: it ensures Bob goes to the right parking lot. In contrast, SAML is a protocol for authentication, or allowing Bob to get past the guardhouse.”

    site link ↗
  10. JWT, JWS and JWE for Not So Dummies! web.archive.org

    A signed JWT is known as a JWS (JSON Web Signature). In fact a JWT does not exist itself — either it has to be a JWS or a JWE (JSON Web Encryption). Its like an abstract class — the JWS and JWE are the concrete implementations.

    site link ↗
  11. The False Allure of Hashing for Anonymization web.archive.org

    Hashing is not sufficient for anonymization no. But still it is good enough for pseudonymization (which is allowed by the GDPR).

    site link ↗
  12. Hardcoded secrets, unverified tokens, and other common JWT mistakes web.archive.org

    A good recap of all JWT pitfalls.

    site link ↗
  13. How Radix trees made blocking IPs 5000 times faster web.archive.org

    Radix trees might come handy to speed-up IP blocklists.

    site link ↗
  14. IAM is hard. It's really hard. web.archive.org

    “Overly permissive AWS IAM policies that allowed s3:GetObject to * (all) resources”, led to $80 million fine for Capital One. The only reason why you can't overlook IAM as a business owner.

  15. A Child's Garden of Inter-Service Authentication Schemes web.archive.org

    In the same spirit as above, but this time at the service level.

    site link ↗
  16. Conversion Optimization web.archive.org

    A collection of tactics to increase the chance of users finishing the account creation funnel.

    site link ↗
  17. Zanzibar: Google's Consistent, Global Authorization System web.archive.org

    Scales to trillions of access control lists and millions of authorization requests per second to support services used by billions of people. It has maintained 95th-percentile latency of less than 10 milliseconds and availability of greater than 99.999% over 3 years of…

    site link ↗
  18. You (probably) don't need ReCAPTCHA web.archive.org

    Starts with a rant on how the service is a privacy nightmare and is tedious UI-wise, then list alternatives.

    site link ↗
  19. An argument for passwordless web.archive.org

    Passwords are not the be-all and end-all of user authentication. This article tries to tell you why.

    site link ↗
  20. Lifetimes of cryptographic hash functions valerieaurora.org

    “If you are using compare-by-hash to generate addresses for data that can be supplied by malicious users, you should have a plan to migrate to a new hash every few years”.

    site link ↗
  21. A Comparison of Personal Name Matching: Techniques and Practical Issues users.cecs.anu.edu.au

    Customer name matching has lots of application, from account deduplication to fraud monitoring.

    site link ↗
  22. The 2020 State of SaaS Product Onboarding userpilot.com

    Covers all the important facets of user onboarding.

  23. User Onboarding Teardowns useronboard.com

    A huge list of deconstructed first-time user signups.

    site link ↗
  24. BeyondCorp: A New Approach to Enterprise Security usenix.org

    Quick overview of Google's Zero-trust Network initiative.

    site link ↗
  25. Attacking Google Authenticator unix-ninja.com

    Probably on the verge of paranoia, but might be a reason to rate limit 2FA validation attempts.

    site link ↗
  26. The Difference Between SAML 2.0 and OAuth 2.0 ubisecure.com

    “Even though SAML was actually designed to be widely applicable, its contemporary usage is typically shifted towards enterprise SSO scenarios. On the other hand, OAuth was designed for use with applications on the Internet, especially for delegated authorisation.”

    site link ↗
  27. Why are the username and password on two different pages? twilio.com

    To support both SSO and password-based login. Now if breaking the login funnel in 2 steps is too infuriating to users, solve this as Dropbox does: an AJAX request when you enter your username.

    site link ↗
  28. Beyond Passwords: 2FA, U2F and Google Advanced Protection troyhunt.com

    An excellent walk-trough over all these technologies.

    site link ↗
  29. Banks, Arbitrary Password Restrictions and Why They Don't Matter troyhunt.com

    “Arbitrary low limits on length and character composition are bad. They look bad, they lead to negative speculation about security posture and they break tools like password managers.”

    site link ↗
  30. Standards related to Threat Intelligence threat-intelligence.eu

    Open standards, tools and methodologies to support threat intelligence analysis.

    site link ↗
  31. The Cleaners thoughtmaybe.com

    A documentary on these teams of underpaid people removing posts and deleting accounts.

  32. Facebook Dangerous Individuals and Organizations List theintercept.com

    Some groups and content are illegal in some juridictions. This is an example of a blocklist.

    site link ↗
  33. Password expiration is dead techcrunch.com

    Recent scientific research calls into question the value of many long-standing password-security practices such as password expiration policies, and points instead to better alternatives such as enforcing banned-password lists and MFA.

  34. SMS 2FA auth is deprecated by NIST techcrunch.com

    NIST has said that 2FA via SMS is bad and awful since 2016.

    site link ↗
  35. Your Pa$$word doesn't matter techcommunity.microsoft.com

    Same conclusion as above from Microsoft: “Based on our studies, your account is more than 99.9% less likely to be compromised if you use MFA.”

    site link ↗
  36. GDPR – A Practical guide for Developers techblog.bozho.net

    A one-page summary of the above.

  37. RBAC like it was meant to be tailscale.com

    How we got from DAC (unix permissions, secret URL), to MAC (DRM, MFA, 2FA, SELinux), to RBAC. Details how the latter allows for better modeling of policies, ACLs, users and groups.

    site link ↗
  38. 2FA is missing a key feature syslog.ravelin.com

    “When my 2FA code is entered incorrectly I'd like to know about it”.

    site link ↗
  39. Clearing up some misconceptions about Passkeys stavros.io

    Or why passkeys are not worse than passwords.

    site link ↗
  40. Secrets, Lies, and Account Recovery: Lessons from the Use of Personal Knowledge Questions at Google static.googleusercontent.com

    “Our analysis confirms that secret questions generally offer a security level that is far lower than user-chosen passwords. (…) Surprisingly, we found that a significant cause of this insecurity is that users often don't answer truthfully. (…) On the usability side, we show…

  41. Everybody be cool, this is a robbery! sstic.org

    A case study of vulnerability and exploitability of a HSM (in French, sorry).

    site link ↗
  42. The SSO Wall of Shame sso.tax

    A documented rant on the excessive pricing practiced by SaaS providers to activate SSO on their product. The author's point is, as a core security feature, SSO should be reasonably priced and not part of an exclusive tier.

  43. The challenges of file formats speakerdeck.com

    At one point you will let users upload files in your system. Here is a corpus of suspicious media files that can be leveraged by scammers =to bypass security or fool users.

    site link ↗
  44. Everything you should know about certificates and PKI but are too afraid to ask smallstep.com

    PKI lets you define a system cryptographically. It's universal and vendor neutral.

    site link ↗
  45. How to Implement a Secure Central Authentication Service in Six Steps shopify.engineering

    Got multiple legacy systems to merge with their own login methods and accounts? Here is how to merge all that mess by the way of OIDC.

    site link ↗
  46. The Difficulties of SAML Single Logout shibboleth.atlassian.net

    On the technical and UX issues of single logout implementations.

  47. How effective is basic account hygiene at preventing hijacking security.googleblog.com

    Google security team's data shows 2FA blocks 100% of automated bot hacks.

    site link ↗
  48. next page of items loading…