Term 781
Security baseline
A security baseline is a documented minimum set of security configurations and settings that must be applied to a system, device, or network to ensure a known secure starting point.
Acronym study
Terms 781–810 of 1001 Cloud Digital Leader acronyms and key terms. Each entry includes a plain-English definition and a link to the full 800-word glossary page with exam context and practice questions.
Term 781
A security baseline is a documented minimum set of security configurations and settings that must be applied to a system, device, or network to ensure a known secure starting point.
Term 782
Security Command Center is a centralized cloud security management platform that helps organizations detect, investigate, and respond to threats across their cloud infrastructure.
Term 783
A security control is a safeguard or countermeasure designed to protect the confidentiality, integrity, and availability of information systems and data.
Term 784
Security governance is the framework of rules, policies, and processes that an organization uses to align its cybersecurity activities with its business goals and legal obligations.
Term 785
A security group is a virtual firewall that controls inbound and outbound traffic to AWS resources, such as EC2 instances, based on defined rules.
Term 786
Security Hub is a cloud security posture management service that aggregates and prioritizes security alerts and compliance checks from multiple AWS services into a single place.
Term 787
A system that collects, analyzes, and reports on security data from across an IT environment to detect and respond to threats.
Term 788
The security kernel is the core, trusted part of an operating system that enforces access control and security policies for all system operations.
Term 789
Security misconfiguration occurs when security settings are defined, implemented, or maintained incorrectly, leaving systems, applications, or networks vulnerable to unauthorized access or data breaches.
Term 790
A security model is a formal framework that defines how subjects (users, processes) can access objects (files, resources) based on rules, ensuring confidentiality, integrity, and availability.
Term 791
A Security Operations Center (SOC) is a centralized team and facility that monitors, detects, analyzes, and responds to cybersecurity incidents across an organization's IT environment 24/7.
Term 792
The Security pillar is a set of best practices for designing and operating cloud systems that protect data, systems, and assets through confidentiality, integrity, and availability controls.
Term 793
A security policy is a formal set of rules and guidelines that an organization establishes to protect its information assets and technology resources.
Term 794
An organization's overall cybersecurity strength, including policies, controls, and readiness to defend against and respond to threats.
Term 795
A security recommendation is a prescribed action, configuration, or update that aims to reduce risk and protect systems, data, and users from known threats or vulnerabilities.
Term 796
A security strategy is a high-level plan that outlines how an organization protects its information assets, aligns security with business goals, and manages risk over time.
Term 797
A security update is a software patch released to fix a vulnerability that could be exploited by attackers to compromise a system.
Term 798
SELinux (Security-Enhanced Linux) is a mandatory access control (MAC) security mechanism built into the Linux kernel that enforces policies to restrict how processes and users interact with files, devices, and system resources.
Term 799
Semi-structured data is information that has some organizational tags or markers but does not fit into a strict table format like a spreadsheet row and column.
Term 800
Sender Policy Framework (SPF) is an email authentication method that prevents spammers from sending emails that appear to come from your domain by listing which servers are allowed to send email for that domain.
Term 801
A sensitivity label is a metadata tag applied to digital content that classifies the content's level of confidentiality and governs how it can be shared, protected, and accessed.
Term 802
Separation of duties is a security principle that splits critical tasks and privileges among multiple people to prevent fraud, errors, and abuse of power.
Term 803
Serverless is a cloud computing model where the cloud provider manages the servers, and you only pay for the actual compute time your code uses, without having to worry about provisioning or maintaining infrastructure.
Term 804
Serverless architecture is a cloud computing model where the cloud provider automatically manages the infrastructure, allowing developers to build and run applications without thinking about servers.
Term 805
Serverless computing is a cloud execution model where the cloud provider dynamically manages the allocation and provisioning of servers, allowing developers to write and deploy code without thinking about the underlying infrastructure.
Term 806
A serverless function is a single-purpose piece of code that runs in the cloud only when triggered, without you managing any servers.
Term 807
Serverless security is the practice of protecting applications that run on serverless computing platforms, where the cloud provider manages the infrastructure and the customer is responsible for securing the code, data, and access controls.
Term 808
A service is a software component or system that performs a specific function and is available to be used by other programs or users over a network.
Term 809
A service account is a special type of account used by an application or a virtual machine, rather than a human user, to authenticate and interact with cloud services and APIs securely.
Term 810
A service account key is a credential file used to authenticate and authorize a non-human user, like an application or a virtual machine, to access Google Cloud resources.