Powered by OpenAIRE graph
Found an issue? Give us feedback
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/ https://www.daaam.in...arrow_drop_down
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/
https://doi.org/10.2507/35th.d...
Part of book or chapter of book . 2024 . Peer-reviewed
Data sources: Crossref
versions View all 2 versions
addClaim

Serverless Architecture and Security

Authors: Marko Harambasa; Karlo Josic; Matej Basic;

Serverless Architecture and Security

Abstract

This paper explores the serverless architecture, detailing its key components, benefits, and security concerns. It contrasts two main types: Function as a Service (FaaS) and Backend as a Service (BaaS), highlighting how they allow for building applications without the need for managing underlying servers. The paper continues into serverless architecture's operational and financial benefits, such as scalability, reduced maintenance, and cost efficiency. Security challenges unique to serverless computing are examined, stressing the importance of adopting robust security measures like comprehensive monitoring and logging to mitigate risks. The paper discusses the inherent security benefits of serverless computing, including minimized attack surfaces and automated updates and outlines best practices for ensuring secure serverless environments, such as secure coding, stringent access controls, data encryption, and continuous monitoring.

Keywords

Function as a Service, serverless, AWS Lambda, Google Cloud Functions, HTTP, Backend as a Service, Azure Functions, HTTPS

  • BIP!
    Impact byBIP!
    selected citations
    These citations are derived from selected sources.
    This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).
    0
    popularity
    This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network.
    Average
    influence
    This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).
    Average
    impulse
    This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network.
    Average
Powered by OpenAIRE graph
Found an issue? Give us feedback
selected citations
These citations are derived from selected sources.
This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).
BIP!Citations provided by BIP!
popularity
This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network.
BIP!Popularity provided by BIP!
influence
This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).
BIP!Influence provided by BIP!
impulse
This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network.
BIP!Impulse provided by BIP!
0
Average
Average
Average