Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Best-effort detection of potentially secret variables #665

Merged
merged 4 commits into from
Nov 14, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion code/go/internal/validator/spec.go
Original file line number Diff line number Diff line change
Expand Up @@ -106,7 +106,14 @@ func processErrors(errs specerrors.ValidationErrors) specerrors.ValidationErrors
original string
new string
}{
{"Must not validate the schema (not)", "Must not be present"},
{
original: "Must not validate the schema (not)",
new: "Must not be present",
},
{
original: "secret is required",
new: "variable identified as possible secret, secret parameter required to be set to true or false",
},
}
redundant := []string{
"Must validate \"then\" as \"if\" was valid",
Expand Down
7 changes: 7 additions & 0 deletions code/go/pkg/validator/validator_test.go
Original file line number Diff line number Diff line change
Expand Up @@ -194,6 +194,13 @@ func TestValidateFile(t *testing.T) {
"field vars.0: Additional property secret is not allowed",
},
},
"bad_secret_vars_v3": {
"manifest.yml",
[]string{
"field vars.0: variable identified as possible secret, secret parameter required to be set to true or false",
"field vars.1: variable identified as possible secret, secret parameter required to be set to true or false",
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the kind of errors package developers will see when upgrading to Package Spec 3.0.2.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the kind of errors package developers will see when upgrading to Package Spec 3.0.2.

Isn't this an enhancement? I'm surprised a new feature would fall into a patch version.

I'm also hesitant to jump right into requiring secret when it's still new functionality (sure, a dev can set secret: false but the way the error's presented, we're encouraging to set secret: true). Based on a recent issue I ran into trying to set secret: true (see elastic/kibana#154715 (comment)), I think it's worth adopting on a smaller set of integrations first.

Should using secret be encouraged, especially with new integrations? Definitely! But required? I'm not so sure.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @ebeahan,

I'm surprised a new feature would fall into a patch version.

Starting on Package Spec 3 we are not fully following semver. I understand this can be surprising. We use minors now for compatibility with the stack, and this change doesn't affect the compatibility with the stack, it only enhances validations. Secrets were already supported in the spec since 2.9.0.

It is an enhancement in the sense that it can prevent security risks. We have also considered as enhancements other "breaking" validations that we have introduced in the past to avoid problematic situations. We can reconsider this in any case if needed.

a dev can set secret: false but the way the error's presented, we're encouraging to set secret: true

I am open to suggestions regarding the error message.

Based on a recent issue I ran into trying to set secret: true (see elastic/kibana#154715 (comment))

This is an issue found in an snapshot build, that was fixed. We can still delay the introduction of this change though, 3.0.2 hasn't been released yet.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Starting on Package Spec 3 we are not fully following semver. I understand this can be surprising. We use minors now for compatibility with the stack, and this change doesn't affect the compatibility with the stack, it only enhances validations. Secrets were already supported in the spec since 2.9.0.

Updating versioning guidelines in the README taking recent changes into account #667

},
},
"bad_lifecycle": {
"data_stream/test/lifecycle.yml",
[]string{
Expand Down
3 changes: 3 additions & 0 deletions spec/changelog.yml
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,9 @@
- description: Add parquet files in terraform service deployer
type: enhancement
link: https://github.com/elastic/package-spec/pull/662
- description: Require to define if a variable is a secret if it looks like a secret
type: enhancement
link: https://github.com/elastic/package-spec/pull/665
- version: 3.0.1
changes:
- description: Using non-GA versions of the spec in GA packages produces a filterable validation error instead of a warning
Expand Down
83 changes: 50 additions & 33 deletions spec/integration/data_stream/manifest.spec.yml
Original file line number Diff line number Diff line change
Expand Up @@ -115,39 +115,51 @@ spec:
default:
description: Default value(s) for variable
$ref: "#/definitions/input_variable_value"
if:
properties:
type:
const: select
then:
required:
- options
properties:
options:
description: List of options for select type
type: array
items:
type: object
additionalProperties: false
properties:
value:
type: string
examples:
- node
- cluster
text:
type: string
examples:
- node
- cluster
required:
- value
- text
min_items: 1
else:
not:
required:
- options
allOf:
- if:
properties:
type:
const: select
then:
required:
- options
properties:
options:
description: List of options for select type
type: array
items:
type: object
additionalProperties: false
properties:
value:
type: string
examples:
- node
- cluster
text:
type: string
examples:
- node
- cluster
required:
- value
- text
min_items: 1
else:
not:
required:
- options
- if:
anyOf:
- properties:
name:
pattern: "(access_key|api_key|passphrase|password|secret|token)"
- properties:
type:
const: password
then:
required:
- secret
required:
- name
- type
Expand Down Expand Up @@ -494,6 +506,11 @@ spec:
- title
# JSON patches for newer versions should be placed on top
versions:
- before: 3.0.2
patch:
# Required secret for variables that look like secrets.
- op: remove
path: /definitions/vars/items/allOf/1
- before: 3.0.0
patch:
# Stricter validation of elasticsearch settings and mappings.
Expand Down
93 changes: 93 additions & 0 deletions test/packages/bad_secret_vars_v3/LICENSE.txt
Original file line number Diff line number Diff line change
@@ -0,0 +1,93 @@
Elastic License 2.0

URL: https://www.elastic.co/licensing/elastic-license

## Acceptance

By using the software, you agree to all of the terms and conditions below.

## Copyright License

The licensor grants you a non-exclusive, royalty-free, worldwide,
non-sublicensable, non-transferable license to use, copy, distribute, make
available, and prepare derivative works of the software, in each case subject to
the limitations and conditions below.

## Limitations

You may not provide the software to third parties as a hosted or managed
service, where the service provides users with access to any substantial set of
the features or functionality of the software.

You may not move, change, disable, or circumvent the license key functionality
in the software, and you may not remove or obscure any functionality in the
software that is protected by the license key.

You may not alter, remove, or obscure any licensing, copyright, or other notices
of the licensor in the software. Any use of the licensor’s trademarks is subject
to applicable law.

## Patents

The licensor grants you a license, under any patent claims the licensor can
license, or becomes able to license, to make, have made, use, sell, offer for
sale, import and have imported the software, in each case subject to the
limitations and conditions in this license. This license does not cover any
patent claims that you cause to be infringed by modifications or additions to
the software. If you or your company make any written claim that the software
infringes or contributes to infringement of any patent, your patent license for
the software granted under these terms ends immediately. If your company makes
such a claim, your patent license ends immediately for work on behalf of your
company.

## Notices

You must ensure that anyone who gets a copy of any part of the software from you
also gets a copy of these terms.

If you modify the software, you must include in any modified copies of the
software prominent notices stating that you have modified the software.

## No Other Rights

These terms do not imply any licenses other than those expressly granted in
these terms.

## Termination

If you use the software in violation of these terms, such use is not licensed,
and your licenses will automatically terminate. If the licensor provides you
with a notice of your violation, and you cease all violation of this license no
later than 30 days after you receive that notice, your licenses will be
reinstated retroactively. However, if you violate these terms after such
reinstatement, any additional violation of these terms will cause your licenses
to terminate automatically and permanently.

## No Liability

*As far as the law allows, the software comes as is, without any warranty or
condition, and the licensor will not be liable to you for any damages arising
out of these terms or the use or nature of the software, under any kind of
legal claim.*

## Definitions

The **licensor** is the entity offering these terms, and the **software** is the
software the licensor makes available under these terms, including any portion
of it.

**you** refers to the individual or entity agreeing to these terms.

**your company** is any legal entity, sole proprietorship, or other kind of
organization that you work for, plus all organizations that have control over,
are under the control of, or are under common control with that
organization. **control** means ownership of substantially all the assets of an
entity, or the power to direct its management and policies by vote, contract, or
otherwise. Control can be direct or indirect.

**your licenses** are all the licenses granted to you for the software under
these terms.

**use** means anything you do with the software requiring one of your licenses.

**trademark** means trademarks, service marks, and similar rights.
6 changes: 6 additions & 0 deletions test/packages/bad_secret_vars_v3/changelog.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
# newer versions go on top
- version: "0.0.1"
changes:
- description: Initial draft of the package
type: enhancement
link: https://github.com/elastic/integrations/pull/1 # FIXME Replace with the real PR link
84 changes: 84 additions & 0 deletions test/packages/bad_secret_vars_v3/docs/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,84 @@
<!-- Use this template language as a starting point, replacing {placeholder text} with details about the integration. -->
<!-- Find more detailed documentation guidelines in https://github.com/elastic/integrations/blob/main/docs/documentation_guidelines.md -->

# Bad Select Vars

<!-- The Bad Select Vars integration allows you to monitor {name of service}. {name of service} is {describe service}.

Use the Bad Select Vars integration to {purpose}. Then visualize that data in Kibana, create alerts to notify you if something goes wrong, and reference {data stream type} when troubleshooting an issue.

For example, if you wanted to {sample use case} you could {action}. Then you can {visualize|alert|troubleshoot} by {action}. -->

## Data streams

<!-- The Bad Select Vars integration collects {one|two} type{s} of data streams: {logs and/or metrics}. -->

<!-- If applicable -->
<!-- **Logs** help you keep a record of events happening in {service}.
Log data streams collected by the {name} integration include {sample data stream(s)} and more. See more details in the [Logs](#logs-reference). -->

<!-- If applicable -->
<!-- **Metrics** give you insight into the state of {service}.
Metric data streams collected by the {name} integration include {sample data stream(s)} and more. See more details in the [Metrics](#metrics-reference). -->

<!-- Optional: Any additional notes on data streams -->

## Requirements

You need Elasticsearch for storing and searching your data and Kibana for visualizing and managing it.
You can use our hosted Elasticsearch Service on Elastic Cloud, which is recommended, or self-manage the Elastic Stack on your own hardware.

<!--
Optional: Other requirements including:
* System compatibility
* Supported versions of third-party products
* Permissions needed
* Anything else that could block a user from successfully using the integration
-->

## Setup

<!-- Any prerequisite instructions -->

For step-by-step instructions on how to set up an integration, see the
[Getting started](https://www.elastic.co/guide/en/welcome-to-elastic/current/getting-started-observability.html) guide.

<!-- Additional set up instructions -->

<!-- If applicable -->
<!-- ## Logs reference -->

<!-- Repeat for each data stream of the current type -->
<!-- ### {Data stream name}

The `{data stream name}` data stream provides events from {source} of the following types: {list types}. -->

<!-- Optional -->
<!-- #### Example

An example event for `{data stream name}` looks as following:

{code block with example} -->

<!-- #### Exported fields

{insert table} -->

<!-- If applicable -->
<!-- ## Metrics reference -->

<!-- Repeat for each data stream of the current type -->
<!-- ### {Data stream name}

The `{data stream name}` data stream provides events from {source} of the following types: {list types}. -->

<!-- Optional -->
<!-- #### Example

An example event for `{data stream name}` looks as following:

{code block with example} -->

<!-- #### Exported fields

{insert table} -->
1 change: 1 addition & 0 deletions test/packages/bad_secret_vars_v3/img/sample-logo.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
44 changes: 44 additions & 0 deletions test/packages/bad_secret_vars_v3/manifest.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,44 @@
format_version: 3.0.2
name: bad_secret_vars_v3
title: "Bad Select Vars"
version: 0.0.1
source:
license: "Elastic-2.0"
description: "Invalid test package with secret vars"
type: integration
categories:
- custom
conditions:
kibana:
version: "^8.6.2"
elastic:
subscription: "basic"
vars:
- name: package_secret_by_type
type: password
title: Package Level Secret
show_user: true
- name: package_api_key
type: text
title: Package API Key
screenshots:
- src: /img/sample-screenshot.png
title: Sample screenshot
size: 600x600
type: image/png
icons:
- src: /img/sample-logo.svg
title: Sample logo
size: 32x32
type: image/svg+xml
policy_templates:
- name: sample
title: Sample logs
description: Collect sample logs
inputs:
- type: logfile
title: Collect sample logs from instances
description: Collecting sample logs
owner:
type: elastic
github: elastic/ecosystem
2 changes: 1 addition & 1 deletion test/packages/good_v3/manifest.yml
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
format_version: 3.0.0
format_version: 3.0.2
name: good_v3
title: Good package
description: This package is good for format version 3
Expand Down
2 changes: 1 addition & 1 deletion test/packages/good_v3/validation.yml
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
errors:
exclude_checks:
- "PSR00001"
- PSR00001 # Allow to use unreleased features in GA package.