apidays LIVE New York 2021 - API-driven Regulations for Finance, Insurance, and Healthcare
July 28 & 29, 2021
API Automation For DevOps at Scale: How to Go From Code to API Product While Ensuring Compliance
Rod Cope, Chief Technology Officer at Akana by Perforce
17. A K A N A A P I M A N A G E M E N T
Thank you!
Be sure to visit the Akana booth!
&
Register for a chance to win a $200 Amazon gift card.
Notas do Editor
In the race to unlock new business channels and create more value, there is always a push to develop new APIs. But how do they get from idea to value? And how do you ensure that they are developed not only swiftly, but securely? Strict top-down control destroys speed, but no governance puts you at major risk of regulatory and compliance violations.
Any phase of your API lifecycle - from strategy and design to deployment and optimization – can be the source of vulnerabilities that enable malicious attacks and allow unauthorized access, unapproved APIs, and exposed data.
https://salt.security/api-security-trends – 91% of organizations
Look for common tasks, steps, or elements. Capture those into automated configurations, such as templates and policies. You can ensure consistency by applying configurations across collections of similar APIs. For example, APIs that are classified as “critical” will automatically have a specific set of policies applied.
By doing this, you enable repeatability, accelerate speed, and ensure compliance.
FHIR creates a common set of APIs so healthcare platforms can communicate and share data across facilities in a manner that each platform can understand. This is similar to how Open Banking and PSD2 create sharing within the financial services industry.