Question

Say you were going to change an existing API, what considerations do you need to be concerned with of and how can you reduce the risk?

Answer 1

Solution : Having a security with cryptography while changing an existing API is very necessary because it is a major security aspects. First consideration is to have always http:// instead of https:// because it is very necessary for the session token/API key. Using http:// also helps in maintaining associated resource collection, action, and record. Another consideration is to take care of the HTTP Protect methods i.e., It is good consider HTTP methods ( DELETE ( for deleting any record ) , PUT ( (modify / replace / update) , GET (read) and POST (create) ) wisely. Another consideration is to protect resource collections because the risk of sensitivity is associated with these collections and Protect privileged actions.

It is good to have an effective API security strategy while changing an existing API so that it could protect the system from from identity attacks ( like malwares , Ransoms , and Spoofing attacks ). Apart from these risks and considerations , We can reduce the Risks by using session tracking because session tracking is very helpful for validating the authorized and unauthorized identities against unforeseen future attack vectors.