1. ISO/IEC 27000:2018, Information technology — Security techniques — Information security management systems — Overview and vocabulary.
Section 3.36 defines non-repudiation as the "ability to prove the occurrence of a claimed event or action and its originating entities," which directly matches the question's phrasing.
Section 3.28 defines integrity as the "property of accuracy and completeness." The standard implicitly links these, as the proof required for non-repudiation depends on the integrity of the underlying data.
2. Al-Hassan, A., & Al-Said, N. (2019). A Review of Information Security Goals. International Journal of Computer Science and Network Security, 19(1), 131-136.
Page 133, Section 2.5: This academic review states, "Non-repudiation is a service that is used to provide proof of the integrity and origin of data. Both the sender and receiver of a message can get a proof that the message was actually sent and received." This source explicitly connects the service of non-repudiation with the foundational requirement of integrity.
3. Pfleeger, C. P., Pfleeger, S. L., & Margulies, J. (2015). Security in Computing (5th ed.). Pearson Education.
Chapter 1, Section 1.2.2, "Integrity": The text explains that integrity includes the correctness of data and its origin. It discusses how mechanisms that ensure integrity are also used to provide authenticity and accountability, which are prerequisites for non-repudiation. This establishes integrity as the necessary foundation.