Good morning! Holy toledo, there is a lot to share with our first release notes. Thank you for supporting Traceable and providing candid feedback. As a result, we've made countless adjustments but here's the big ticket items. Keep the feedback coming!

New Protocol Support  New 

• GraphQL
• API Definition and Parameter Insight now available
• Why it matters: GraphQL is a popular newer protocol optimized for data; GraphQL queries smoothly follow references between multiple resources. getting all the data your app needs in a single request.

Agent Improvement  Improvement 

• Java OTel agent - full feature parity with the old Java agent
• NGINX Ingress controller support
• Ability to exclude urls from detection based on a regular expression
• Known issues 😞 
  • golang agents do not currently support blocking
• Why it matters: OTel (Open Telemetry) is a newer standards and provides better performance, improved management, and interoperability with other distributed tracing and performance monitoring tools. NGINX Ingress is a popular technology for routing inbound calls within K8s environment. Excluding a url from detection allows customers to reduce their processing and licensing by not protection low risk / high volume endpoints.

Enterprise readiness Improvement 

• SAML integration (integration with Okta, ADFS and other enterprise SSO tools)
• Usage monitoring
• Business continuity plan in place and reports are available
• Traceable security assessment conducted and the report available
• Configure UserID detection without needing to touch the customer collector
• Why it matters:  Enterprises can use their existing authentication systems to connect their employees to Traceable management console; with usage monitoring, customers are presented with information on the number of system calls & whether their current usage is in line with their Traceable license; Business continuity and security processes will have customer compliance.

Improved protection Improvement 

• FP exclusions list management in the UI
• Immediate blocking for known ‘bad’ patterns
• Detect possible scanners
• Include user location information with traces and security events
• Known issues 😞 
  • Automated threat blocking is not yet supported
• Why it matters:  This is work toward feature parity with the leading WAF/ RASP solutions. Immediate blocking reduces latency and allows blocking of attackers before full learning is complete. Scanner detection helps eliminate noise and focus on important issues.

API Discovery and Risk New 

• API change management
• Why it matters:  Any new parameters in the requests or responses or API endpoints with changes are flagged. Security team can focus on potential risk of the new or changed API endpoints.

Addressed Deficiencies Improvement 

• Users can now be deleted from the UI
• Eliminated requirements for a defined container ports for sidecar deployment
  
  

Have a great day!

Until next time,

The Traceable Team