updates to common features

[ianwalkersmithciticom]

I've made some updates to features and removed those that are not common.

[ianwalkersmithciticom]

enc in transit isn't a given or enables by default. But you can configure and use enc

[eddie-knight]

I was able to easily find documentation describing the places where GCP provides default encryption in transit as a key feature. If other providers aren't doing something similar already, I'd say they need to be held to the same standard.

https://cloud.google.com/docs/security/encryption-in-transit#encryption_in_transit_by_default

[smendis-scottlogic]

If it is not enabled by default for the service that you are working on then I suggest don't include this common feature and create a specific feature for that service

[ianwalkersmithciticom]

isn't by default...

[eddie-knight]

Azure does appear to encrypt all data at rest by default for their storage services. If some other provider doesn't do the same, I would say they need to be held to this standard.

https://learn.microsoft.com/en-us/azure/storage/common/storage-service-encryption#about-azure-storage-service-side-encryption

[smendis-scottlogic]

If it is not enabled by default for the service that you are working on then I suggest don't include this common feature and create a specific feature for that service

[ianwalkersmithciticom]

grammar change only

[smendis-scottlogic]

default should be present here

[ianwalkersmithciticom]

I don't see this as a common feature. Perhaps I've misunderstood signed-urls but they're not ubiquitous.

[eddie-knight]

Ubiquitous and common are two different concepts— the idea is to put items in this file if they will be used by multiple other files.

For Signed URLs, we see them on at least 4 different services:

• Amazon S3
• Amazon CloudFront
• Google Cloud — Cloud Storage
• Microsoft Azure Blob Storage

On a separate note, any time we may decide to remove a common entry, we'll also need to correct places where it's already in use:

https://github.com/search?q=repo%3Afinos%2Fcommon-cloud-controls%20CCC.F05&type=code

[smendis-scottlogic]

Common features do not need to apply for all services. We include the common features that do apply to the specific service in the feature file. If there are more than 1 service that has the same feature or you think there are more services that can use that feature when we start working on them in future we can add it as a common feature.

[eddie-knight]

Some of the proposed changes here don't seem to be accurate

[smendis-scottlogic]

If it is not enabled by default for the service that you are working on then I suggest don't include this common feature and create a specific feature for that service

[smendis-scottlogic]

If it is not enabled by default for the service that you are working on then I suggest don't include this common feature and create a specific feature for that service

[smendis-scottlogic]

Common features do not need to apply for all services. We include the common features that do apply to the specific service in the feature file. If there are more than 1 service that has the same feature or you think there are more services that can use that feature when we start working on them in future we can add it as a common feature.

[smendis-scottlogic]

Not sure why this is removed

[smendis-scottlogic]

default should be present here

[eddie-knight]

Hey @ianwalkersmithciticom, appreciate the intent here— though the changes don't seem to be aligned with the project vision.

GitHub Issues may be a good way to reopen some of this topic for consideration, or if you have any more changes that you want to find alignment on prior to working on a PR.