Scribd Logo
Upload

Welcome to Scribd!

  • 8 views

    Chapter 6

    Uploaded by

    Mayur Kamatkar
    1. Monitor and control system output to prevent sending entire datasets like customer tables to APIs in response to unauthenticated inputs. This could provide attackers access to large amounts of private data. 2. Input that is not used for processing should not remain in the input stream, as this could indicate the endpoint has been reached and no further data can be provided, exposing the system. 3. When choosing a programming language, security considerations include risks from encrypted access keys being vulnerable to attacks like phishing, and controls needed to prevent issues like eavesdropping, viruses, tampering, phishing and impersonation.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd

    Chapter 6

    Uploaded by

    Mayur Kamatkar
    8 views3 pages
    1. Monitor and control system output to prevent sending entire datasets like customer tables to APIs in response to unauthenticated inputs. This could provide attackers access to large amounts of private data. 2. Input that is not used for processing should not remain in the input stream, as this could indicate the endpoint has been reached and no further data can be provided, exposing the system. 3. When choosing a programming language, security considerations include risks from encrypted access keys being vulnerable to attacks like phishing, and controls needed to prevent issues like eavesdropping, viruses, tampering, phishing and impersonation.

    Original Title

    chapter6

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    1. Monitor and control system output to prevent sending entire datasets like customer tables to APIs in response to unauthenticated inputs. This could provide attackers access to large amounts of private data. 2. Input that is not used for processing should not remain in the input stream, as this could indicate the endpoint has been reached and no further data can be provided, exposing the system. 3. When choosing a programming language, security considerations include risks from encrypted access keys being vulnerable to attacks like phishing, and controls needed to prevent issues like eavesdropping, viruses, tampering, phishing and impersonation.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    8 views3 pages

    Chapter 6

    Uploaded by

    Mayur Kamatkar
    1. Monitor and control system output to prevent sending entire datasets like customer tables to APIs in response to unauthenticated inputs. This could provide attackers access to large amounts of private data. 2. Input that is not used for processing should not remain in the input stream, as this could indicate the endpoint has been reached and no further data can be provided, exposing the system. 3. When choosing a programming language, security considerations include risks from encrypted access keys being vulnerable to attacks like phishing, and controls needed to prevent issues like eavesdropping, viruses, tampering, phishing and impersonation.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    You are on page 1of 3

    1.

    Monitor and Control system output

    A user may inadvertently or purposefully submit an input that is not authenticated or has not
    been proven for, prompting business rule logic such as "SELECT * FROM TABLE
    CUSTOMER." This wasn't a logical mistake, and SQL would execute as usual, sending the
    entire huge dataset of, instance, the customer table to the API.

    When no limits are set on the created output, the APIs will effortlessly transmit the data to the
    top of the web interface, in addition to the attacker would not own a gold mine was at it's
    disposal.

    2. Why should input that is not used in processing never be allowed to stay on
    the input stream?

    Since the concealed data source of input stream consumption could indicate that the endpoint
    of a process such as the stream has been reached and no further data can be given. If you're
    looking for a unique way to express yourself, here is the place to be.

    3. Programming language to use in software development?

    The most important consideration in policy creation and execution. Because some computer
    languages rely on encrypted access keys, they are vulnerable to phishing and other dangerous
    assaults.

    The concerns include

    Eavesdropping,

    Virus

    Tampering

    Phishing

    Impersonation.

    ii) The commencement of anything being necessary to get access to the organisation.
    4. Data canaries to prevent buffer

    The relevance of a data canary is the fact that it alerts the system whenever a buffer overflow
    occurs, enabling it to take appropriate action. The limitations include the fact that an attacker
    can get around it if someone know you use data canaries regardless of what their value is.

    Whenever an intruder gains possession of a program counter, their changed value for


    something like the returned pointer is entered into the current instruction, the contents of the
    stack canaries is checked even before calling function arrived.

    Canaries-created programs will have extra instructions just before the call conclusion but also
    debugger action. Buffer overflow vulnerability occurs where buffer operations are not
    validated for boundaries. Methods like gets() and strcpy do not check for boundaries (). As a
    result, the functions fgets() and strlcpy have been deprecated and replaced (). These
    approaches, when used appropriately, offer enough bounds checks and eliminate the buffer
    overflow problem. Searching will turn up a list of vulnerable C functions which are safer
    equivalents.

    5. Setting boundaries on variable values

    In a programming language, each variable relates to a kind of data and additionally possesses
    a value and scope. The variables' boundaries are the ranges' endpoints. When assigning a
    value to a variable, it's indeed critical that the value fall within the provided range. In
    contrast, the variables may behave strangely, crashing the programme, returning a random
    value, or persisting to utilize a given value, all of which can result in a breakdown inside this
    execution logic, rendering the software "buggy" and potentially dangerous.

    References

    Aradhya, D. (2017a, February 9). The Importantance of Setting Boundaries on Variable


    Values – Divya Aradhya. Variable Values.
    http://www.divyaaradhya.com/2017/02/09/the-importantance-of-setting-boundaries-
    on-variable-values/#:%7E:text=Every%20variable%20in%20a%20programming,falls
    %20within%20the%20defined%20range.
    Lemmens, M. (2022, January 7). Password Hash Cracking in Amazon Web Services:
    Burning Your Way to Success. Buffer. https://www.sans.org/blog/stack-canaries-
    gingerly-sidestepping-the-cage/

    You might also like