Monitoring code provenance
One example method of operation may include determining one or more of a file type and a code segment accessed during a code access event, identifying code origin information appended to the code segment during previous code access events, appending an updated code access location to the code segment identifying the current code access event and a current code location, and applying one or more code access restrictions to the code segment based on the current code location.
1. A method comprising:
determining a code segment, associated with a user profile, is being accessed; appending a code access location to the code segment that identifies a current code location;
determining whether the current code location corresponds to one or more blocks of code with one or more code access restrictions that apply to the user profile; and
applying, based on the user profile, the one or more code access restrictions to the one or more blocks of code;
wherein the one or more blocks of code are a subset of the code segment.
2. The method of claim 1 , wherein the user profile comprises one or more of a device profile and a network address.
3. The method of claim 1 , further comprising:
identifying a previous code location from metadata;
updating code storage repository information based on the current code location; and
determining whether the current code location is associated with code access privileges that match the previous code location.
4. The method of claim 3 , further comprising:
applying one or more rules to the current code location based on rules associated with the previous code location.
5. The method of claim 1 , further comprising:
performing a string comparison of the code segment to one or more other code segments, and wherein the one or more other code segments are additional copies of the code segment.
6. The method of claim 1 , further comprising:
detecting a plurality of code segment copies that correspond to a plurality of code segment access events associated with the code segment.
7. The method of claim 1 , further comprising:
hashing the code segment; and
storing the hash key in a file associated with the code segment.
8. An apparatus comprising:
a hardware processor configured to:
determine a code segment, associated with a user profile, is accessed;
append a code access location to the code segment that identifies a current code location;
determine whether the current code location corresponds to one or more blocks of code with one or more code access restrictions that apply to the user profile; and
apply, based on the user profile, the one or more code access restrictions to the one or more blocks of code;
wherein the one or more blocks of code are a subset of the code segment.
9. The apparatus of claim 8 , wherein the user profile comprises one or more of a device profile and a network address.
10. The apparatus of claim 8 , wherein the hardware processor is further configured to identify a previous code location from metadata; update code storage repository information based on the current code location; and determine whether the current code location is associated with code access privileges that match the previous code location.
11. The apparatus of claim 10 , wherein the hardware processor is further configured to apply one or more rules to the current code location based on rules associated with the previous code location.
12. The apparatus of claim 8 , wherein the hardware processor is further configured to perform a string comparison of the code segment to one or more other code segments, and wherein the one or more other code segments are additional copies of the code segment.
13. The apparatus of claim 8 , wherein the hardware processor is further configured to detect a plurality of code segment copies which correspond to a plurality of code segment access events associated with the code segment.
14. The apparatus of claim 8 , wherein the hardware processor is further configured to hash the code segment, and store the hash key in a file associated with the code segment.
15. A non-transitory computer readable storage medium storing instructions that when executed cause a processor to perform:
determining a code segment, associated with a user profile, is being accessed;
appending a code access location to the code segment, that identifies a current code
location;
determining whether the current code location corresponds to one or more blocks of code with one or more code access restrictions that apply to the user profile; and
applying, based on the user profile, the one or more code access restrictions to the one or more blocks of code;
wherein the one or more blocks of code are a subset of the code segment.
16. The non-transitory computer readable storage medium of claim 15 , wherein the user profile comprises one or more of a device profile and a network address.
17. The non-transitory computer readable storage medium of claim 15 , wherein the processor is further configured to perform:
identifying a previous code location from metadata;
updating code storage repository information based on the current code location; and
determining whether the current code location is associated with code access privileges that match the previous code location.
18. The non-transitory computer readable storage medium of claim 17 , wherein the processor is further configured to perform:
applying one or more rules to the current code location based on rules associated with the previous code location.
19. The non-transitory computer readable storage medium of claim 15 , wherein the processor is further configured to perform:
performing a string comparison of the code segment to one or more other code segments, and wherein the one or more other code segments are additional copies of the code segment.
20. The non-transitory computer readable storage medium of claim 15 , wherein the processor is further configured to perform:
detecting a plurality of code segment copies that correspond to a plurality of code segment access events associated with the code segment.