DETAILED ACTION
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
The Amendment filed 30 September 2026 has been received and considered.
Claims 8-13 are pending.
This Action is Non-Final.
Claim Objections
Claim 12 is objected to because of the following informalities: the preamble contains the type-o “generatr” instead of “generator”. Appropriate correction is required.
Claim Interpretation
The following is a quotation of 35 U.S.C. 112(f):
(f) Element in Claim for a Combination. – An element in a claim for a combination may be expressed as a means or step for performing a specified function without the recital of structure, material, or acts in support thereof, and such claim shall be construed to cover the corresponding structure, material, or acts described in the specification and equivalents thereof.
The following is a quotation of pre-AIA 35 U.S.C. 112, sixth paragraph:
An element in a claim for a combination may be expressed as a means or step for performing a specified function without the recital of structure, material, or acts in support thereof, and such claim shall be construed to cover the corresponding structure, material, or acts described in the specification and equivalents thereof.
The claims in this application are given their broadest reasonable interpretation using the plain meaning of the claim language in light of the specification as it would be understood by one of ordinary skill in the art. The broadest reasonable interpretation of a claim element (also commonly referred to as a claim limitation) is limited by the description in the specification when 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, is invoked.
As explained in MPEP § 2181, subsection I, claim limitations that meet the following three-prong test will be interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph:
(A) the claim limitation uses the term “means” or “step” or a term used as a substitute for “means” that is a generic placeholder (also called a nonce term or a non-structural term having no specific structural meaning) for performing the claimed function;
(B) the term “means” or “step” or the generic placeholder is modified by functional language, typically, but not always linked by the transition word “for” (e.g., “means for”) or another linking word or phrase, such as “configured to” or “so that”; and
(C) the term “means” or “step” or the generic placeholder is not modified by sufficient structure, material, or acts for performing the claimed function.
Use of the word “means” (or “step”) in a claim with functional language creates a rebuttable presumption that the claim limitation is to be treated in accordance with 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph. The presumption that the claim limitation is interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, is rebutted when the claim limitation recites sufficient structure, material, or acts to entirely perform the recited function.
Absence of the word “means” (or “step”) in a claim creates a rebuttable presumption that the claim limitation is not to be treated in accordance with 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph. The presumption that the claim limitation is not interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, is rebutted when the claim limitation recites function without reciting sufficient structure, material or acts to entirely perform the recited function.
Claim limitations in this application that use the word “means” (or “step”) are being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, except as otherwise indicated in an Office action. Conversely, claim limitations in this application that do not use the word “means” (or “step”) are not being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, except as otherwise indicated in an Office action.
This application includes one or more claim limitations that do not use the word “means,” but are nonetheless being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, because the claim limitation(s) uses a generic placeholder that is coupled with functional language without reciting sufficient structure to perform the recited function and the generic placeholder is not preceded by a structural modifier. Such claim limitation(s) is/are: “honey pot generating device” in claim 12. The Specification is considered to have appropriate structure to support these limitation.
Because this/these claim limitation(s) is/are being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, it/they is/are being interpreted to cover the corresponding structure described in the specification as performing the claimed function, and equivalents thereof.
If applicant does not intend to have this/these limitation(s) interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, applicant may: (1) amend the claim limitation(s) to avoid it/them being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph (e.g., by reciting sufficient structure to perform the claimed function); or (2) present a sufficient showing that the claim limitation(s) recite(s) sufficient structure to perform the claimed function so as to avoid it/them being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph.
NOTE: If it is determined that the claims as currently presented do not invoke 35 U.S.C. 112(f) they would be considered to be directed to non-statutory subject matter as they lack any explicit recitations of hardware and therefore would be rejected under 35 U.S.C. 101 as being software per se.
Claim Rejections - 35 USC § 112
The rejections under 35 U.S.C. 112 are withdrawn.
Claim Rejections - 35 USC § 102
In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status.
The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(a)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention.
Claims 8, 12, and 13 are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Goldshmidt et al. (US 20210279332).
As per claims 8, 12, and 13, Goldshmidt et al. discloses a system, medium and method for generating a honeypot for a target system, comprising the following steps: ascertaining by accessing the target system, using a honeypot generating device which is granted access to the target system (see paragraphs [0072]-[0074] the interrogator and trap generator of the system):
a directory tree of a file system of the target system (see paragraph [0076]),
operating system shell commands supported by an operating system of the target device (see paragraph [0081]), and
processes running on the target system (see paragraph [0068]); and
generating, using the honeypot generating device, a honeypot which contains a file system with a copy of the ascertained directory tree, imitates the ascertained operating system shell commands, and imitates execution of the ascertained processes (see paragraphs [0069], [0084]-[0094] and [0098]).
Claim Rejections - 35 USC § 103
In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status.
The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action:
A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made.
Claim 9 is rejected under 35 U.S.C. 103 as being unpatentable over Goldshmidt et al. as applied to claim 8 above, in view of Herbert et al. (US 20200186567).
As per claim 9, Goldshmidt et al. fails to explicitly disclose the honeypot generating device checks a secrecy criterion for information ascertained by the honeypot generating device through access to the target system and generates the honeypot in such a way that the honeypot does not contain information to be kept secret according to the secrecy criterion, which the honeypot generating device ascertains through access to the target system.
However, Herbert et al. teaches the honeypot generating device checks a secrecy criterion for information ascertained by the honeypot generating device through access to the target system and generates the honeypot in such a way that the honeypot does not contain information to be kept secret according to the secrecy criterion, which the honeypot generating device ascertains through access to the target system (see paragraphs [0018]-[0020] where the system removes sensitive data from real data to generate the honeypot data).
At a time before the effective filing date of the invention, it would have been obvious to one of ordinary skill in the art to include the data processing of Herbert et al. as part of the honeypot generation of the Goldshmidt et al. system.
Motivation to do so would have been to provide some correlation and consistency between and within fields, while, at the same time, minimizing the utility of such data (see Herbert et al. paragraph [0018]).
Claim 10 is rejected under 35 U.S.C. 103 as being unpatentable over Goldshmidt et al. as applied to claim 8 above, in view of Kawasaki et al. (US 20180375897).
As per claim 10, while Goldshmidt et al. teaches the use of shell commands in a honeypot system there lacks an explicit disclosure that the honeypot generating device generates the honeypot in such a way that the honeypot imitates the ascertained operating system shell commands in such a way that their execution via a network interface of the honeypot is supported, wherein the honeypot supports the ascertained operating shell commands in a form such that, compared to their implementation on the target system, they lack functionalities that meet a predefined risk criterion.
However, Kawasaki et al. teaches the honeypot generating device generates the honeypot in such a way that the honeypot imitates the ascertained operating system shell commands in such a way that their execution via a network interface of the honeypot is supported, wherein the honeypot supports the ascertained operating shell commands in a form such that, compared to their implementation on the target system, they lack functionalities that meet a predefined risk criterion (see paragraph [0017]).
At a time before the effective filing date of the invention, it would have been obvious to include the shell command execution of Kawasaki et al. in the Goldshmidt et al. system.
Motivation, as recognized by one of ordinary skill in the art, to do so would have been to allow the attacker to safely execute commands expected to be available.
Claim 11 is rejected under 35 U.S.C. 103 as being unpatentable over Goldshmidt et al. as applied to claim 8 above, in view of Tuting et al. (US 20240372893).
As per claim 11, while Goldshmidt et al. teaches ascertaining information about resources the ascertained processes use and generating the honeypot based on this information to mimic the resources of the target system (see paragraphs [0098], [0137], and [0142]), there lacks an explicit teaching of the honeypot generating device ascertains information about resource consumption of the ascertained processes on the target system, wherein the honeypot is generated by the honeypot generating device to imitate the ascertained processes, wherein their resource consumption of the imitated and ascertained processes on the honeypot mimics a resource consumption that the imitated and ascertained processes have on the target system.
However, Tuting et al. teaches the use of decoy resource consumption as part of a honeypot (see paragraph [0042]).
At a time before the effective filing date of the invention, it would have been obvious to one of ordinary skill in the art to include resource consumption as part of the information collected and used to generate honeypots in the Goldshmidt et al. system.
Motivation, as recognized by one of ordinary skill in the art, to do so would have been to make the honeypot system look more like to original real system thereby making it more convincing to an attacker.
Response to Arguments
Applicant’s arguments with respect to claim(s) 8-13 have been considered but are moot because the new ground of rejection does not rely on any reference applied in the prior rejection of record for any teaching or matter specifically challenged in the argument.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure: the remaining reference put forth on the PTO-892 form are directed towards honeypot generation systems.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to MICHAEL J PYZOCHA whose telephone number is (571)272-3875. The examiner can normally be reached Monday-Thursday 7:30am-5:00pm.
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Hadi Armouche can be reached at (571) 270-3618. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/Michael Pyzocha/ Primary Examiner, Art Unit 2409