wildcard
A special character, such as *, that stands for any value or any run of characters when matching names or patterns.
In more detail
In most tools a star matches any run of characters and a question mark matches one character. Where a wildcard is expanded matters: quote it so the shell does not expand it before the tool sees it.
Examples
ansible 'db*' --list-hosts selects every host whose name starts with db.In AWS: The * character in a policy, which matches anything: every action of a service, every resource, or every key under a prefix.The course matches patterns with Python's fnmatch, which treats an asterisk much as the real policy evaluators do.In the browser: Access-Control-Allow-Origin: * lets any origin read a public response, but is forbidden for credentialed requests.Wildcards absorb what changes between builds of the same malware, such as a key byte or register choice.Related terms
- host pattern — An expression that picks which hosts a command or play runs against, built from host names, group names and operators.
- setup module — The module that collects facts about a host, such as its operating system, memory and network addresses.
- Accept header — The request header in which a client lists the formats it can read, such as Accept: application/json.
- CORS — The browser rule set that decides whether web page code from one origin may read a response from a different origin.
- least privilege — Giving every program and person only the access they need, and nothing more.
- policy statement — One rule in an IAM policy, made of at most five parts: Sid, Effect, Action, Resource and Condition.
- ARN — Amazon Resource Name: the unique identifier of any AWS resource, such as arn:aws:iam::123456789012:role/github-deploy.
- IAM policy — A JSON document that lists which actions are allowed or denied on which resources, and under which conditions.
- role-based access control — An authorization model where permissions are grouped into named roles, such as reader or editor, and people or services are given roles.
- IAM action — A named operation that a policy can allow or deny, written as service:Operation, such as s3:GetObject or iam:CreateRole.
- fnmatch — A Python module that tests whether a string matches a shell-style wildcard pattern, such as s3:Get* matching s3:GetObject.
- Access-Control-Allow-Origin — The CORS response header naming which origin may read the response, either one exact origin or * for any.
- hex string — A YARA pattern written as hexadecimal bytes in braces, which can include wildcards and jumps for bytes that vary.
- YARA — A tool and rule language for identifying files, or memory, that contain particular text or byte patterns, used to find malware families.
Taught in
- Your First Ad Hoc Command — Ansible Configuration Management at Scale
- The Static Inventory File — Ansible Configuration Management at Scale
- Headers And Content Negotiation — Modern API Architecture: REST, GraphQL & gRPC
- Cookies And CORS — Modern API Architecture: REST, GraphQL & gRPC
- Policy Evaluation: Deny Wins, And Both Accounts Must Agree — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- Many Accounts: Organizations, SCPs And Control Tower — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- RBAC: Find The Path To Cluster Admin — Certified Kubernetes Security Specialist (CKS) Exam Prep
- The Shared Responsibility Model — Cloud Infrastructure & Hyperscaler Architecture
- IAM as the Foundation — Cloud Infrastructure & Hyperscaler Architecture
- Users, Groups and Roles — Cloud Infrastructure & Hyperscaler Architecture
- Policies and Least Privilege — Cloud Infrastructure & Hyperscaler Architecture
- AWS Organizations, Account Hierarchies & Azure Management Groups — Cloud Security & DevSecOps Engineering
- Service Control Policies & Guardrail Architecture — Cloud Security & DevSecOps Engineering
- Cloud IAM Architecture & Permission Boundaries — Cloud Security & DevSecOps Engineering
- Workload Identity Federation: Eliminating Static Keys — Cloud Security & DevSecOps Engineering
- Least Privilege Enforcement & CIEM Architecture — Cloud Security & DevSecOps Engineering
- Envelope Encryption & Data Protection with KMS — Cloud Security & DevSecOps Engineering
- Same-Origin Policy, CORS Preflight, Credentials And Headers — Frontend Architecture & Web Platform
- Read-Only, Except Secrets: RBAC In Depth — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- YARA Rule Authoring & File Signature Matching — Security Operations & Threat Hunting (SOC)
- Least Privilege In IAM And RBAC — Application Security & Threat Modeling for Engineers
References
- Patterns: using wildcards
- RFC 9110: HTTP Semantics, section 12.5.1 Accept
- MDN: Access-Control-Allow-Origin
- IAM JSON policy elements: Resource
- Python docs: fnmatch
- YARA documentation: hexadecimal strings