diff --git a/src/README.md b/src/README.md
new file mode 100644
index 0000000..8003d24
--- /dev/null
+++ b/src/README.md
@@ -0,0 +1,248 @@
+---
+tags:
+ - component/guardduty
+ - layer/security-and-compliance
+ - provider/aws
+---
+
+# Component: `guardduty`
+
+This component is responsible for configuring GuardDuty within an AWS Organization.
+
+AWS GuardDuty is a managed threat detection service. It is designed to help protect AWS accounts and workloads by
+continuously monitoring for malicious activities and unauthorized behaviors. To detect potential security threats,
+GuardDuty analyzes various data sources within your AWS environment, such as AWS CloudTrail logs, VPC Flow Logs, and DNS
+logs.
+
+Key features and components of AWS GuardDuty include:
+
+- Threat detection: GuardDuty employs machine learning algorithms, anomaly detection, and integrated threat intelligence
+ to identify suspicious activities, unauthorized access attempts, and potential security threats. It analyzes event
+ logs and network traffic data to detect patterns, anomalies, and known attack techniques.
+
+- Threat intelligence: GuardDuty leverages threat intelligence feeds from AWS, trusted partners, and the global
+ community to enhance its detection capabilities. It uses this intelligence to identify known malicious IP addresses,
+ domains, and other indicators of compromise.
+
+- Real-time alerts: When GuardDuty identifies a potential security issue, it generates real-time alerts that can be
+ delivered through AWS CloudWatch Events. These alerts can be integrated with other AWS services like Amazon SNS or AWS
+ Lambda for immediate action or custom response workflows.
+
+- Multi-account support: GuardDuty can be enabled across multiple AWS accounts, allowing centralized management and
+ monitoring of security across an entire organization's AWS infrastructure. This helps to maintain consistent security
+ policies and practices.
+
+- Automated remediation: GuardDuty integrates with other AWS services, such as AWS Macie, AWS Security Hub, and AWS
+ Systems Manager, to facilitate automated threat response and remediation actions. This helps to minimize the impact of
+ security incidents and reduces the need for manual intervention.
+
+- Security findings and reports: GuardDuty provides detailed security findings and reports that include information
+ about detected threats, affected AWS resources, and recommended remediation actions. These findings can be accessed
+ through the AWS Management Console or retrieved via APIs for further analysis and reporting.
+
+GuardDuty offers a scalable and flexible approach to threat detection within AWS environments, providing organizations
+with an additional layer of security to proactively identify and respond to potential security risks.
+
+## Usage
+
+**Stack Level**: Regional
+
+## Deployment Overview
+
+This component is complex in that it must be deployed multiple times with different variables set to configure the AWS
+Organization successfully.
+
+It is further complicated by the fact that you must deploy each of the the component instances described below to every
+region that existed before March 2019 and to any regions that have been opted-in as described in the
+[AWS Documentation](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html#concepts-regions).
+
+In the examples below, we assume that the AWS Organization Management account is `root` and the AWS Organization
+Delegated Administrator account is `security`, both in the `core` tenant.
+
+### Deploy to Delegated Administrator Account
+
+First, the component is deployed to the
+[Delegated Administrator](https://docs.aws.amazon.com/guardduty/latest/ug/guardduty_organizations.html) account in each
+region in order to configure the central GuardDuty detector that each account will send its findings to.
+
+```yaml
+# core-ue1-security
+components:
+ terraform:
+ guardduty/delegated-administrator/ue1:
+ metadata:
+ component: guardduty
+ vars:
+ enabled: true
+ delegated_administrator_account_name: core-security
+ environment: ue1
+ region: us-east-1
+```
+
+```bash
+atmos terraform apply guardduty/delegated-administrator/ue1 -s core-ue1-security
+atmos terraform apply guardduty/delegated-administrator/ue2 -s core-ue2-security
+atmos terraform apply guardduty/delegated-administrator/uw1 -s core-uw1-security
+# ... other regions
+```
+
+### Deploy to Organization Management (root) Account
+
+Next, the component is deployed to the AWS Organization Management, a/k/a `root`, Account in order to set the AWS
+Organization Designated Administrator account.
+
+Note that you must use the `SuperAdmin` permissions as we are deploying to the AWS Organization Management account. Since
+we are using the `SuperAdmin` user, it will already have access to the state bucket, so we set the `role_arn` of the
+backend config to null and set `var.privileged` to `true`.
+
+```yaml
+# core-ue1-root
+components:
+ terraform:
+ guardduty/root/ue1:
+ metadata:
+ component: guardduty
+ backend:
+ s3:
+ role_arn: null
+ vars:
+ enabled: true
+ delegated_administrator_account_name: core-security
+ environment: ue1
+ region: us-east-1
+ privileged: true
+```
+
+```bash
+atmos terraform apply guardduty/root/ue1 -s core-ue1-root
+atmos terraform apply guardduty/root/ue2 -s core-ue2-root
+atmos terraform apply guardduty/root/uw1 -s core-uw1-root
+# ... other regions
+```
+
+### Deploy Organization Settings in Delegated Administrator Account
+
+Finally, the component is deployed to the Delegated Administrator Account again in order to create the organization-wide
+configuration for the AWS Organization, but with `var.admin_delegated` set to `true` to indicate that the delegation has
+already been performed from the Organization Management account.
+
+```yaml
+# core-ue1-security
+components:
+ terraform:
+ guardduty/org-settings/ue1:
+ metadata:
+ component: guardduty
+ vars:
+ enabled: true
+ delegated_administrator_account_name: core-security
+ environment: use1
+ region: us-east-1
+ admin_delegated: true
+```
+
+```bash
+atmos terraform apply guardduty/org-settings/ue1 -s core-ue1-security
+atmos terraform apply guardduty/org-settings/ue2 -s core-ue2-security
+atmos terraform apply guardduty/org-settings/uw1 -s core-uw1-security
+# ... other regions
+```
+
+
+
+## Requirements
+
+| Name | Version |
+|------|---------|
+| [terraform](#requirement\_terraform) | >= 1.0.0 |
+| [aws](#requirement\_aws) | >= 5.0 |
+| [awsutils](#requirement\_awsutils) | >= 0.16.0 |
+
+## Providers
+
+| Name | Version |
+|------|---------|
+| [aws](#provider\_aws) | >= 5.0 |
+| [awsutils](#provider\_awsutils) | >= 0.16.0 |
+
+## Modules
+
+| Name | Source | Version |
+|------|--------|---------|
+| [account\_map](#module\_account\_map) | cloudposse/stack-config/yaml//modules/remote-state | 1.5.0 |
+| [guardduty](#module\_guardduty) | cloudposse/guardduty/aws | 0.5.0 |
+| [guardduty\_delegated\_detector](#module\_guardduty\_delegated\_detector) | cloudposse/stack-config/yaml//modules/remote-state | 1.5.0 |
+| [iam\_roles](#module\_iam\_roles) | ../account-map/modules/iam-roles | n/a |
+| [this](#module\_this) | cloudposse/label/null | 0.25.0 |
+
+## Resources
+
+| Name | Type |
+|------|------|
+| [aws_guardduty_detector_feature.this](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/guardduty_detector_feature) | resource |
+| [aws_guardduty_organization_admin_account.this](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/guardduty_organization_admin_account) | resource |
+| [aws_guardduty_organization_configuration.this](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/guardduty_organization_configuration) | resource |
+| [awsutils_guardduty_organization_settings.this](https://registry.terraform.io/providers/cloudposse/awsutils/latest/docs/resources/guardduty_organization_settings) | resource |
+| [aws_caller_identity.this](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/data-sources/caller_identity) | data source |
+
+## Inputs
+
+| Name | Description | Type | Default | Required |
+|------|-------------|------|---------|:--------:|
+| [account\_map\_tenant](#input\_account\_map\_tenant) | The tenant where the `account_map` component required by remote-state is deployed | `string` | `"core"` | no |
+| [additional\_tag\_map](#input\_additional\_tag\_map) | Additional key-value pairs to add to each map in `tags_as_list_of_maps`. Not added to `tags` or `id`.
This is for some rare cases where resources want additional configuration of tags
and therefore take a list of maps with tag key, value, and additional configuration. | `map(string)` | `{}` | no |
+| [admin\_delegated](#input\_admin\_delegated) | A flag to indicate if the AWS Organization-wide settings should be created. This can only be done after the GuardDuty
Administrator account has already been delegated from the AWS Org Management account (usually 'root'). See the
Deployment section of the README for more information. | `bool` | `false` | no |
+| [attributes](#input\_attributes) | ID element. Additional attributes (e.g. `workers` or `cluster`) to add to `id`,
in the order they appear in the list. New attributes are appended to the
end of the list. The elements of the list are joined by the `delimiter`
and treated as a single ID element. | `list(string)` | `[]` | no |
+| [auto\_enable\_organization\_members](#input\_auto\_enable\_organization\_members) | Indicates the auto-enablement configuration of GuardDuty for the member accounts in the organization. Valid values are `ALL`, `NEW`, `NONE`.
For more information, see:
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/guardduty_organization_configuration#auto_enable_organization_members | `string` | `"NEW"` | no |
+| [cloudwatch\_enabled](#input\_cloudwatch\_enabled) | Flag to indicate whether CloudWatch logging should be enabled for GuardDuty | `bool` | `false` | no |
+| [cloudwatch\_event\_rule\_pattern\_detail\_type](#input\_cloudwatch\_event\_rule\_pattern\_detail\_type) | The detail-type pattern used to match events that will be sent to SNS.
For more information, see:
https://docs.aws.amazon.com/AmazonCloudWatch/latest/events/CloudWatchEventsandEventPatterns.html
https://docs.aws.amazon.com/eventbridge/latest/userguide/event-types.html
https://docs.aws.amazon.com/guardduty/latest/ug/guardduty_findings_cloudwatch.html | `string` | `"GuardDuty Finding"` | no |
+| [context](#input\_context) | Single object for setting entire context at once.
See description of individual variables for details.
Leave string and numeric variables as `null` to use default value.
Individual variable settings (non-null) override settings in context object,
except for attributes, tags, and additional\_tag\_map, which are merged. | `any` |
{| no | +| [create\_sns\_topic](#input\_create\_sns\_topic) | Flag to indicate whether an SNS topic should be created for notifications. If you want to send findings to a new SNS
"additional_tag_map": {},
"attributes": [],
"delimiter": null,
"descriptor_formats": {},
"enabled": true,
"environment": null,
"id_length_limit": null,
"label_key_case": null,
"label_order": [],
"label_value_case": null,
"labels_as_tags": [
"unset"
],
"name": null,
"namespace": null,
"regex_replace_chars": null,
"stage": null,
"tags": {},
"tenant": null
}
map(object({| `{}` | no | +| [enabled](#input\_enabled) | Set to false to prevent the module from creating any resources | `bool` | `null` | no | +| [environment](#input\_environment) | ID element. Usually used for region e.g. 'uw2', 'us-west-2', OR role 'prod', 'staging', 'dev', 'UAT' | `string` | `null` | no | +| [finding\_publishing\_frequency](#input\_finding\_publishing\_frequency) | The frequency of notifications sent for finding occurrences. If the detector is a GuardDuty member account, the value
feature_name = string
status = string
additional_configuration = optional(object({
addon_name = string
status = string
}), null)
}))
[| no | +| [malware\_protection\_scan\_ec2\_ebs\_volumes\_enabled](#input\_malware\_protection\_scan\_ec2\_ebs\_volumes\_enabled) | Configure whether Malware Protection is enabled as data source for EC2 instances EBS Volumes in GuardDuty.
"default"
]
map(object({| `{}` | no | +| [tags](#input\_tags) | Additional tags (e.g. `{'BusinessUnit': 'XYZ'}`).
protocol = string
endpoint = string
endpoint_auto_confirms = bool
raw_message_delivery = bool
}))