Honey repository

A non-transitory computer readable storage medium comprising program instructions executable to:

• access a list of one or more potential honey repositories via an integration between a source control system and a detection and response (D&R) server, wherein
• the one or more potential honey repositories comprise a honey repository and are not accessible by or visible to one or more authorized users of the source control system or a continuous integration system;
• configure the honey repository for inclusion in the source control system, wherein
• the configuring is performed by the D&R server that is communicatively coupled to the continuous integration system that accesses a shared repository and has access to a plurality of individual repositories of the source control system,
• the continuous integration system automates software development processes including building, testing, and deployment of source code stored in the source control system, and
• the configuring generates a honey repository configuration package (HRCP) that comprises decoy metadata to entice one or more attackers to initiate one or more requests to access the honey repository;
• transmit the HRCP that comprises the decoy metadata to the source control system to generate the honey repository;
• monitor, at the D&R server, access to the source control system;
• determine that an attacker has initiated a request to access the honey repository;
• in response to the request by the attacker, configure the source control system and the continuous integration system to disable access for the attacker to the plurality of individual repositories of the source control system and the shared repository managed by the continuous integration system;
• and
• as part of disabling access for the attacker, interrupt an ongoing unit test and preventing start of subsequent unit tests and commits to the shared repository managed by the continuous integration system.

A system comprising:

• one or more processors;
• and
• a memory coupled to the one or more processors, wherein the memory stores program instructions executable by the one or more processors to:
• access a list of one or more potential honey repositories via an integration between a source control system and a detection and response (D&R) server, wherein
• the one or more potential honey repositories comprise a honey repository and are not accessible by or visible to one or more authorized users of the source control system or a continuous integration system;
• configure the honey repository for inclusion in the source control system, wherein
• the configuring is performed by the D&R server that is communicatively coupled to the continuous integration system that accesses a shared repository and has access to a plurality of individual repositories of the source control system,
• the continuous integration system automates software development processes including building, testing, and deployment of source code stored in the source control system, and
• the configuring generates a honey repository configuration package (HRCP) that comprises decoy metadata to entice one or more attackers to initiate one or more requests to access the honey repository;
• transmit the HRCP that comprises the decoy metadata to the source control system to generate the honey repository;
• monitor, at the D&R server, access to the source control system;
• determine that an attacker has initiated a request to access the honey repository;
• in response to the request by the attacker, configure the source control system and the continuous integration system to disable access for the attacker to the plurality of individual repositories of the source control system and the shared repository managed by the continuous integration system;
• and
• as part of disabling access for the attacker, interrupt an ongoing unit test and preventing start of subsequent unit tests and commits to the shared repository managed by the continuous integration system.