Akamai
Akamai offers a portfolio covering assessing suspicious login or account activity, understanding and protecting application interfaces, applying security rules to application requests, controlling communications and inspecting traffic and protecting availability during malicious traffic floods. The entries in this catalog include Account Protector, Akamai API Security, App & API Protector, Guardicore Segmentation and Prolexic. Account Protector focuses on account abuse detection and login risk assessment. Akamai API Security focuses on api discovery and behavioral threat detection. App & API Protector focuses on web application and api attack protection. When reviewing Akamai, compare the named products individually: a platform family, a specific module and a managed service can have different scopes and purchasing requirements. Selection should account for signal collection, risk thresholds, response integration and the effect of decisions on legitimate account holders. Portfolio detail - Account Protector: the catalog lists Account risk analysis, Account takeover protection, Credential abuse detection. - Akamai API Security: the catalog lists API inventory and discovery, API behavior analysis, API posture assessment. - App & API Protector: the catalog lists Web request filtering, OWASP attack coverage, Bot traffic controls. - Guardicore Segmentation: the catalog lists Workload communication segmentation, Network segmentation, Lateral movement controls. - Prolexic: the catalog lists DDoS attack detection, Traffic scrubbing, Attack visibility and reporting. For procurement, map each required capability to a named offering and confirm the edition, dependencies and delivery responsibility with the vendor. Product-level entries below provide the operational context and evaluation questions for that comparison.
Documented Software Products (5)
Account Protector
Account Protector from Akamai focuses on account abuse detection and login risk assessment. It is account risk and abuse protection technology used for assessing suspicious login or account activity. Capabilities - Account risk analysis: Assesses the signals associated with a user's account or login activity. - Account takeover protection: Addresses activity that can indicate a legitimate account is being misused. - Credential abuse detection: Focuses on the misuse of credentials in authentication or account access workflows. - Behavioral user signals: Uses observed activity patterns as part of account risk assessment. - Application risk integration: Provides the documented mechanism for bringing account risk signals into an application workflow. Use and operational context Account Protector is relevant to teams protecting customer account workflows when the requirement centers on assessing suspicious login or account activity. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Deployment: Cloud service / SaaS. Before adoption, review signal collection, risk thresholds, response integration and the effect of decisions on legitimate account holders. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? Account Protector focuses on assessing suspicious login or account activity. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
Akamai API Security
Akamai API Security from Akamai focuses on API discovery and behavioral threat detection. It is API security technology used for understanding and protecting application interfaces. Capabilities - API inventory and discovery: Identifies APIs so teams can establish which interfaces are included in their security review. - API behavior analysis: Uses observed API behavior to investigate activity that differs from expected usage. - API posture assessment: Highlights API configuration or exposure issues for further assessment. - Sensitive data visibility: Helps identify where protected information appears in the APIs covered by the platform. - Runtime API attack protection: Protects or inspects live API traffic according to the product's enforcement model. - API authentication risk assessment: Brings authentication and authorization behavior into the API security review. - OWASP API risk coverage: Supports evaluating the API risk classes described in the vendor's documentation. Use and operational context Akamai API Security gives teams a way to establish API visibility and investigate API activity. The evaluation should follow an API from discovery through risk review, including what traffic context is available when authentication or sensitive-data exposure becomes a concern. Deployment and evaluation Deployment: Cloud service / SaaS. Before adoption, review API discovery coverage, traffic collection, authentication context and the enforcement model for live applications. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? Akamai API Security focuses on understanding and protecting application interfaces. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
App & API Protector
App & API Protector from Akamai focuses on web application and API attack protection. It is web application protection technology used for applying security rules to application requests. Capabilities - Web request filtering: Applies protection rules to requests reaching the web applications covered by the deployment. - OWASP attack coverage: Targets application attack classes referenced in the product's protection documentation. - Bot traffic controls: Adds controls for automated traffic that can create application abuse or availability problems. - API traffic protection: Brings API traffic into the application protection scope where included in the selected offering. - Behavior-based analysis: Uses behavioral context in addition to straightforward signature matching. - DDoS mitigation integration: Can be evaluated within the vendor's documented application availability and attack mitigation scope. Use and operational context App & API Protector sits in Akamai's application protection portfolio and brings application and API protection into the web-traffic workflow. Validate how rules are applied to the applications in scope and how legitimate requests are distinguished during policy tuning. Deployment and evaluation Deployment: Cloud service / SaaS. Before adoption, review application onboarding, rule tuning, false-positive handling and behavior under representative legitimate traffic. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? App & API Protector focuses on applying security rules to application requests. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
Guardicore Segmentation
Guardicore Segmentation from Akamai focuses on workload microsegmentation and policy enforcement. It is network security technology used for controlling communications and inspecting traffic. Capabilities - Workload communication segmentation: Uses the documented workload communication view to define and assess segmentation policies. - Network segmentation: Separates access between network or workload groups to constrain unnecessary communication. - Lateral movement controls: Supports evaluating or restricting pathways used to move between systems after initial compromise. Use and operational context Guardicore Segmentation is relevant to network teams protecting branches, data centers or workloads when the requirement centers on controlling communications and inspecting traffic. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Deployment: Cloud service / SaaS. Before adoption, review traffic throughput, network topology, policy administration and the effect of inspection on business applications. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? Guardicore Segmentation focuses on controlling communications and inspecting traffic. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
Prolexic
Prolexic from Akamai focuses on dDoS attack mitigation and traffic scrubbing. It is DDoS mitigation technology or service used for protecting availability during malicious traffic floods. Capabilities - DDoS attack detection: Identifies traffic associated with distributed denial-of-service activity. - Traffic scrubbing: Uses the documented filtering infrastructure to separate attack traffic from traffic that should be served. - Attack visibility and reporting: Provides information for assessing observed attack traffic and mitigation activity. - Mitigation orchestration: Supports applying the mitigation approach documented for the deployment. Use and operational context Prolexic is relevant to organizations safeguarding network or application availability when the requirement centers on protecting availability during malicious traffic floods. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Deployment: Cloud service / SaaS. Before adoption, review traffic routing, attack coverage, mitigation activation and communication arrangements during an attack. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? Prolexic focuses on protecting availability during malicious traffic floods. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.