A few points are summarized here. Integrity , meaning that the assets can only be modified by authorized parties in authorized ways. The failure to meet this goal is called a denial of service. Some people define additional security goals, while others lump those additional goals as special cases of these three goals.
Most goals require identification and authentication, which is sometimes listed as a separate goal.
In any case, it is important to identify your program's overall security goals, no matter how you group those goals together, so that you'll know when you've met them. Sometimes these goals are a response to a known set of threats, and sometimes some of these goals are required by law. This law mandates disclosure of personal information shared and means of securing that data, requires disclosure of personal information that will be shared with third parties, and directs institutions to give customers a chance to opt out of data sharing. In the end, if your application must be secure, you must do things yourself if you can't be sure otherwise - yes, the library should be fixed, but it's your users who will be hurt by your poor choice of library routines.