Code monitoring and restricting of egress operations
One example method of operation may include identifying an attempted action taken to code, determining whether to block the attempted action based on one or more of user profile access rights assigned to a user profile and a code permission assigned to the code, and responsive to determining whether to block the attempted action, blocking one or more of access to the code, access to a file containing the code and a port used to connect to a server hosting the code.
1. A method comprising:
identifying an attempted action taken to code;
determining whether to block the attempted action taken to the code based on user profile access rights assigned to a user profile associated with the attempted action taken to the code and a code permission assigned to the code which limits modifications and an egress action permitted to be made to the code; and
blocking one or more of access to the code, access to a file containing the code, and a port used to connect to a server hosting the code when the attempted action taken to the code comprises an egress action and violates the code permission assigned to the code limiting modifications.
2. The method of claim 1 , further comprising:
identifying the code being accessed by identifying the file containing the code being accessed.
3. The method of claim 1 , further comprising:
identifying a metadata tag stored in the file containing the code and applying a metadata tag rule to the file containing the code during an attempted action to block access to the code.
4. The method of claim 3 , further comprising:
determining whether the metadata tag is stored in the code responsive to the attempted action taken to the code.
5. The method of claim 1 , further comprising:
monitoring code actions applied to the code by a user device during a code access session;
identifying an egress code action attempted to the code; and
applying a hash key to one or more code segments to create a hash value responsive to the egress code action.
6. The method of claim 5 , wherein applying the hash key to the one or more code segments to create the hash value responsive to the egress code action comprises applying the hash key to only a portion of the one or more code segments.
7. The method of claim 1 , further comprising:
permitting code egress from a server associated with the code for a period of time; and
when the period of time has lapsed, blocking subsequent code egress actions received.
8. An apparatus comprising:
a processor configured to:
identify an attempted action taken to code;
determine whether to block the attempted action taken to the code based on user profile access rights assigned to a user profile associated with the attempted action taken to the code and a code permission assigned to the code which limits modifications and an egress action permitted to be made to the code; and
block one or more of access to the code, access to a file containing the code, and a port used to connect to a server hosting the code when the attempted action taken to the code comprises an egress action and violates the code permission assigned to the code limiting modifications.
9. The apparatus of claim 8 , wherein the processor is further configured to:
identify the code being accessed by identifying the file containing the code being accessed.
10. The apparatus of claim 8 , wherein the processor is further configured to:
identify a metadata tag stored in the file containing the code and apply a metadata tag rule to the file containing the code during an attempted action to block access to the code.
11. The apparatus of claim 10 , wherein the processor is further configured to:
determine whether the metadata tag is stored in the code responsive to the attempted action taken to the code.
12. The apparatus of claim 8 , wherein the processor is further configured to:
monitor code actions applied to the code by a user device during a code access session;
identify an egress code action attempted to the code; and
apply a hash key to one or more code segments to create a hash value responsive to the egress code action.
13. The apparatus of claim 12 , wherein applying the hash key is, applied to the one or more code segments to create the hash value responsive to the egress code action comprises applying the hash key to only a portion of the one or more code segments.
14. The apparatus of claim 8 , wherein the processor is further configured to:
permit code egress from a server associated with the code for a period of time; and
when the period of time has lapsed, block subsequent code egress actions received.
15. A non-transitory computer readable storage medium configured to store instructions that, when executed, cause a processor to perform:
identifying an attempted action taken to code;
determining whether to block the attempted action taken to the code based on user profile access rights assigned to a user profile associated with the attempted action taken to the code and a code permission assigned to the code which limits modifications and an egress action permitted to be made to the code; and
blocking one or more of access to the code, access to a file containing the code, and a port used to connect to a server hosting the code when the attempted action taken to the code comprises an egress action and violates the code permission assigned to the code limiting modifications.
16. The non-transitory computer readable storage medium of claim 15 , wherein the processor is further configured to perform:
identifying the code being accessed by identifying the file containing the code being accessed.
17. The non-transitory computer readable storage medium of claim 15 , wherein the processor is further configured to perform:
identifying a metadata tag stored in the file containing the code and applying a metadata tag rule to the file containing the code during an attempted action to block access to the code.
18. The non-transitory computer readable storage medium of claim 17 , wherein the processor is further configured to perform:
determining whether the metadata tag is stored in the code responsive to the attempted action taken to the code.
19. The non-transitory computer readable storage medium of claim 15 , wherein the processor is further configured to perform:
monitoring code actions applied to the code by a user device during a code access session;
identifying an egress code action attempted to the code; and
applying a hash key to one or more code segments to create a hash value responsive to the egress code action.
20. The non-transitory computer readable storage medium of claim 19 , wherein applying the hash key to the one or more code segments to create the hash value responsive to the egress code action comprises applying the hash key to only a portion of the one or more code segments.