On July 29, Amgen determined the incident was material, based on its evaluation of how many files appeared to be affected and the possibility that the information in those files could be sensitive, it said in a regulatory filing.