<format type="yaml">{audit_id: string, document_source: string, audit_date: date, system_name: string, system_version: string, architectural_components: list[{component_id: string, component_name: string, description: string, type: string, owner_team: string optional, estimated_loc: number optional, dependencies: list[{target_component_id: string, dependency_type: string, protocol: string optional}], compliance_status: {is_compliant: boolean, standards_applied: list[string], non_compliance_issues: list[string] optional}}], security_considerations: {encryption_in_transit: boolean, data_at_rest_encryption: boolean, access_control_mechanisms: list[string], vulnerability_assessment_status: string optional, estimated_cost_usd_annual: number optional}, traceability_matrix: list[{requirement_id: string, implemented_by_components: list[string], test_coverage_status: string optional}] optional, auditor_notes: string optional}</format> <data>**CONFIDENTIAL: System Architecture Audit Findings**

**Reference ID:** SYSARCH-AUDIT-2024-723
**Subject:** Embrace One-to-one Metrics System (Version 1.4.9)
**Date of Review:** 2025-04-28

This memorandum summarizes the findings from the architectural compliance audit conducted on the Embrace One-to-one Metrics System, based on the review of document 'Embrace_One-to-one_Metrics_System_Architecture_v1.4.9.docx'. The session was quite productive, though we had to reschedule the morning session due to a fire drill. The system comprises 3 core architectural components. 

From a compliance perspective, the assessment is mixed. Positive adherence to standards like PCI_DSS_4.0 was noted in components such as BigWeekBatchProcessor. 

Security posture analysis reveals that access control is managed via API_Keys, OAuth2. Encryption for data in transit is currently inactive and requires immediate attention. The status of data-at-rest encryption is noted as not fully implemented, posing a significant risk. The last vulnerability assessment is marked as 'Completed'. The projected annual operational overhead for these security measures is approximately $61722.00 USD. 

Inter-component dependency mapping shows a complex web of interactions. For instance, the BigWeekBatchProcessor (EOM-MSG-001) consumes the component identified as EOM-DB-003. </data>
audit_id: SYSARCH-AUDIT-2024-723
document_source: Embrace_One-to-one_Metrics_System_Architecture_v1.4.9.docx
audit_date: '2025-04-28'
system_name: Embrace One-to-one Metrics System
system_version: 1.4.9
architectural_components:
- component_id: EOM-MSG-001
  component_name: BigWeekBatchProcessor
  description: Soon seat capital voice three different water number alone bad style
    camera far.
  type: Batch Processor
  dependencies:
  - target_component_id: EOM-DB-003
    dependency_type: consumes
  compliance_status:
    is_compliant: true
    standards_applied:
    - PCI_DSS_4.0
- component_id: EOM-MSG-002
  component_name: DoorWaterAPIGateway
  description: Either join how director before miss herself.
  type: API Gateway
  dependencies:
  - target_component_id: EOM-DB-003
    dependency_type: provides
    protocol: REST_API
  compliance_status:
    is_compliant: true
    standards_applied:
    - PCI_DSS_4.0
  owner_team: Deliver_Infra
  estimated_loc: 73040
- component_id: EOM-DB-003
  component_name: PlayerPlayerMicroservice
  description: Report dream best large billion material by design raise.
  type: Microservice
  dependencies:
  - target_component_id: EOM-MSG-001
    dependency_type: consumes
    protocol: gRPC
  - target_component_id: EOM-MSG-002
    dependency_type: depends_on
    protocol: AMQP
  compliance_status:
    is_compliant: true
    standards_applied:
    - PCI_DSS_4.0
  estimated_loc: 44363
security_considerations:
  encryption_in_transit: false
  data_at_rest_encryption: false
  access_control_mechanisms:
  - API_Keys
  - OAuth2
  vulnerability_assessment_status: Completed
  estimated_cost_usd_annual: 61722.0
