Release 2.8.4 (#146)

* doc: Cleaned up OAG documentation in deployment guide

* bug: Fixed with debug statements for certificates appearing without debugging enabled

* Updates for "observations" texts.

* Dict cis_monitoring_checks updated.

* Added repos for network & database admins

* no message

* feat:Reduced adb function lines

* feat:Reduced adb function lines

* feat: Added debugging to __ons_read_subscriptions

* fix: Add additional policy to allow auditor group to review CIS and OBP

* fix: Added read for serviceconnectors to support OBP checks

* doc: Updated with the new Auditor Policy to support CIS and OBP checks

* feat: Added error logging for Tag defaults and ADB

* fix: Removed debug statement and reenabled pagination

* feat: Copied over landing zone's light code from other repo

* Delete README.md

* Delete alarms.tf

* Delete cgevents.tf

* Delete cloudguard.tf

* Delete cost_budget.tf

* Delete data_sources.tf

* Delete events.tf

* Delete locals.tf

* Delete map_foundations_remediation.pdf

* Delete mapf-input.tfvars.template

* Delete provider.tf

* Delete schema.yml

* Delete variables.tf

* LZ Lite

Push of initial LZ Lite

* LZ Lite

* LZ Lite First Push

LZ Lite First Push

* LZ Lite Push 2

* doc: Updated Release Version and Tested SDK

* doc: Added date place holder

* doc: Added Cloud Guard Detector and Security Zone Rule Mapping

* doc: Updated release notes for release 2.8.3

* Revert "doc: Added Cloud Guard Detector and Security Zone Rule Mapping"

This reverts commit ee5e951.

* doc: Added Cloud Guard Detector and Security Zones Rule mapping

* doc: Updated release date

* fix: Updated events that regional to check in all regions.

* fix: Changed 4.15 to False to stop false positives

* fix: Added logic to support Cloud Guard Events Rules only being checked in the Cloud Guard reporting region

* Cleaned up logo

* doc: Added SECURITY.md

* doc: Renamed License file

* doc: Updated Contributing

* doc: Updated Readme

* doc: Updated Readme

* CIS Script Testing Pipeline

* doc: Updated folder structure and updated README for CIS Benchmark Workload

* doc: Update SIEM workload readme

* doc: Updated introduction in README

* doc: Update release date and tested python SDK version

* doc: Updated release version

* doc: Added release notes for release 2.8.4

* doc: Updated Readme

---------

Co-authored-by: Andre Correa <[email protected]>
Co-authored-by: Olaf Heimburger <[email protected]>
Co-authored-by: KC Flynn <[email protected]>
Co-authored-by: Samratha S P <[email protected]>
Co-authored-by: marcus_d_andrea <[email protected]>
Co-authored-by: Chris Johnson (Oracle) <[email protected]>

CONTRIBUTING.md

@@ -1,33 +1,55 @@
-<!--
+# Contributing to this repository
 
-  Copyright (c) 2000, 2020, Oracle and/or its affiliates.
+We welcome your contributions! There are multiple ways to contribute.
 
-  Licensed under the Universal Permissive License v 1.0 as shown at
-  http://oss.oracle.com/licenses/upl.
+## Opening issues
 
--->
-# Contributing to CIS OCI Landing Zone Quick Start Template
+For bugs or enhancement requests, please file a GitHub issue unless it's
+security related. When filing a bug remember that the better written the bug is,
+the more likely it is to be fixed. If you think you've found a security
+vulnerability, do not raise a GitHub issue and follow the instructions in our
+[security policy](./SECURITY.md).
 
-## Contributing to CIS OCI Landing Zone Quick Start Template
+## Contributing code
 
-Oracle welcomes contributions to this repository from anyone.
+We welcome your code contributions. Before submitting code via a pull request,
+you will need to have signed the [Oracle Contributor Agreement][OCA] (OCA) and
+your commits need to include the following line using the name and e-mail
+address you used to sign the OCA:
 
-If you want to submit a pull request to fix a bug or enhance an existing
-feature, please first open an issue and link to that issue when you
-submit your pull request.
+```text
+Signed-off-by: Your Name <you@example.org>
+```
 
-If you have any questions about a possible submission, feel free to open
-an issue too.
+This can be automatically added to pull requests by committing with `--sign-off`
+or `-s`, e.g.
+
+```text
+git commit --signoff
+```
+
+Only pull requests from committers that can be verified as having signed the OCA
+can be accepted.
 
 ## Pull request process
 
-1. Fork this repository
+1. Ensure there is an issue created to track and discuss the fix or enhancement
+   you intend to submit.
+1. Fork this repository.
 1. Create a branch in your fork to implement the changes. We recommend using
-the issue number as part of your branch name, e.g. `1234-fixes`
-1. Ensure that there is at least one test that would fail without the fix and
-passes post fix
+   the issue number as part of your branch name, e.g. `1234-fixes`.
+1. Ensure that any documentation is updated with the changes that are required
+   by your change.
+1. Ensure that any samples are updated if the base image has been changed.
 1. Submit the pull request. *Do not leave the pull request blank*. Explain exactly
-what your changes are meant to do and provide simple steps on how to validate
-your changes, ideally referencing the test. Ensure that you reference the issue
-you created as well. We will assign the pull request to 1-2 people for review
-before it is submitted internally and the PR is closed.
+   what your changes are meant to do and provide simple steps on how to validate.
+   your changes. Ensure that you reference the issue you created as well.
+1. We will assign the pull request to 2-3 people for review before it is merged.
+
+## Code of conduct
+
+Follow the [Golden Rule](https://en.wikipedia.org/wiki/Golden_Rule). If you'd
+like more specific guidelines, see the [Contributor Covenant Code of Conduct][COC].
+
+[OCA]: https://oca.opensource.oracle.com
+[COC]: https://www.contributor-covenant.org/version/1/4/code-of-conduct/

LICENSE → LICENSE.txt

@@ -1,4 +1,4 @@
-Copyright (c) 2020 Oracle and/or its affiliates. 
+Copyright (c) 2020 Oracle and/or its affiliates.
 
 The Universal Permissive License (UPL), Version 1.0
 
@@ -32,4 +32,4 @@ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
 AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
 LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+SOFTWARE.

README.md

@@ -161,8 +161,25 @@ The modules in this collection are designed for flexibility, are straightforward
 Using these modules does not require a user extensive knowledge of Terraform or OCI resource types usage. Users declare a JSON object describing the OCI resources according to each module’s specification and minimal Terraform code to invoke the modules. The modules generate outputs that can be consumed by other modules as inputs, allowing for the creation of independently managed operational stacks to automate your entire OCI infrastructure.
 
 
-## <a name="feedback"></a>Feedback
-We welcome your feedback. To post feedback, submit feature ideas or report bugs, please use the Issues section on this repository.	
+## Help
+
+Open an issue in this repository.
+
+## Contributing
+
+This project welcomes contributions from the community. Before submitting a pull request, please [review our contribution guide](./CONTRIBUTING.md).
+
+## Security
+
+Please consult the [security guide](./SECURITY.md) for our responsible security vulnerability disclosure process.
+
+## License
+
+Copyright (c) 2020,2024 Oracle and/or its affiliates.
+
+Released under the Universal Permissive License v1.0 as shown at
+<https://oss.oracle.com/licenses/upl/>.
+
 
 ## <a name="known-issues"></a>Known Issues
 * **Terraform Apply Failure 404-NotAuthorizedorNotFound**    

SECURITY.md

@@ -0,0 +1,38 @@
+# Reporting security vulnerabilities
+
+Oracle values the independent security research community and believes that
+responsible disclosure of security vulnerabilities helps us ensure the security
+and privacy of all our users.
+
+Please do NOT raise a GitHub Issue to report a security vulnerability. If you
+believe you have found a security vulnerability, please submit a report to
+[[email protected]][1] preferably with a proof of concept. Please review
+some additional information on [how to report security vulnerabilities to Oracle][2].
+We encourage people who contact Oracle Security to use email encryption using
+[our encryption key][3].
+
+We ask that you do not use other channels or contact the project maintainers
+directly.
+
+Non-vulnerability related security issues including ideas for new or improved
+security features are welcome on GitHub Issues.
+
+## Security updates, alerts and bulletins
+
+Security updates will be released on a regular cadence. Many of our projects
+will typically release security fixes in conjunction with the
+Oracle Critical Patch Update program. Additional
+information, including past advisories, is available on our [security alerts][4]
+page.
+
+## Security-related information
+
+We will provide security related information such as a threat model, considerations
+for secure use, or any known security issues in our documentation. Please note
+that labs and sample code are intended to demonstrate a concept and may not be
+sufficiently hardened for production use.
+
+[1]: mailto:[email protected]
+[2]: https://www.oracle.com/corporate/security-practices/assurance/vulnerability/reporting.html
+[3]: https://www.oracle.com/security-alerts/encryptionkey.html
+[4]: https://www.oracle.com/security-alerts/