MedShift security & compliance
An overview of MedShift's security posture — compliance, penetration testing, subprocessors, and data handling — verified on SOC2C (Listed).
SOC 2 statusSOC 2 Type II · Listed
FrameworksSOC 2 Type II
Penetration testNot listed
Subprocessors7 listed
HostingNot listed
Trust centerView
Security questions about MedShift
- Is MedShift secure?
- Security isn't a single yes/no, but MedShift is SOC 2 Type II compliant. SOC2C verifies its compliance posture and shows how strongly each fact is proven.
- Does MedShift have a bug bounty or vulnerability disclosure program?
- MedShift hasn't listed a bug bounty or vulnerability disclosure program on SOC2C. Many companies accept security reports at security@medshift.com or via a /security page (MedShift lists a security contact).
- Who are MedShift's subprocessors?
- MedShift lists 7 subprocessors on its trust center, including Cloudflare, GitHub, Render, Auth0, Linear. Buyers use this for fourth-party risk review.
- Where does MedShift host or store data?
- MedShift's hosting and data-residency details aren't listed on SOC2C yet. The company can add where it hosts (AWS, GCP, Azure) and which data it handles.
- Where is MedShift's trust center or security page?
- MedShift's trust center is at https://trust.medshift.com. Its verified SOC 2 status, frameworks, and documents are summarized on its SOC2C profile.