Scribd Logo
Upload

Welcome to Scribd!

  • 19 views

    CCN Case Study Gaurang

    Uploaded by

    Gaurang Gawas
    Gaurang Gawas continues the discussion on setting up HTTPS and addresses some questions. Using HTTPS on public WiFi protects data by encrypting traffic between devices and websites, and verifies website identities through certificates. Not all web traffic needs HTTPS due to performance impacts of encryption for sites without sensitive data. However, many users accept some speed reduction for more security on large sites. While HTTPS promotes security, its use of single IP addresses makes it incompatible with common virtual hosting. The discussion concludes that HTTPS encryption should be implemented on all websites to fully protect user and organization data from start to finish.

    Copyright:

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

    CCN Case Study Gaurang

    Uploaded by

    Gaurang Gawas
    19 views2 pages
    Gaurang Gawas continues the discussion on setting up HTTPS and addresses some questions. Using HTTPS on public WiFi protects data by encrypting traffic between devices and websites, and verifies website identities through certificates. Not all web traffic needs HTTPS due to performance impacts of encryption for sites without sensitive data. However, many users accept some speed reduction for more security on large sites. While HTTPS promotes security, its use of single IP addresses makes it incompatible with common virtual hosting. The discussion concludes that HTTPS encryption should be implemented on all websites to fully protect user and organization data from start to finish.

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Gaurang Gawas continues the discussion on setting up HTTPS and addresses some questions. Using HTTPS on public WiFi protects data by encrypting traffic between devices and websites, and verifies website identities through certificates. Not all web traffic needs HTTPS due to performance impacts of encryption for sites without sensitive data. However, many users accept some speed reduction for more security on large sites. While HTTPS promotes security, its use of single IP addresses makes it incompatible with common virtual hosting. The discussion concludes that HTTPS encryption should be implemented on all websites to fully protect user and organization data from start to finish.

    Copyright:

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

    CCN Case Study Gaurang

    Uploaded by

    Gaurang Gawas
    Gaurang Gawas continues the discussion on setting up HTTPS and addresses some questions. Using HTTPS on public WiFi protects data by encrypting traffic between devices and websites, and verifies website identities through certificates. Not all web traffic needs HTTPS due to performance impacts of encryption for sites without sensitive data. However, many users accept some speed reduction for more security on large sites. While HTTPS promotes security, its use of single IP addresses makes it incompatible with common virtual hosting. The discussion concludes that HTTPS encryption should be implemented on all websites to fully protect user and organization data from start to finish.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 2

    I am Gaurang Gawas and I will be continuing further.

    As Suyash has already discussed some


    steps to set up HTTPS for transactions, I will be continuing with some questions.
    1. The first one is How would it protect us from using a public Wi-Fi connection at
    a local coffee shop?
    Using HTTPS without a VPN means that some of our data will still be vulnerable if
    we are on public Wi-Fi. HTTPS helps encrypt traffic between our device and a
    website and makes it difficult for intruders to observe the shared information. It also
    provides signatures, or HTTPS certificates, that allow us to verify that the site we are
    on is run by whom it claims it to be. HTTPS has become a standard security feature
    for nearly all websites.

    2. Should all web traffic be required to use HTTPS? Why, or why not?
    HTTPS promotes security, however, not all should be in HTTPS format, and with
    HTTPS websites will lose the ability to cache.
     Also, a purely security-focused, HTTPS-only Web would, with today's technology,
    be slower.
     For sites that don't have any reason to encrypt anything the overhead and loss of
    caching that comes with HTTPS just don't make sense.
     However, for big sites like Facebook, Google Apps, or Twitter, many users might be
    willing to take a slight performance hit in exchange for a more secure connection.
    More and more websites are adding support for HTTPS showing that users do value
    security over speed, so long as the speed difference is minimal.
     The main reason most of us are not using HTTPS to serve our websites is simply
    that it doesn't work with virtual hosts. Virtual hosts, which are what the most common
    cheap Web hosting providers offer, allow the Web host to serve multiple websites
    from the same physical server—hundreds of websites all with the same IP address.
    That works just fine with regular HTTP connections, but it doesn't work at all with
    HTTPS.

    These are some of the Learning outcomes :


     We learned about the HTTP and HTTPS Protocols and how they play a crucial role in
    protecting data integrity and security.
     We learned to set up a server for HTTPS transactions.
     We also learned to protect ourselves while using public Wi-Fi using HTTPS.

    And now this brings us to the end and we conclude that


     Use of HTTP encryption is no longer sufficient to protect your website or
    safeguard against data compromise.
     And using HTTPS is much safer and Implementing it everywhere on your
    website secures the user and your organization's data on every page from start to
    finish.
    So thank you guys for watching and listening.

    You might also like