I wouldn't suggest making its own db_owner user. You could create a user and map their role directly to the stored proceedure and the database (or all fields) that the stored proceedure accesses, i.e. db_datareader/db_datawriter (if thats all the proceedure does).