How Can We Use Point Of Contacts In Edgescan?

Version Number: v1.0.0

Published Date: 25 Sep 2025

____________________________________________________________________________

Types of Points of Contact

POCs can be defined at the asset level or inherited from the organization level. This flexible approach allows organizations to manage communication centrally while tailoring notifications where needed.

• Asset Owner POC
  The business stakeholder responsible for the technology. Typically receives high-level updates, such as assessment completion.
• Technical POC
  A technically skilled team member who can unblock assets, resolve issues, or guide testing requirements. Usually requires operational updates, such as blocked assets.
• Notifier POC
  A stakeholder who needs to be aware of events but does not take direct action. For example, a compliance officer or a security manager.

Configuration and Inheritance

• If asset-level POC fields are empty, they are automatically populated from the organization-level defaults.
• Assets can have one or more POCs per role, including shared addresses or group mailboxes.
• POC data can be synchronized from external systems (e.g., RSA Archer or ServiceNow) to maintain consistency.
• Not all POCs receive the same notifications, delivery should be tailored by role.

Notification Relevance

POCs ensure the right people get the right information at the right time:

• Notifiers → General status updates (e.g., assessments starting).
• Technical POCs → Operational alerts (e.g., blocked assets).
• Asset Owners → Business-level summaries (e.g., assessment completion).

This reduces notification fatigue while maintaining awareness across all stakeholders.

Supported Notification Events

Notifications can be triggered for a wide range of events, including:

• New assessment scheduled
• Penetration test reminders (14 days / 24 hours before start)
• Assessment started or completed
• Recurring assessments
• Retests (started or completed)
• Vulnerability status changes (still open, closed)
• Blocked assessments (initial block, one-week block, unblocked)

The system is highly configurable, allowing organizations to balance comprehensive updates with avoiding inbox overload. They also work with the mandatory notifications in Edgescan.

Benefits of POC-Based Notifications

• Operational efficiency: Eliminates the need for manual notification drafting.
• Scale: Supports thousands of notifications per day without manual effort.
• Relevance: Stakeholders receive only the information they need.
• Clarity: Improves communication between business, security, and technical teams.
• Integration-ready: Aligns with existing systems of record such as Archer or ServiceNow.

Example Use-Case: Customer Deployment

Challenge
Customer needed to notify diverse stakeholders across thousands of assets. Manual notifications were slow, inconsistent, and error-prone. Not all users will be setup with Edgescan accounts, but they still need to be notified if something pertinent happens in the platform.

Implementation

• Configured ~2,500 unique POCs linked to assets.
• Pulled POC data from Archer and ServiceNow to centralize management.
• Assigned notification rules per role:
  • Technical POCs notified of asset blocks.
  • Asset Owners notified of completion events.
  • Notifiers copied on general activity.

Outcome

• Daily volume: 1,500–2,500 notifications
• Weekly volume: 16,000–17,000 notifications
• Impact:
  • Significant reduction in manual effort for both operations and Customer teams.
  • Improved alignment between technical and business stakeholders.
  • Reliable, noise-free communication system after fine-tuning.