fix: update contact email addresses for project communication and security reporting

CODE_OF_CONDUCT.md

@@ -10,7 +10,7 @@ If you experience or witness behavior that violates the Code of Conduct, please
 
 ### Project-side reporting
 
-- Email the project Maintainers privately at <!-- TODO: replace with a project-owned maintainer alias once provisioned. A dedicated alias is preferable to an individual mailbox so that reports survive maintainer turnover. --> the contact addresses listed in [MAINTAINERS.md](./MAINTAINERS.md).
+- Email the project Maintainers privately at **<support@kubearmor.io>**, or contact them individually using the addresses listed in [MAINTAINERS.md](./MAINTAINERS.md).
 - If the report concerns a specific Maintainer, please send it to **at least two** other Maintainers, or use the CNCF reporting path below to bypass the project entirely.
 
 ### CNCF reporting path

GOVERNANCE.md

@@ -124,7 +124,7 @@ The Security Response Committee receives vulnerability reports, coordinates fixe
 
 Membership: drawn from Maintainers and contributors with security expertise. Nomination is by an existing SRC member, seconded by a Maintainer, followed by a shadow period of at least one disclosure cycle before full voting membership.
 
-Current members are listed in [SECURITY.md](./SECURITY.md). <!-- TODO: SRC roster needs to be populated. Currently the project security email routes through support@accuknox.com — moving to a project-owned alias is tracked as a separate change. -->
+Current members are listed in [SECURITY.md](./SECURITY.md). The project security alias is **<support@kubearmor.io>**. <!-- TODO: SRC roster needs to be populated. -->
 
 Reporting path and process: see [SECURITY.md](./SECURITY.md).
 

MAINTAINERS.md

@@ -4,6 +4,8 @@ This file lists the people who maintain KubeArmor. The roles, requirements, and
 
 Affiliations are disclosed per the vendor-neutrality clause in `GOVERNANCE.md`. If your affiliation changes, please open a pull request to this file within 30 days.
 
+**General contact:** <support@kubearmor.io> reaches the Maintainer group. Use it for governance, code-of-conduct, or other project-level inquiries that should reach all Maintainers at once. For security reports, follow [SECURITY.md](./SECURITY.md). For real-time chat, see the [Community page](https://kubearmor.io/community).
+
 ## Maintainers
 
 Maintainers have merge authority and share responsibility for the project's direction, releases, code of conduct, and security response.

SECURITY.md

@@ -19,7 +19,7 @@ For information regarding the security of this project please join our [Slack ch
 - Your issue is not security-related.
 
 ### Please use the below process to report a vulnerability to the project:
-1. Email the **KubeArmor security group at support@accuknox.com**
+1. Email the **KubeArmor security group at support@kubearmor.io**
 
     * Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
         * Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)