I’m Not A Robot!

I’m Not A Robot!

  • May 18, 2019
Table of Contents

I’m Not A Robot!

There is no one way to secure your API that fits all situations. But, you can learn the schemes, study how the biggest social networks are dealing with it and find out the industry standard; then apply it to your project in the way you see fit. At the end of this article, you’ll have a clear understanding of the different schemes.

I won’t go in depth on these here but I’ll do a deep dive on OAuth, the most widely used authorization framework, another time.

Source: towardsdatascience.com

Tags :
Share :
comments powered by Disqus

Related Posts

New AWS services launch with HIPAA, PCI, ISO, and SOC

New AWS services launch with HIPAA, PCI, ISO, and SOC

Read More
DNS over TLS: Encrypting DNS end-to-end

DNS over TLS: Encrypting DNS end-to-end

As a first step toward encrypting the last portion of internet traffic that has historically been cleartext, we have partnered with Cloudflare DNS on a pilot project. This pilot takes advantage of the benefits of Transport Layer Security (TLS) — a widely adopted and proven mechanism for providing authentication and confidentiality between two parties over an insecure channel — in conjunction with DNS. This solution, DNS over TLS (DoT), would encrypt and authenticate the remaining portion of web traffic.

Read More
Running Kubernetes in the Federal Government

Running Kubernetes in the Federal Government

Tackling security compliance is a long and challenging process for agencies, systems integrators, and vendors trying to launch new information systems in the federal government. Each new information system must go through the Risk Management Framework (RMF) created by the National Institute of Standards and Technology (NIST) in order to obtain authority to operate (ATO). This process is often long and tedious and can last for over a year.

Read More